Privacy notice

1. Information accessed

With the account holder’s Google authorisation, the assistant can retrieve the connected Gmail address, mailbox history identifiers, message and thread identifiers, sender and recipient headers, subjects, dates, snippets, labels and relevant message bodies. It may read earlier messages in a relevant thread to understand requests and deadlines.

Routine monitoring covers new inbox arrivals after its monitoring baseline. It does not automatically scan the existing backlog or Spam folder, download attachments, or follow links in email. Those activities would require separately agreed scope.

The informational website does not display email, collect Google passwords or provide an account-registration form. Google sign-in and consent happen on Google’s own pages through a separate local authorisation flow.

2. Purpose and permission

Data is used to identify correspondence needing attention, produce concise summaries and help with account-holder-approved email organisation. It is not sold, used for advertising or credit decisions, or used by the operator to train general-purpose AI models.

The connection requests https://www.googleapis.com/auth/gmail.modify. This permission technically allows reading, composing, sending and modifying Gmail messages. The monitoring implementation only reads Gmail. Moving approved messages to Trash, changing labels, archiving, unsubscribing or sending email requires explicit approval for the particular action or batch. Routine monitoring does not immediately permanently delete messages or empty Trash.

Use and transfer of information received from Google APIs is subject to the Google API Services User Data Policy, including its Limited Use requirements. Google data is restricted to providing the account holder’s requested email-assistance features.

3. Where processing happens

• Google: provides Gmail and the authorisation/token services used by the assistant.
• Local Hermes installation: stores authorisation credentials, monitoring state, pending-message metadata, snippets, deferred summaries and operational records on the operator’s computer. Access restrictions are applied to credential files and monitoring state.
• AI service: relevant message information and thread text can be sent to the configured AI provider for classification and summarisation. The current configuration uses OpenAI through Hermes. This means email processing is not entirely on-device. Provider-side storage, access and data handling are governed by the account’s applicable settings and service terms; this notice does not promise zero provider retention.
• Telegram: receives concise attention summaries through the operator’s verified private bot chat. The messages are processed and retained by Telegram under its own terms. They are not posted to a group or made available on this website.
• Cloudflare: hosts and delivers these public informational pages. It can process ordinary web-request information such as IP addresses, browser details and security logs. The website does not send mailbox content or authorisation tokens to Cloudflare as part of its page content.

The operator does not intentionally make private email available to other people. The installation is for personal use; enabling other accounts or changing providers requires a review of these disclosures and the relevant permissions.

4. Storage and retention

Original messages remain in Gmail and are subject to Gmail’s own retention and the account holder’s actions. Local pending entries are removed from the monitoring queue when processed; nonurgent attention notes are held until an eligible notification time.

Local credentials, decision reports, assistant or scheduler records and conversation history can remain until the operator removes them. There is currently no fixed automatic deletion period for all local records. The operator should review and remove data no longer needed.

AI-service records, Cloudflare logs and Telegram messages have their own retention rules. Deleting local records or revoking Google access does not automatically delete those copies. This notice does not claim that all records are encrypted at rest, end-to-end encrypted or confined to the UK.

5. Notifications and safeguards

Checks run hourly while the computer and Hermes scheduler are available. Routine attention summaries are held between 22:00 and 08:00 Europe/London time; genuinely urgent alerts may bypass quiet hours. Empty or unchanged checks do not generate routine notifications.

Monitoring preserves Gmail’s unread state. Notification logic checks the intended private Telegram recipient and tracks pending and delivered items. A notification with an uncertain delivery outcome is held for manual review rather than automatically resent. Credentials, verification codes and authentication secrets must not appear in alerts.

These safeguards reduce risk; they are not a guarantee of perfect classification, uninterrupted monitoring or complete detection. The account holder should continue checking Gmail directly for critical correspondence.

6. Stop access or request deletion

The account holder can stop scheduled monitoring through Cortana or Hermes, and can revoke the app’s Google access at any time using Google Account → Third-party connections. Revocation prevents future authorised Gmail access but does not erase existing records.

To remove stored data, ask the operator to stop the job and delete the local credentials, monitoring data and relevant assistant records. Review Telegram messages and AI-service account controls separately. This informational website has no public account or data-deletion form.

7. Website, contact and changes

These static pages contain no advertising, analytics scripts, embedded players or third-party fonts. They contain ordinary links to the privacy notice and relevant Google account/policy pages. Cloudflare’s own delivery and security processing remains applicable.

Operator: Codrin. For privacy questions or deletion requests, use the support email displayed on the app’s Google consent screen or contact the operator through your established private channel.

The operator should update this notice before materially changing the purposes of processing, providers, sharing arrangements or account access, and obtain additional consent where required.