Privacy Policy

Purpose and scope

Britannia AI Agent Dev is a personal-use development application restricted to one approved Google account. This policy explains how the application handles Google account data, Gmail data, Calendar data, and Drive data when that user connects the application.

Data accessed

The application requests only:

• basic Google identity information: account identifier, email address, and profile;
• Gmail read-only access to search and read messages and threads;
• access to read and create events on calendars owned by the approved user, intended for bounded event-window reads and explicit approval-gated creation of one timed event on that user's primary calendar.
• Google Drive read-only access to search existing file metadata and read bounded text content from one unambiguous matching file.

Google's owned-event Calendar scope can technically permit event changes and deletion. This application exposes no route to update, move, or delete an event, create recurring or all-day events, or invite attendees. It does not request permission to create drafts, send email, modify messages or labels, or create, modify, delete, move, share, or publish Gmail or Drive data.

How data is used

Google identity data is used to authenticate the approved user and link that identity to the user's Discord account. Gmail data is accessed only to fulfil an explicit request from that user, such as searching for or summarising email.

Calendar data is used only for explicit, bounded requests to view events on the approved user's owned primary calendar, or to prepare one timed event for the user's review. The event is created only after the user sends a separate confirmation containing the exact approval identifier. Drive data is used only for explicit requests to search existing files or read bounded text from one unambiguous match.

When the user requests an AI-generated answer or summary, limited Gmail excerpts, Calendar event fields, Drive file metadata, or bounded Drive text needed for that request may be sent to a configured model service solely to generate the requested result. Gmail and Calendar use Google Cloud Agent Platform; Drive uses the configured BSL model gateway. Google user data is not sold, used for advertising, or used by this application to train general-purpose AI models.

Data stored

• Google and Discord account-link identifiers;
• the approved Google email address and granted OAuth scopes;
• an encrypted OAuth refresh token;
• an encrypted Calendar event approval containing its title, time, and optional location;
• security and operation audit events.

Gmail search text, sender and recipient addresses, subject lines, and message bodies are not stored in audit records. Raw Gmail message and thread identifiers are not stored in audit records. Calendar titles, descriptions, locations, attendees, conference links, and event identifiers are not stored in audit records. Drive search text, file names, file content, raw file identifiers, and opaque file references are not stored in audit records; a keyed hash identifies an audited file read. Gmail and Drive content and Calendar content read from Google are not persisted in the application database. A proposed Calendar event is stored only in its encrypted, identity-bound approval record.

Retention and deletion

Gmail, Calendar, and Drive audit events are retained for up to 90 days. Account-link and encrypted credential data are retained while the connection remains active. A Calendar approval can be used for only ten minutes; after confirmation, cancellation, expiry, or an execution result, it becomes terminal and cannot be reused. Its encrypted approval record is retained while the account connection remains active. The user can request deletion using the support email displayed on the Google OAuth consent screen.

Security

OAuth refresh tokens are encrypted before storage. Access is restricted to the approved account. Gmail and Drive permissions are read-only. Calendar creation requires a separate, identity-bound approval that expires after ten minutes and is atomically consumed before one creation attempt; the application does not retry that provider call. Sensitive tokens are not placed in application logs or this public website. Drive file identifiers are represented by short-lived, identity-bound opaque references. No security measure can guarantee absolute protection, but the application limits exposed operations and stored data.

Sharing

Data is not sold or shared for advertising. Data is disclosed only to service providers necessary to operate an enabled user-requested feature, including Google OAuth, Gmail API, Calendar API, Drive API, Google Cloud Agent Platform, and the configured BSL model gateway, subject to their applicable terms and privacy commitments.

Your controls

The user may revoke access at any time through Google Account connections. Revocation prevents future Gmail, Calendar, and Drive access. The user may also contact the developer through the support email shown on the OAuth consent screen to request deletion of locally stored account-link and credential data.

Changes

This policy will be updated before the application requests broader Google permissions or materially changes how Google user data is handled.