AI Inbox Triage Privacy Policy
Effective date: October 6, 2026
AI Inbox Triage is operated by Tech Future LLC ("we," "us," or "our"), 30 N Gould St, Ste R, Sheridan, WY 82801, USA. This policy explains how we handle information in the AI Inbox Triage web application during its pilot phase. Contact us through our Contact page.
At a glance
- Gmail access is read-only. We do not send, draft, label, archive, delete, or otherwise modify your Gmail messages.
- We process recent email to identify conversations that may need a reply. Some email content is processed temporarily on our servers.
- We store selected metadata and encrypted contact details, subject hints, and short classification reasons. We do not persist full email bodies in our application database or application logs.
- After you accept the Gmail and AI disclosure, limited message excerpts may be sent to OpenAI. Provider retention is separate from our application's storage practices.
- We do not sell your information or use it for advertising. You can turn off AI processing at any time in Settings, stop all Gmail and AI processing by disconnecting Gmail, or delete your account yourself in Settings.
1. Scope and purpose
This policy covers the pilot web application and information accessed through Google APIs. It does not govern Google's services or third-party websites you visit using links in the app. AI Inbox Triage helps identify recent conversations that may require your attention; its recommendations do not send replies or take actions in Gmail.
Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements, and the applicable Google Workspace user data and developer policy. We use Google data only to provide or improve the appropriate user-facing features described here, subject to those restrictions. Pilot status does not change these commitments.
2. Information we collect
Account information: When you sign in with Google, we receive your Google account identifier, email address, and display name. We use this information to identify your account and maintain your session.
Gmail information: After you separately authorize Gmail access, we read recent message metadata, including sender, recipients, subject, date, message and thread identifiers, and labels. For classification, we may temporarily retrieve the latest relevant message. We request the message in full format to extract text; we do not make separate attachment-download requests. A full-format message may include inline MIME content.
Stored email-related information: We retain message and thread identifiers, dates, conversation direction, and a cryptographic fingerprint for detecting duplicates or changes. We also retain encrypted contact addresses and display names, truncated subject hints, and short AI-generated reasons used in your prioritized list. These remain personal information even when encrypted. We also retain connection status, granted permissions, synchronization state, and encrypted mailbox addresses or available aliases used to determine conversation direction.
Preferences and actions: We record your time zone, working days, digest settings, ignored senders or domains, and actions such as Done, Snooze, Dismiss, and classification corrections. We use these to reflect your choices and preserve your corrections in the list.
Consent and operational records: We record disclosure versions, consent and withdrawal timestamps, security events, processing outcomes, and delivery status. Application request logs contain limited operational fields, such as request identifier, route, method, status, timing, account identifier, and task label. They exclude email bodies, subjects, contact details, authentication tokens, and session identifiers. Infrastructure providers may separately process technical information needed to operate and secure their services.
Support information: If you contact us, we receive the information you submit, including your name, email address, and message. Please avoid including unnecessary email content or sensitive information in support requests.
3. Gmail permissions and processing
We request Google sign-in permissions (openid, userinfo.email, and userinfo.profile) and the gmail.readonly permission. Gmail's read-only permission is broader than our application's scan limits: our software limits the initial scan by a recent date range and a message-count cap, excludes Spam and Trash, and then checks incrementally for new activity.
We use metadata to determine direction and recency. Where message text is needed for classification, we process it in server memory, convert HTML to text where needed, attempt to remove recognized quoted reply history, and truncate it before sending an excerpt for AI classification after you accept the Gmail and AI disclosure. We do not write full email bodies to our application database or application logs. Short derived reasons may still contain information from the underlying email.
Email content may contain personal or sensitive information about you, correspondents, or other people. Removing formatting and shortening an excerpt does not anonymize it. Each classification uses the relevant account's conversation; we do not combine mailboxes from different app accounts in a classification request.
4. How we use information
We use information to authenticate you; synchronize recent mail; identify and prioritize conversations; display your list; reflect your preferences and actions; deliver a daily service digest when delivery is configured; provide support; and maintain security and service reliability. Daily digest emails contain counts and a link to the app, not sender names, subjects, or message content. Connected accounts may receive digests on a default schedule without a separate email opt-in. You can change the time and working days in Settings; selecting no working days disables scheduled digests.
We do not sell information, serve advertisements, build advertising profiles, or use Google data to train or improve generalized AI models. Any personalization based on your feedback is limited to your own user-facing experience.
5. AI processing and consent
Deterministic rules handle conversations they can classify. The current pilot connection flow presents a combined Gmail and AI disclosure for your affirmative acceptance before Google authorization. Ambiguous conversations may then be sent to our current AI provider, OpenAI. The request contains a length-limited, normalized excerpt of selected message text, the time elapsed since the last incoming message, and classification instructions. We do not export your mailbox or separately download attachments for this feature. An excerpt may contain a complete short message and personal information included in its text.
OpenAI returns a structured classification, a short reason, and a suggested action category. These are recommendations for you to review. The feature does not execute tools or act on your mailbox. If AI is unavailable or no active AI consent is recorded, the app uses a conservative rules-only fallback. You can switch to rules-only mode at any time by turning off AI processing in Settings > Data & privacy.
We send API requests with store=false and have not opted into sharing API data for model training. OpenAI's standard API terms do not use API content for model training unless the customer opts in. We do not currently have confirmed Zero Data Retention for this service. The store=false setting does not itself eliminate all provider retention.
Under OpenAI's standard practices, abuse-monitoring logs may include inputs and outputs and are generally retained for up to 30 days, with longer retention possible where required by law or reasonably necessary to prevent harm. Endpoint, model, and feature-specific processing may also involve temporary storage or caching. Details are available in OpenAI's data controls documentation: https://developers.openai.com/api/docs/guides/your-data.
You can withdraw consent for each purpose separately in Settings > Data & privacy. Turning off AI processing stops new excerpts from being sent to OpenAI; your mailbox stays connected and your list continues in rules-only mode. Reasons already shown for existing items remain until that conversation is next re-evaluated. Withdrawing Gmail processing consent disconnects Gmail as described in Section 8, which also ends AI processing. Neither action recalls information already sent to OpenAI or guarantees immediate deletion of its retained records. A request already in progress when you withdraw may finish processing.
6. Service providers and other disclosures
We share information only as needed to operate the service, subject to applicable restrictions:
- Google provides sign-in and Gmail authorization and responds to authorized API requests.
- OpenAI receives the excerpts and instructions described in Section 5.
- Our application hosting and database provider handles the account, mailbox-derived, and technical data needed to host the application, store its data, and run background processing.
- Our digest delivery provider receives your email address and digest counts when a daily digest is sent.
- Our transactional email providers deliver contact-form submissions containing the name, email address, and message you enter. A fallback provider may be used if the primary provider is unavailable.
- Google Analytics, provided by Google, receives the website usage information described in Section 10 when you accept analytics cookies on our public pages. It does not receive Gmail data.
We may disclose information where necessary for security or to comply with applicable law. Any disclosure of Google user data remains subject to Google's applicable data-use restrictions. A general business purpose does not override those restrictions.
If a merger, acquisition, or sale of assets involves transferring Google user data, we will obtain your explicit prior consent as required by Google's policy. Any transfer of other personal information will remain subject to applicable law and disclosed privacy commitments. We do not treat notification alone as consent where consent is required.
7. Retention
Full email bodies: Processed temporarily in our application server memory, not persisted in our application database or application logs. Excerpts sent to OpenAI are subject to Section 5.
Synced Gmail metadata and derived items: Retained while your connection remains active to support your list, with no automatic age limit while connected. We attempt deletion from our active application database on disconnection; failed or interrupted cleanup is retried by the scheduled retention process. Cleanup is also scheduled when we detect that authorization requires reconnection.
OAuth refresh token: Retained while connected and removed from our active application database when you disconnect; we also request revocation of the Google authorization.
Account and non-mailbox settings: Retained until you delete your account. Disconnection preserves your account, time zone, working days, and digest-time settings. Mailbox-related feedback is deleted during mailbox cleanup. Ignored sender and domain preferences are cleared when no active mailbox remains. A minimal connection-history record remains; a connection requiring reconnection also retains its mailbox address and permissions metadata.
Consent history: Retained after Gmail disconnection to document consent and withdrawal. On account deletion, we delete this history unless a specific legal obligation requires limited retention. Any retained record is restricted to that purpose and kept only as long as required.
Application operational records: Scheduled for automatic deletion after 30 days. Security audit events: Scheduled for automatic deletion after 90 days. Infrastructure application logs: Currently retained by our hosting provider for 7 days. After account deletion, security audit events and operational metrics are no longer linked to your account and are deleted on this schedule. Scheduled deletion depends on the recurring cleanup process and is not an exact-to-the-second guarantee.
Support correspondence: Retained as needed to resolve and document your request, then deleted when no longer needed, subject to applicable legal obligations. Provider-held delivery records may follow the provider's applicable retention practices.
Database backups: Not currently enabled for this service. If introduced, backup retention will be no more than 30 days, and we will update this policy to describe the deletion implications.
8. Disconnection and account deletion
Disconnecting in the app stops new mailbox synchronization, removes the stored refresh token, requests revocation with Google on a best-effort basis, and attempts to delete synced messages, threads, contacts, follow-up items, and mailbox-related feedback from our active application database. Failed or interrupted cleanup is retried by the scheduled retention process; immediate completion is not guaranteed. It does not delete your Gmail messages. This action does not promise immediate erasure of records held by service providers or the consent, account, and security records described in Section 7. Withdrawing Gmail processing consent in Settings has the same effect.
You can also revoke authorization through https://myaccount.google.com/permissions. Once we detect invalid or revoked authorization, we stop further mailbox access, remove the stored token, mark the connection as requiring reconnection, and schedule mailbox-data cleanup. Revocation in Google does not itself delete your service account or submit an account-deletion request to us.
You can delete your account yourself in Settings > Data & privacy. To protect you, you must type DELETE to confirm, and you may be asked to sign in with Google again. Deletion disconnects Gmail, requests revocation of Google authorization, and immediately deletes your account and its associated data from our active application database. It also signs you out on all devices. It does not delete your Gmail messages. If you cannot use the app, you can instead submit a deletion request through our Contact page with the email address associated with your account. We may request proportionate information to verify the request. We aim to complete verified requests within 30 days and will tell you if an applicable legal exception or permitted extension affects completion. Any shorter legally required deadline applies.
Account deletion includes your account, preferences, feedback, and associated application data, subject to the limited retention exceptions described above. We will explain any information we must retain and why. Information already submitted to a provider may remain for its applicable retention period. Support correspondence is handled as described in Section 7.
9. Security and human access
We apply administrative, technical, and organizational safeguards, including encryption of stored OAuth tokens and sensitive derived fields, restricted access, limited application logging, and security audit records. Background job payloads use internal identifiers rather than message content or credentials. No service can guarantee absolute security.
We do not routinely read your Gmail content. Human access to Google user data is limited to cases permitted by Google's policy: your documented explicit consent to view specified data; necessary security investigation; compliance with applicable law; or aggregated and anonymized data used for permitted internal operations. Exceptional access is restricted, time-limited, justified, and logged. An internal approval alone does not authorize access outside these grounds.
10. Cookies and processing locations
We use a necessary session cookie for sign-in, consent, and form security, including on the public Contact page. It is opaque, HttpOnly, Secure, and expires according to our session limits. We do not use advertising cookies or cross-site tracking pixels.
With your permission, we use Google Analytics on our public pages (the home page before Gmail is connected, this Privacy Policy, and the Contact page) to understand how visitors use them. Google Analytics is not loaded until you select Accept in the cookie banner, and it is never loaded on pages that display mailbox information. If you accept, Google Analytics sets first-party cookies (named _ga and _ga_<ID>) that typically last up to two years. Google receives information such as pages viewed, the referring page, device and browser details, and approximate location derived from your IP address. We have disabled Google signals and ad personalization for this data. Your choice is stored in your browser. You can change it at any time using Cookie settings in the page footer; declining removes the analytics cookies we can access. Google Analytics never receives Gmail data.
Pilot users may be located in any country. Data may be processed or accessed internationally, subject to applicable privacy and data-transfer requirements. The application's primary hosting region is currently US West, California, USA. Authorized personnel, service providers, and their subprocessors may access or process information internationally. We limit such access to permitted service, support, security, and legal purposes, subject to applicable safeguards and the human-access restrictions in Section 9. Hosting in the United States does not mean all access or processing occurs there. Where legally required, international transfers must be supported by appropriate safeguards.
11. Eligibility, choices, and privacy rights
The pilot is intended for adults using the service for professional or business purposes. You must be at least 18 to create an account or connect Gmail. The service is not directed to children. This eligibility rule does not mean emails from adult participants cannot contain information about minors. Contact us if you believe a minor has created an account so we can investigate and remove it as appropriate.
You can change preferences, turn off AI processing, disconnect Gmail, and delete your account in Settings > Data & privacy. You can request access to, correction of, a copy of, or deletion of your personal information through our Contact page. We verify requests as appropriate and respond within applicable legal time limits. Additional rights, including any right to appeal a decision, depend on your location and applicable law. We will not discriminate against you for exercising applicable privacy rights, although withdrawing access may prevent features that require that access from working.
12. Policy changes and contact
We may update this policy as the pilot develops. We will post the revised policy with an updated date and provide notice of material changes through the app or email as appropriate. Where a change requires consent, we will obtain it before applying the change to the affected processing; continued use alone is not a substitute for required consent.
For privacy questions or requests, use our Contact page or write to Tech Future LLC, 30 N Gould St, Ste R, Sheridan, WY 82801, USA.