Privacy Policy

Application: cachymeyoucanhermes · Last updated: 29 September 2026

This policy describes how the cachymeyoucanhermes application (“the Application”) handles information. The Application is a private, single-user automation agent that runs locally on its owner's own computer and operates only on that same owner's Google account.

1. Who this applies to

The Application has exactly one user: the account owner. It is not a public service and is not offered to, or usable by, anyone else.

2. Information the Application accesses

When the owner authorises it, the Application may access the following data in the owner's own Google Account:

• Gmail — read, compose, send and modify email
• Google Calendar — read and manage calendars and events
• Google Drive, Docs and Sheets — read and write files owned by the owner
• Google Contacts — read the owner's contacts (read-only)

3. How the information is used

Accessed data is used solely to perform the automation tasks the owner requests — for example, summarising the day's email, creating calendar events, or updating a personal spreadsheet. The data is used only for these personal productivity purposes.

4. Storage and retention

Data is processed and stored locally on the owner's own computer. OAuth credentials are held locally on that machine and never transmitted to any third party. Locally cached data is retained only as long as it is useful to the owner and can be deleted by the owner at any time.

5. Sharing and disclosure

No data is sold, rented, traded, or shared with any third party. The Application does not use or transfer Google user data for advertising, profiling, or any purpose unrelated to the personal automation described above. Data is not used to train, develop, or improve machine learning models.

6. Google API Services User Data Policy

The Application's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Only the minimum data needed to carry out a requested task is accessed, and it is never transferred to others.

7. Security

Access is granted via Google's standard OAuth 2.0 flow. The Application holds no passwords for the owner's Google Account; it uses revocable OAuth tokens stored locally. Google account access is protected by the owner's own Google Account security settings, including two-factor authentication where enabled.

8. Revoking access and deleting data

The owner may revoke the Application's access at any time from the Google Account permissions page. Once revoked, the Application can no longer access any Google data, and locally stored tokens become unusable. Locally stored data may be deleted by the owner at any time.

9. Children's privacy

The Application is a personal tool with a single adult user and is not directed at children.

10. Changes to this policy

Any changes will be posted on this page, and the “Last updated” date above will be revised.

11. Contact

Questions about this policy or the Application's data practices may be sent to wari.wahab@gmail.com.