Scope and operator
IBKR email trigger demo is a personal utility operated solely for the Google account owner who authorizes it. It is not offered to the general public.
Google user data accessed
The application uses the Gmail API with the gmail.readonly and gmail.send OAuth scopes. It receives mailbox history identifiers, retrieves message metadata, and retrieves the raw content of messages that match configured IBKR execution-alert criteria. It uses Gmail send access only to send a simulation report to the same authorized mailbox.
How data is used
Message content is used to authenticate and parse qualifying IBKR execution alerts, extract normalized execution details, prevent duplicate processing, generate a simulation-only order-request preview, and report failures. The current deployed application does not submit an order or call an external trading API.
Data stored
The application stores operational records in a private Google Cloud project. These records can include Gmail message identifiers, hashes of raw messages and RFC message identifiers, Gmail history checkpoints, normalized execution fields, authentication results, deduplication and audit records, and generated report-delivery state. Raw email bodies, OAuth access tokens, passwords, and brokerage account numbers are not stored in the operational database or application logs. OAuth client credentials and the refresh token are stored in Google Secret Manager.
Sharing and sale
Google user data is not sold, rented, used for advertising, or shared with data brokers. Data is processed using Google APIs and services in the owner's Google Cloud project. A simulation report is sent only to the same Gmail account that authorized the application. The current deployment does not transmit Google user data to IBKR, Tradovate, NinjaTrader, or another trading venue.
Retention and deletion
No automated retention schedule is currently configured. Operational records remain in the private Google Cloud project until the owner deletes them. The owner can stop future access at any time by revoking the application's Google Account access and can delete stored records, secrets, or the project through Google Cloud.
Security
The application uses least-privilege service accounts, private cloud service endpoints for mail processing, encrypted Google-managed storage, sender allowlists, email-authentication validation, deduplication, and redacted logging. No system can guarantee absolute security.
Google API Limited Use
The application's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Changes and contact
This policy will be updated if the application's data practices materially change. The owner can be contacted using the support email displayed on the Google OAuth consent screen.