Robin Privacy Policy
Last updated August 30, 2026.
Google data we access
After you authorize Robin, we access your Google identity, the Google Drive files and folders within the operating scope you select, relevant Google Calendar events and attendees, Google Meet events and artifacts, Gmail sending needed for task delivery, and Google Cloud project and billing state needed to create and operate your isolated Robin tenant.
How we use Google data
We use this data only to authenticate you, understand and execute your goals, retrieve authorized company context, place completed work in authorized Drive destinations, deliver contextualized tasks, process authorized Calendar and Meet events, and provision and operate your tenant. We do not use Google Workspace data to train generalized AI or machine-learning models.
Google Workspace Limited Use
Robin's use of information received from Google Workspace APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Tenant storage and isolation
Each Robin tenant has isolated runtime state, credentials, billing, configuration, memory, and evolving custom tools. A tenant cannot influence another tenant's execution, data, billing, or learning.
Sharing
We share data with Google APIs as required to provide the authorized service and with the Drive collaborators or Gmail recipients designated by the authenticated executive when necessary to deliver completed work or contextualized human tasks. We do not sell Google user data, use it for advertising, or share it with unrelated third parties.
Retention, deletion, and revocation
You may revoke Google authorization or deprovision Robin. Revocation blocks new execution. Deprovisioning removes routing and subscriptions, unlinks tenant billing, requests deletion of the tenant Google Cloud project, and destroys the tenant credential after teardown authority is no longer needed. Required non-secret verification receipts may be retained to prove the lifecycle outcome.
Security
Robin uses encrypted credential custody, short-lived tenant-bound assertions, least-authority routing, immutable release verification, and per-tenant Google Cloud isolation.
Changes and contact
We may update this policy as Robin evolves. Material changes will be reflected on this page. Questions or deletion requests: adampaulin14@gmail.com.