Privacy policy
Sendora personal Gmail agent · last updated 26 October 2026
Sendora ("the application") is a private automation tool that runs on its owner's computer and acts on a single Gmail mailbox — the owner's own. This policy explains exactly what the application accesses, where that data lives, and how to remove it.
1. Data controller
The application is operated by an individual, not a company, and only for their own personal mailbox. Contact: pchanvallon@gmail.com.
2. What the application accesses
| Google scope | Why |
|---|---|
gmail.readonly | Read message metadata and bodies of the owner's own mailbox in order to classify incoming mail. |
gmail.modify | Apply and remove Gmail labels, and create draft replies. Drafts are never sent automatically. |
No other Google service is accessed. The application does not use Calendar, Drive, Contacts, or any messaging scope.
3. How data is processed
- Messages are read on demand, one batch at a time, to decide which label applies and whether a draft reply is worth preparing.
- Processing happens locally. Message contents are not uploaded to any third-party analytics, advertising, or AI-training service beyond the model provider used to generate the draft text, which receives only the message being classified.
- The application never sends email. It never deletes messages. It never shares or transfers mailbox data to another person or service.
- No mailbox data is sold, rented, or used for advertising. Google Workspace / Gmail API user data is not used to develop, improve, or train generalized AI or machine-learning models.
4. Storage and retention
- The OAuth refresh token is stored in a local file on the owner's Mac, readable only by the owner's OS account.
- Classification results and log lines are kept locally for a few days for troubleshooting, then discarded.
- No mailbox content is retained on any server: there is no Sendora backend or database.
5. Sharing
No data is shared with third parties. There are no sub-processors other than Google's own APIs (Gmail) and the language model provider used to draft text, both used solely to perform the operations described above.
6. Your rights and revocation
- Access can be revoked at any time at myaccount.google.com/permissions, which immediately ends the application's ability to read or modify the mailbox.
- Deleting the local token file removes all stored credentials.
- For any question about access, deletion, or portability of data handled by the application, write to pchanvallon@gmail.com.
7. Security
The token file is stored with owner-only permissions on an encrypted macOS disk. Traffic to Google uses TLS. Because the application runs locally and has no server component, there is no shared infrastructure to breach.
8. Changes
If this policy changes, the updated date at the top of this page changes with it. Given the single-user nature of the application, no notification is sent.