ACCOUNT PRIVACY

Privacy Policy

Last updated: October 31, 2026 · English

This policy describes the information handled by the current Aether AI Workspace at aether-ai.bbroot.com. The workspace operator can be contacted at adarsha.kharel99@gmail.com.

Information used for your account

When you choose Google sign-in, Google provides basic identity information to Supabase, our authentication provider. This can include your name, email address, Google account identifier, and profile-picture information. Aether uses your authenticated account to identify your own profile. We request the basic openid, email, and profile permissions; we do not request access to your Google Drive, Gmail, contacts, or calendar.

Supabase Auth stores your account and identity information. Aether’s profile table stores your account identifier, editable display name, product-update preference, and profile creation/update timestamps. The product-update preference starts turned off.

If you use the optional email/password method, your credentials are handled by Supabase Auth. Aether does not store a copy of your password in its profile table.

How account information is used

To sign you in, maintain your session, and identify your account.
To display and save your profile name and product-update preference.
To restrict profile access to the appropriate signed-in account and support account security.
To respond when you contact the workspace operator about your account.

The current app stores the product-update preference but does not include an automatic marketing-email service. It includes a Paddle billing integration that becomes available after the workspace operator completes merchant setup. When payments are not configured, the app explains that payments are unavailable.

Payments and subscription information

When the operator has enabled a configured payment account and you choose a paid subscription, Aether sends your account email and account identifier to Paddle to link your purchase. The account identifier is included in purchase metadata. Paddle provides the checkout and handles the payment information you enter there. Aether does not store card numbers or bank details in its account database.

Aether stores private links between your account and Paddle customer, checkout/transaction identifiers, subscription status and billing-period information, webhook/adjustment receipt identifiers and timestamps, and payment-block identifiers and covered-period timestamps. It does not persist raw adjustment payloads. This information is used to show billing status, open your customer-specific billing portal, prevent duplicate processing, and determine your app allowance, including changes resulting from a verified refund or dispute. The browser cannot write paid subscription status. Paid access changes only after the server verifies provider information; a checkout return URL or browser completion event alone does not grant it.

Sandbox checkout is visibly identified and does not move real money or grant live Pro allowance. Live subscriptions can renew under the terms and interval presented in Paddle checkout. Use the billing portal to manage or cancel your subscription, or contact the workspace operator for help. Closing checkout, signing out, removing Google access, or deleting an Aether account does not cancel an existing Paddle subscription. Cancel through the billing portal before requesting account deletion.

The operator must publish accurate commercial terms, support/contact information and a refund policy before opening live sales. This privacy page does not set a refund period or promise an automatic refund. Paddle processes financial information under its applicable terms and Privacy Policy.

Browser storage and demo features

Aether uses browser storage for its authentication session, selected language, theme, signed-out demo profile, and locally created demo projects. Session credentials are used by Supabase to keep you signed in. Signing out ends the app session; it does not delete the account record. A selected billing cycle and account reference may be kept in this browser tab to continue checkout after sign-in. This choice is accepted for up to 15 minutes and is cleared when used or canceled.

Analytics and activity history shown in the dashboard are sample data. Demo projects are not automatically uploaded to your signed-in profile. Chat messages remain in the current page’s memory rather than being saved in browser storage or the account database. Starting a new chat or changing accounts clears the temporary conversation; reloading the page also clears it.

You can remove browser-local preferences and demo data by clearing this website’s storage in your browser. This does not delete information stored in Supabase.

AI chat requests

AI chat uses Google’s Gemini API when the workspace operator has configured its server-side API key. Chat requires a signed-in account. If the provider is not configured or a request fails, Aether shows a setup or error message instead of generating a sample answer.

When you send a message, Aether sends that message, a limited amount of recent conversation history, and the selected language through a Supabase Edge Function to Gemini. The function verifies your session and applies request limits. A temporary service failure can cause one automatic retry to the same provider. It does not automatically include your account identifier, email, profile, demo projects, or dashboard analytics in the model request. Information you type into the conversation is included in the request.

Aether does not save chat content in its database or intentionally log message content in its chat function. It stores private per-account request counters and time windows. Starter allows 100 requests per day; an eligible, server-verified live, active and unexpired Pro subscription allows 1,000 per day. A verified full refund or dispute can remove the higher allowance for its covered billing period. Both plans have a 10-per-minute limit, and daily windows reset at midnight UTC. Sandbox subscriptions do not increase actual AI allowance. Those limits are separate from the dashboard’s sample usage charts. A submitted request can count toward the limit even if the provider cannot complete it.

Google processes the prompts and responses under the operator’s Gemini API service terms and account configuration. Data use and retention differ between unpaid and paid services; under the unpaid-service terms, content may be used to improve Google products and reviewed by people. Avoid sending confidential, sensitive, or personal information. See the Gemini API Additional Terms for the applicable details. This app does not promise that providers retain no request content.

Service providers and data access

Aether is hosted through Sites. Google supports Google sign-in and provides Gemini responses. Supabase provides authentication, the account-profile database, private request counters and billing metadata, and the server functions handling chat and billing requests. Paddle provides payment checkout, subscription processing and the customer billing portal when configured. These providers handle information necessary to operate their services and may process technical request and security logs.

The Supabase account database for this workspace is hosted in the Mumbai region. Providers may process chat, technical, and authentication information in other locations under their own service terms and privacy policies. See Google’s Privacy Policy and Supabase’s Privacy Policy.

The app’s database access policies restrict profile reads and updates to the profile’s authenticated owner. Private billing records are handled through authenticated server functions and verified provider notifications rather than direct browser writes. The workspace operator and authorized database administrators can manage account and billing metadata through Supabase. The current app has no advertising integrations or public directory of user profiles.

Retention and your choices

Active account records remain in Supabase until the workspace operator removes the account; no automatic account-deletion schedule is currently configured. Removing the Supabase authentication account also removes its linked Aether profile, request-counter record and linked billing metadata from the active database. It does not cancel the separate Paddle subscription or delete Paddle’s financial records. Cancel the subscription before deleting the app account. Paddle records, service-provider logs and backups follow the applicable providers’ retention policies. The request-counter record is reused as its time windows change; it is not a saved conversation history.

You can edit your display name and product-update preference in Settings. To request access, a correction you cannot make yourself, or account deletion, contact adarsha.kharel99@gmail.com. You can also manage Aether’s Google access in your Google Account connections. Removing Google access does not by itself delete the existing Supabase account or its saved profile.

Changes and contact

This page describes the current account, AI chat, payment integration and demo features. If Aether’s data handling changes, this policy should be updated to reflect those changes. For privacy questions or requests, email adarsha.kharel99@gmail.com.