Privacy Policy

Last updated: September 27, 2026 • Data Protection & Google API Policy Compliance

Google API User Data Policy & Limited Use Commitment

“useaetheris.com's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.”

Explicit AI Model Training Exclusion & Zero Data Sale Guarantee

Google user data is NOT used for training AI models, sold, or transferred to third parties for advertising.

Your Gmail messages, email headers, metadata, sender information, and prompts processed by Aetheris AI are used exclusively to render real-time inbox summaries and draft responses directly for your account session. They are never ingested, leased, or disclosed to train foundation AI models or build marketing profiles.

1. Credential Security & Data Privacy After Submission

When you create an account or submit credentials on Aetheris AI, your data is safeguarded using multi-layer cryptographic protection:

Irreversible Password Hashing: Passwords entered during sign-up or sign-in are never stored in plain text. Authentication handlers utilize irreversible cryptographic hashing algorithms (Argon2 / bcrypt) before saving authentication states.
Database Row Level Security (RLS): User profiles and private workspace records are stored in Supabase PostgreSQL tables enforced with strict Row Level Security (RLS) policies. Every database operation isolates records so that only your authenticated session can access your information.
HTTPS / TLS 1.3 Transport Security: All data transmitted between your browser, our Next.js backend, and database servers is encrypted in transit using mandatory HTTPS / TLS 1.3 encryption.

2. How Tokens Are Stored in the Database

Aetheris AI manages two categories of tokens: OAuth Integration Tokens (Google OAuth access & refresh tokens) and AI Credit Usage Tokens. Both are stored with high-security safeguards:

Google OAuth Access & Refresh Tokens

When you grant Gmail access via Google OAuth 2.0, the returned OAuth access tokens and refresh tokens are encrypted at rest using server-side AES encryption and stored in isolated Supabase PostgreSQL database tables. Tokens are accessible strictly by authorized server-side integration APIs to fetch email threads or send approved drafts on your request. Third parties and unauthorized users cannot read or extract token credentials.

AI Credit Tokens & Refill Cycles

AI usage tokens (e.g. 5,000 / 125,000 / 500,000 credit allocations) represent atomic quantitative usage counters stored in your user record. Every prompt execution estimates token consumption and atomically updates your balance in Supabase. Token tracking stores numerical counter metrics only and does not expose your raw credentials or private data.

3. Google Workspace / Gmail Scope Permissions

Aetheris AI requests only the minimum necessary Google API permissions to provide autonomous email triage:

https://www.googleapis.com/auth/gmail.readonly: Used strictly to fetch incoming email messages and headers so our Google Gemini multimodal engine can generate context summaries and intent classification highlights in your private workspace.
https://www.googleapis.com/auth/gmail.send: Used strictly to dispatch drafted email replies when you explicitly initiate or confirm a response action.
userinfo.email & profile: Used strictly to identify your account session and display your primary Gmail address in your dashboard settings.

4. Data Deletion, Revocation & Contact Support

You maintain total control over your connected accounts and stored data:

You can disconnect your Gmail or Microsoft integration at any time from your settings page.
You can revoke Aetheris AI permissions directly from your Google Account Permissions page.
You can request complete account deletion and database record erasure by emailing our data protection team at: devd34427@gmail.com.

Terms & Conditions →Home Page