Privacy policy.

With Google authorization, AIOS accesses connected-account information and selected Gmail messages. This includes message and thread identifiers, sender and recipient details, subjects, timestamps, mailbox labels, read status, short snippets, message bodies and relevant attachments.

• Display connected Inbox and Sent views, and retrieve messages for live reading.
• Classify or summarize email and prepare drafts in an authorized AI-assisted workflow.
• Extract structured receipt and billing facts for subscription review.
• Carry out explicit archive or mark-as-read actions, and separately approved email sends.
• Deliver configured priority-mail alert summaries and prepare their queued Calendar reminders.
• Maintain sync state, review decisions and operational activity records.

The application database stores account settings, identifiers, sender and recipient information, subjects, timestamps, labels and read status, and snippets of up to 200 characters. It also stores draft references and brief notes, structured billing facts, source references, review decisions, approval records and activity logs.

Message bodies are retrieved live when needed. The mailbox mirror and billing collector do not store full message bodies in their database tables. Draft message bodies are stored in Gmail. Authorized AI workflows may process message context outside Gmail; their providers and local session tools have separate processing and retention controls.

Google provides the connected mailbox. Vercel hosts the AIOS dashboard, GitHub Actions runs the scheduled billing collector, and Neon stores its operational records. These services process the information needed to provide those functions.

When AI assistance is authorized, relevant context may be sent to the configured assistant or model providers to summarize, classify or prepare a draft. The operator’s policy limits this processing to the requested AIOS feature.

When configured priority-mail alerts are enabled, limited Gmail-derived alert summaries and message receipt times may be delivered to the operator through Telegram. Related reminder details may be sent to Google Calendar when a queued action is executed under the configured standing authorization.

AI Future Studio’s operating policy requires information received from Google APIs to be used in accordance with the Google API Services User Data Policy, including its Limited Use requirements.

That policy permits Google information only for the requested, visible AIOS features. It prohibits selling that information, using it for advertising or data brokerage, and using it to train or improve general-purpose AI models. AI service configurations must support this commitment before Google context is processed through them.

• Google API Services User Data Policy
• Google Workspace user data and developer policy

The Inbox and Sent message index uses a rolling 90-day window. That window does not apply to every AIOS record. Attention records, draft references, billing evidence, decisions, approvals and activity records are separate stores and remain until removed through an operator-managed process. Provider logs, backups and assistant-session records have their own retention controls.

Use AIOS Email settings to control connected mailboxes and folder mirroring. Remove the app’s access in your Google Account to stop future Gmail API access.

Revoking access does not automatically erase existing AIOS records. Request deletion of AIOS-held records at phil@aifuturestudio.com. Deletion is handled manually for the relevant stores; this app does not offer an automatic delete-all control.

• Google’s connected-app controls

AIOS is restricted to its operator. Gmail connects through Google OAuth; the app does not receive the Google account password. OAuth credentials are kept outside application data tables in local and hosting environment settings.

Contact phil@aifuturestudio.com about access, processing or deletion. Changes to this policy are reflected on this page with an updated date.