Privacy policy

Prepared 4 November 2026. Operator: Louis Evan.

Purpose and access

This personal application reads the owner's Gmail account to identify financial receipts and reconcile them with a private ledger. Google's read-only permission technically allows reading the mailbox; the finance process uses a bounded financial-email search. It does not have permission to send, edit or delete email. Mailbox change notifications include the authorized email address and a history identifier.

Information processed

The application processes financial-email contents, sender-authentication results, message identifiers, dates, amounts, account aliases, merchant descriptions and evidence hashes. Original selected financial messages are retained privately for audit and reconciliation, including personal information contained in those messages. Unsupported or ambiguous evidence is held for review rather than treated as confirmed spending.

Storage and service providers

Google Gmail and Cloud Pub/Sub provide mailbox access and change notifications. Processing runs on the owner's Windows computer. Google credentials are encrypted for that Windows user; private Site service credentials are held in memory. Evidence is stored in the owner's local or Google Drive archive and private Cloudflare R2 storage. The private ledger and review application use the owner's Sites service and Cloudflare storage. Authorized owner tools can access those private records. The paired widget receives aggregate budget, spending and freshness information.

Use and disclosure

Data is used for the owner's financial reconciliation, review and widget updates. The application does not sell Google user data, use it for advertising or make financial records public. The application's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. Access by the owner or an explicitly authorized assistant remains subject to the owner's instructions and the connected services' controls.

Retention and controls

Selected evidence and ledger history are retained for reconciliation until the owner requests their removal; no automatic deletion period is currently configured. The owner can revoke Google access through the Google Account permissions page, stop the local receiver and revoke paired widget access. Revoking authorization prevents future access but does not automatically delete already archived records. Deletion requests must also address stored evidence, ledger records and applicable backups.

Contact

Questions, access or deletion requests: louisevanmoniaga@gmail.com.