Privacy

Last updated: 25 October 2026.

What Google data is used

After the account owner connects Google and separately approves a task, CountingSecrets may read matching Gmail inbox metadata and snippets, primary Calendar event summaries, and selected Drive file metadata and body text. Resource, date, size and call limits apply to each task. The selected-file permission supplied by Google includes editing; CountingSecrets exposes read operations only.

Why it is used

Data is used to carry out the owner-approved task and return its results to the chosen AI agent. CountingSecrets does not use Google data for advertising or to train AI models.

Storage and sharing

Google credentials are encrypted in CountingSecrets’ private Google connector. They are not given to the agent. The system retains task permissions and minimized receipts, including resource identifiers, requested scope, times, decisions, outcomes and result digests. Google message and document bodies are not retained in the receipt store.

Cloudflare hosts the application and private storage. Auth0 authenticates agent connections using basic identity information; it does not receive Gmail, Calendar or Drive permissions. Approved Google results are disclosed to the selected agent and its provider. That provider’s own privacy and retention settings also apply. Data already returned to an agent cannot be recalled by revoking a task.

Your controls

The account owner can decline requests, revoke individual tasks, disconnect a client or stop Google access. Google authorization can also be revoked in the Google Account’s third-party connections settings. Revocation stops future covered access; existing receipt history is retained for review. Automated receipt deletion and a self-service account-history deletion flow are not currently provided.

CountingSecrets’ use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Contact

For this personal-use setup, contact the application owner through the support contact shown on Google’s consent screen.