Last updated October 14, 2026

Privacy Policy

This policy describes the personal-use application Hermes Financial Inbox and its access to Google user data. The application is operated by its account owner for private financial organization and is not offered to other users.

Google data accessed

With the account owner's authorization, the application uses the Gmail API scope https://www.googleapis.com/auth/gmail.readonly. That scope permits viewing mailbox messages and their contents, including attachments. It does not permit sending, deleting, or changing Gmail messages.

Purpose and current use

The application is intended to identify and organize financial notifications, statements, payment amounts, and due dates. Its initial deployed reader stores Gmail message identifiers and metadata such as sender, subject, and date in a locally hosted SQLite index. Future financial processing or attachment retention will be enabled and reviewed separately.

Storage and access

OAuth credentials and the local message index are held on infrastructure administered by the account owner rather than on this public website. Access to those resources is restricted to the owner and the necessary connector process. This public Cloudflare Pages site contains only informational pages and does not collect Gmail messages or OAuth tokens.

Sharing and transfers

The application is not designed to sell Google user data, share it with advertisers, or make the mailbox available to the public. Gmail data may be processed by the account owner's private application infrastructure for the stated financial-organization purpose. No third-party AI analysis of email contents is enabled in the initial reader.

Retention and deletion

Message metadata remains in the local index until removed by the account owner. The owner can delete the local index and any subsequently retained financial documents. Deleting local files does not itself revoke Google OAuth authorization.

Revoking access

The owner can revoke access through Google Account third-party connections and can delete the application's local OAuth credentials and stored data. Revoking access prevents further authorized Gmail API requests using that grant, but does not automatically erase data previously indexed locally.

Security

The connector uses Google OAuth rather than storing a Gmail password. Local OAuth credentials are restricted to the connector's protected storage. As with any self-hosted service, the owner remains responsible for device, network, backup, and access security.

Contact

Questions and requests about this application or Google user data can be sent to neachcuideachaidh@gmail.com.