EatherBack to Eather ↗
Eather / Your information

Privacy Policy

How your information moves through Eather, what is saved, and the choices you have.

Last updated: October 17, 2026 · Applies to eather.ai

Connected apps are optional and read-only. When you allow an app in chat, relevant information can be sent to the AI service answering your question.

Your chat history is saved in this browser. Sending a message still involves server processing. Turning off new retrieval does not remove information already in a conversation.

Who we are

Eather is an AI chat service operated by Eather. This policy covers Eather's website, its account connections, and its hosted API. It describes the current service; an available connection may still require setup or approval from its provider or your school.

Eather uses your information to answer your requests, maintain your sign-in, manage access and usage, operate optional connections, process purchases, and respond to support requests.

Information we handle

  • Account information: your sign-in email, verification records, session credentials, subscription or access status, and usage-credit balance.
  • What you submit: messages, selected conversation history, optional memory or conversation summaries, attached text and images, and files or audio you ask Eather to process. File contents may be extracted in your browser before relevant content is submitted.
  • Connection information: the app you authorize, its permission grants, encrypted access and refresh tokens, your connection settings, and information retrieved for your request.
  • AI/API credentials: provider keys you save, your selected model and settings, and hashes and limited display details for Eather API keys you create.
  • Service records: request counts, rate-limit identifiers, feedback, diagnostic events, and purchase or delivery records. Hosting and service providers also receive normal network information, such as IP address and request metadata.

Sign-in information, preferences, conversations and optional memory are stored in browser storage. A short-lived security cookie is also used when you authorize a connection. The app's service worker caches icons and installation assets.

Connected apps

You choose which accounts to authorize. Current readers access the following information to answer your questions or let you select sources:

ConnectionInformation used
GmailMatching email subjects, senders, dates, message text or snippets, and message links. The reader does not download email attachments.
Google CalendarEvents from your primary calendar, including titles, times, descriptions, locations and event links.
Canvas LMSPlanner entries, course names, due dates, available descriptions and assignment links from your authorized school.
CanvaDesign identifiers, titles and links. The reader does not retrieve the contents of design pages.
CleverIdentity information returned for your account, such as user ID, type, name and district. This does not provide access to every app in Clever.
Edia / school portalThe homepage shortcut you save and any files you choose to upload. These cards do not automatically sign in to or read those sites.

These account readers do not send email, edit events, change school records or submit assignments. Eather stores the authorization tokens supplied by the service; it does not ask you for that service's password.

With Apps: Auto and Allow in chat enabled, relevant excerpts may be retrieved when you ask a related question. They are added to the AI request. Replies, source links and read-status information can remain in your saved chat. Sources you attach yourself become part of its content.

AI and service providers

Eather sends your request, relevant conversation context and any selected or retrieved content to the service handling that task. An answer-review option can make another call using the draft and its context. A configured backup may also receive that information if the first model fails.

  • AI processing: depending on your selection and the operator's configuration, requests may go to Groq, OpenAI, Anthropic, Google Gemini, Cloudflare Workers AI, OpenRouter and its routed model provider, or an operator-approved compatible endpoint. A model connected with your own API key uses that provider account.
  • Hosting and storage: Cloudflare runs the application and its server-side data stores. Image-generation prompts may also be processed by Cloudflare Workers AI.
  • Email: Resend processes the recipient address and contents needed to deliver sign-in codes and account or purchase emails.
  • Payments: Stripe processes checkout and payment details. Eather receives information needed to grant plans or credits, including the purchaser email, purchase identifiers, amount and payment status. Full payment-card details are handled by Stripe's checkout.
  • Web features: when enabled, ordinary web research may send search queries to Serper, Brave Search or Tavily, and fetch pages from their publishers. Connected-account retrieval turns off Eather's web-search tools for that request. The main app may load fonts from Google Fonts and document-processing libraries from cdnjs; those hosts receive ordinary resource requests.

Provider account settings and applicable terms affect processing and retention. Eather does not control a provider's entire infrastructure. For Google account data, the restrictions below apply to permitted processing and transfers. Information may be processed in the countries where these service providers operate.

Google data and Limited Use

We commit to handling information received from Google APIs in accordance with the Google API Services User Data Policy and the Google Workspace Limited Use requirements.

Gmail and Calendar information is used for the visible features you authorize, such as finding an email or summarizing your schedule. Relevant content is transferred to an AI processor to provide your requested answer. Google data is not sold, used for advertising or credit decisions, or used to train general-purpose AI models. Eather has no general-purpose model-training feature.

Human access to Google data is limited to your specific permission, necessary security investigations, legal obligations, or policy-permitted internal use of aggregated, anonymized data. These commitments also apply to information derived from Google data and to permitted service providers.

Storage and retention

  • Chats and preferences: remain in browser storage until you delete them or clear the site's data. Optional summaries and memory can also remain there. Conversations are not automatically synced between your devices. Sending context to an AI provider is separate from this local storage.
  • Connections: saved tokens and provider keys are encrypted in Eather's server database. Connection metadata, such as service names and preferences, is also stored. These records remain until removed through the app or by the operator. Revoking access at a provider may leave an unusable saved record until you disconnect it in Eather.
  • Login and API access: email sign-in codes expire after ten minutes. A verified session can last up to a year. OAuth setup records expire after ten minutes and are removed when used or during later cleanup. Eather API keys expire after ninety days and can be revoked sooner.
  • Feedback and operations: written feedback is stored for up to sixty days in the app's active store. Feedback ratings and usage totals help operate the service. Some aggregate totals have no automatic expiry. Certain mail and provider diagnostics expire after thirty days, while undelivered purchase-email records can remain for up to ninety days.
  • Billing and access records: plan, credit and purchase records are retained as needed to supply access, reconcile purchases and handle support. Some do not expire automatically. Deletion requests are reviewed for any records still required for billing, security or legal obligations.

Deleting information from Eather's active records does not instantly erase a service provider's logs, backups or records of earlier processing. Their retention arrangements apply. Eather uses encrypted connections and protects saved connector credentials, but cannot guarantee that any service is completely secure.

Your choices

  1. Stop new retrieval: choose Apps: Off or disable Allow in chat for an app in Connections.
  2. Disconnect an account: use Connections → Disconnect. This removes its saved connection credentials, metadata and pending authorization records from Eather's active database. You can also revoke Eather in the provider's account settings, including Google Account connections.
  3. Remove local conversations: delete a chat or use Settings → Delete all my chats. Clear the site's browser data to remove other local state, including saved memory and sign-in. Repeat on each device where you used Eather.
  4. Manage API access: revoke Eather API keys in Connections. Removing a connected AI provider also removes the Eather API keys tied to that provider profile. You can revoke the underlying provider key with its issuer.
  5. Request help with your data: contact us below to request access, correction or deletion. We may need to verify control of the relevant account before making changes.

Turning an app off or disconnecting it does not remove data already included in a saved chat or undo earlier provider processing. Start a new chat to avoid sending earlier conversation content again. Deleting Eather data does not cancel a subscription or delete the original records in Gmail, Canvas or another connected service.

Only connect accounts and submit school records you are authorized to use. Parents, guardians and school administrators can contact us about a student's information, including an access or deletion concern. A school may require separate authorization before its tools can be connected.

Contact and privacy requests

Operator: Eather

Email: support@aetherhq.xyz

For a request, tell us which Eather account and information are involved. Do not send passwords, access tokens or API keys. Written feedback in the app is visible to the operator; avoid putting private source content in it unless you intend to share that content for support.

We may update this policy as the service changes. The date above identifies this version. Material changes to connected-data use will be explained before that new use, with renewed permission where required.