Who operates the application
Moore's Automation is a private invoice-processing application operated for Moore's CVR. Privacy enquiries and requests can be sent to moorescvr@gmail.com.
Google account and Gmail data accessed
The application is authorised only for moorescvr@gmail.com. It uses the Gmail API to search for messages from configured suppliers, read message identifiers, dates, sender and recipient information, headers and authentication results, and retrieve PDF invoice attachments.
The OAuth permission requested is https://www.googleapis.com/auth/gmail.modify. That permission technically permits Gmail message modification. The deployed application currently uses it only to list and retrieve messages and attachments. It does not change message contents, read state or labels, delete messages, or send email.
Gmail label modification may be introduced later to mark processing status. It is not currently active. Before any such feature is activated, this policy and the application homepage will be updated to disclose which labels are created or changed, when changes occur, and how they can be reversed.
Why the data is used
Google user data is used only to identify genuine supplier invoice emails, validate their origin, obtain the attached invoice evidence, prevent duplicate processing, support review and audit, and—only when the separately controlled production workflow is enabled—prepare invoice records for Moore's CVR's internal accounting process.
The application does not use Google user data for advertising, marketing, profiling, sale, or unrelated purposes.
Data stored
The application may store Gmail message and attachment identifiers, sender and recipient details, message dates and authentication evidence, original PDF invoice attachments and their cryptographic hashes, extracted invoice details, processing status, error and audit records, and OAuth credentials.
OAuth client and refresh credentials are encrypted using Windows Local Machine Data Protection API protection on the service host. Access tokens are short-lived and are not deliberately stored as plaintext. Logs are designed to exclude OAuth tokens and client secrets.
Original PDF evidence is written to an access-controlled local spool. When the production workflow is enabled and validation succeeds, invoice evidence and associated processing records may also be stored in Moore's CVR's private NAS archive and PostgreSQL invoice database. Failed, conflicting and duplicate evidence is preserved for human review rather than silently discarded.
Retention and deletion
There is currently no automatic fixed deletion period. Invoice documents, source evidence, hashes and audit records are retained for Moore's CVR's accounting, duplicate-prevention, troubleshooting and legal-record purposes, and until they are manually reviewed and deleted under Moore's CVR's record-management decisions. Revoking Google access stops future API access but does not automatically delete evidence already retained for those purposes.
For a request concerning retained information, contact moorescvr@gmail.com. A request will be assessed against applicable accounting, legal and operational retention requirements.
Sharing and transfers
Google user data is not sold and is not shared for advertising. It is processed only by Moore's CVR and the infrastructure needed to operate the private workflow, including Google's Gmail service and Moore's CVR-controlled Windows, NAS and database systems. Information may be disclosed where required by law or where necessary to establish, exercise or defend legal claims.
The public pages themselves may be served through Cloudflare. They contain no Gmail or invoice data, and the OAuth application does not send Gmail content to the public website.
Security
The application restricts mailbox identity, supplier senders and authenticated-message checks; protects stored credentials and local spool data with operating-system access controls; uses cryptographic hashes to verify invoice evidence; and separates Gmail intake from database and live invoice-commit safety gates. No system can guarantee absolute security, but access and processing are limited to the private business purpose described here.
Your choices
The Google account owner can revoke the application's access through Google Account security settings. Questions, access requests, correction requests and deletion requests may be sent to moorescvr@gmail.com.
Changes to this policy
This policy will be updated before Gmail label modification is activated and whenever the application's Gmail access, data uses, storage locations, sharing or retention practices materially change. The revision date above will be updated at the same time.