Privacy and Google data use
Your mailbox access has a specific purpose.
Operator: Aidan Gleeson. Updated: 23 October 2026.
Information and purpose
The intended workflow uses public tender information and, after consent, the authorized Gmail account’s identity and relevant email metadata and content. Gmail searches support duplicate-alert checks and procurement-notification processing. Send permission supports delivery of tender digests to the configured recipient. OAuth credentials and a refresh token support unattended scheduled execution.
The Gmail read permission technically permits access to the whole mailbox. Workflow searches must be limited to information relevant to tender monitoring; the app must not use unrelated personal correspondence for other purposes.
Access and sharing
Google processes Gmail authorization and email delivery. GitHub Actions is the intended cloud execution service and therefore processes data required by each run. Configured digest recipients receive the tender information selected for an alert. Authorized project administrators may access monitoring records.
The intended workflow must not sell Google user data, use it for advertising, or send Gmail content to AI model providers. No AI processing of Gmail content is part of the currently prepared workflow. Any future change requires review and an updated notice before activation.
Storage and security requirements
Client credentials and refresh tokens must be stored as GitHub Actions secrets, never in source code, this website, or workflow output. Workflow permissions must be limited to the functions required. Credential values and full Gmail message bodies must not be written to scan reports or logs.
Processing of email content should be temporary during a run. Durable history may retain tender references, alert timestamps, relevant content fingerprints, and sent-message identifiers for duplicate prevention and amendment tracking while the monitor operates. Retention and deletion of that history must be implemented and documented before launch. Gmail messages remain subject to the account owner’s Gmail settings.
Choice, revocation, and deletion
The account owner can refuse authorization or revoke access through Google Account connections. Revocation stops future authorized API access; it does not recall emails already delivered or automatically delete records already stored. Contact the operator to request deletion of retained monitoring data and removal of stored credentials.
Google API Limited Use
Project Tenders’ use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.
This information website
These static pages contain no login form, Gmail integration, analytics scripts, advertising, or application cookies. Cloudflare hosts this website and may process ordinary web-request information such as IP addresses and diagnostic records. See Cloudflare’s privacy policy.
Contact and changes
For questions or requests, email aidangleeson123@gmail.com. Material changes to data access or use must be reflected here before they take effect.