Privacy policy
Who this is for
Executor Gmail is a personal OAuth app. Lloyd is the only user. It is used so his own assistants, running in his Executor workspace, can act on his Google accounts.
Google user data we access
When Lloyd signs in with Google, the app may request:
- Gmail: read, compose, send, and delete mail (
https://mail.google.com/). - Google Drive: list and work with files, including broader Drive scopes already on this Cloud project.
- Google Calendar: read and manage events on the same OAuth client.
- Basic identity: name and email, so Executor can label the connection.
How that data is used
Google user data is used only to do the job Lloyd asked an assistant to do: find a message, draft or send mail he confirmed, check a calendar, or open a Drive file. It is not used for advertising, analytics products, training public models, or resale.
Use of information received from Google APIs follows the Google API Services User Data Policy, including Limited Use.
How it is stored and who sees it
OAuth access and refresh tokens are stored in Executor’s vault for Lloyd’s personal organisation. Mail, calendar, and Drive content is fetched when a task needs it and is not copied into a separate marketing database. Lloyd’s assistants can see that content while doing the task. No third party is sold access.
Sharing
We do not sell or rent Google user data. We do not share it with other companies except Google (to provide the API) and Executor (to hold the tokens and run the tools), and except where the law requires it.
Retention and revocation
Tokens stay until Lloyd disconnects the Executor account or revokes access in his Google Account under third-party apps. He can delete a connection in Executor at any time. After revoke, the app cannot call Gmail, Drive, or Calendar until he signs in again.
Contact
Questions: me@lloydvickery.com.