Privacy Policy
Last updated: 2026-10-20
Aino LifeOS, Aino Desktop, Aino mobile, and Aino Web Clipper are local-first productivity tools. This Privacy Policy explains what information we process when you use Aino, Aino Desktop, Aino Pro, and Aino Web Clipper.
Local notes and files
Your notes, attachments, tasks, and vault configuration are stored in folders you choose on your device or in your own sync provider, such as iCloud Drive. Aino Desktop's core editor, file management, tasks, calendar, and review features, and Aino mobile's Quick Journal, widgets, and file management features do not upload your note content to our servers.
Purchases and subscriptions
Aino mobile subscriptions and Aino Desktop one-time licenses are processed by platform billing providers or official purchase channels:
- iOS purchases use Apple App Store billing.
- Android purchases may use RevenueCat Web Billing.
- Aino Desktop one-time licenses may use the official purchase page, payment providers, and activation-code delivery.
RevenueCat helps us check subscription status, restore purchases, and unlock Aino Pro. Desktop purchase and activation flows help us issue, verify, and manage Aino Desktop Pro licenses. We may receive subscription or license metadata such as product identifier, entitlement status, expiration date, anonymized app user ID, order ID, email address, activation code, authorized device count, and purchase management URL. We do not receive your full payment card number.
AI and third-party services
Aino Desktop AI features require you to configure your own model API keys, OpenAI-compatible endpoints, or local CLI agents. When you use those features, selected note content, prompts, or context may be sent to the third-party model service or local tool you configured. Aino does not provide hosted AI inference for Desktop by default.
Gmail and the experimental mail application
Connecting Gmail is optional and requires your authorization. The following disclosures apply to Aino Desktop's experimental mail application, including optional mail AI features in builds that support them.
Google user data we access
With gmail.readonly, Aino Desktop accesses your connected Gmail address, message identifiers, mailbox labels used for inbox display and synchronization, message headers (including sender, recipients, subject and date), message bodies and attachments you open. With gmail.send, it submits the recipients, subject, body and attachments of a message you choose to send. It does not request permission to delete messages or change messages, labels or settings in Gmail.
How we use Google user data
We use this data to display and search the messages fetched into Aino, synchronize the inbox, open messages and attachments, prepare drafts, and send or reply after you review and confirm the message. We do not send messages merely because you open an email or generate an AI reply.
Email AI changes in Desktop 1.4.30-beta.1 and compatible clients
The following protections apply to this beta and compatible clients, not to older installed versions. Upgrade every device that accesses these conversations. Older conversations whose mail provenance was already lost cannot reliably be identified automatically.
Email AI uses your own API credentials on each device. Email-context conversations are limited to the official OpenAI Chat Completions endpoint (https://api.openai.com/v1/chat/completions) and Anthropic Messages endpoint (https://api.anthropic.com/v1/messages). No Aino-hosted model proxy or model billing is provided. CLI agents, custom gateways, tools and automatic background continuation are disabled for these conversations; ordinary non-email AI settings remain separate.
Attaching an email does not transmit it. Before the first authorized request in an app session, Aino shows the provider, model, actual endpoint, data categories, provider terms and storage disclosures. You must actively authorize the transfer and confirm that training and optional data sharing are disabled for this API account. Aino cannot independently inspect those provider-side settings. Authorization is not synchronized across devices; changes to the destination or API credentials configured in Aino require confirmation again. Email provenance is retained in managed histories and generated replies even if the visible context card is removed.
The request may include message text and quoted content, subject, participants, mailbox address, date, message identifiers and references, attachment names and sizes, your question, attached chat context and existing conversation history. Attachment files and mailbox credentials are not automatically included. Requests reject redirects and unexpected endpoints. OpenAI requests set store=false. OpenAI and Anthropic commercial API terms do not train on API data by default, subject to voluntary sharing and other applicable exceptions. This is not a promise of zero retention, and consumer subscriptions or CLI logins are not substitutes for commercial API terms. See the OpenAI API data controls and Anthropic commercial data policy.
Managed email AI history is protected separately from mailbox credentials with versioned AES-256-GCM encryption. Conversation titles, email snapshots, messages and generated responses are encrypted; generic labels, identifiers, times and counts remain in indexes. Compatible mobile clients also protect mail drafts and queued turns. Your vault sync provider transports these encrypted files. A 256-bit recovery key is saved separately by you, and is kept only in memory for the current app session; restarting or using another device requires entering it again. Aino cannot recover a lost key. API keys and mailbox credentials are not distributed through chat history.
Existing identifiable managed copies are migrated after confirmation, verifying encryption before replacement. Failed or cancelled unlocking preserves encrypted originals and prevents placeholder overwrites. Existing plaintext copies retain their previous format until migration succeeds. This does not erase external backups or caches retained by older software. Disconnecting a mailbox does not delete AI history. Deleting a conversation records a shared deletion marker that compatible clients honor and removes locally managed history copies; provider records and external backups follow their own retention and deletion rules. Explicitly copied or exported content must be managed separately, and already transmitted requests cannot be recalled.
Earlier versions: email AI and saved history
In builds with mail AI, the opened message can appear as context in the AI sidebar. Associating that context does not itself send a model request. When you submit an AI question with mail context attached, the context may include the mailbox address, sender and recipients, subject, date, message identifiers, references, message text including quoted text, and attachment names and sizes. This context and your question are sent to the model endpoint or CLI agent you configured to answer questions, summarize, extract tasks or draft a reply. This attachment of mail context does not include downloaded attachment contents or Google authorization credentials. A CLI agent may itself use a remote model service; running a CLI on your device does not guarantee local-only processing. You can remove the attached mail context before submitting your question. Third-party processing is subject to the selected provider's privacy and retention terms.
Mail context attached to an AI conversation and generated responses can be saved in the conversation history on your device and, for vault-backed conversations, in your vault. These conversation files are not protected by the mail credential encryption and may be synchronized by your vault's sync provider or shared with your connected devices. Their protection also depends on your device, vault and sync settings. This is separate from the mail reader's temporary cache.
How we protect and store Google user data
Aino Desktop connects from your device to Google's authorization and Gmail services over HTTPS. It uses the system browser for OAuth authorization with PKCE and state validation. The mail application does not route your messages or Google authorization tokens through an Aino-hosted mail server.
OAuth credentials, mail drafts and sending records are encrypted locally using Electron safeStorage backed by the operating system's secure storage. If secure storage is unavailable, Aino refuses to save mail credentials in plaintext. The mail reader's message cache, attachments being processed and synchronization summaries are temporarily held in memory. Attachments you explicitly save remain in the location you choose.
Retention, deletion and revoking access
Disconnecting an account in mail settings removes its local mail credentials, drafts and sending records and clears the mail cache. It does not delete messages in Gmail, files you saved, or mail content already saved in AI conversation history. You can delete those conversations in the AI interface and remove exported files yourself; copies retained by a sync provider or AI provider follow that provider's retention and deletion policies. You can revoke the Google grant in Google Account third-party connections. Disconnecting in Aino does not itself revoke that grant.
Limited Use
We do not sell Gmail data, use it for advertising, or use it to train general-purpose AI models. Aino's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Contact the privacy address below with questions about Google data handling.
Aino Web Clipper
Aino Web Clipper runs when you actively open the extension and choose to clip the current page. It may process the current page title, URL, selected text, readable article content, full-page content, and referenced images so it can create the Markdown note you requested. It does not continuously monitor browsing activity.
The extension uses Chrome local storage to keep your clipping preferences, templates, theme, Aino Desktop port, and destination folder on your device. It communicates with Aino Desktop only through the local loopback addresses 127.0.0.1 or localhost. Clipped content is written to the local vault you opened in Aino Desktop and is not sent to an Aino-hosted clipping server.
AI summary is optional and starts only when you select the summary action. The selected page content is first sent to Aino Desktop on your device. Aino Desktop may then send that content to the AI model provider or local tool you configured, according to the settings and privacy terms of that provider.
We do not sell clipped content, use it for advertising, or use it to build browsing profiles. Our use of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.
Support
If you contact support, we process the information you choose to send, such as your email address, support ID, device details, screenshots, and issue description.
Analytics
The Aino app does not require analytics to use your local notes. Only after you choose Allow analytics, the website uses Microsoft Clarity and sends anonymous conversion events to the Aino service, such as page visits, installer clicks, pricing views, purchase clicks, and quick-start completion. These events may include a random visitor ID, session ID, page path, language, referring host, and UTM campaign parameters. They do not include page content, note content, or text you enter on the page.
Trial requests, clicking the trial email link to reach the example vault download, and permanent-license fulfillment create server-side lifecycle events. The redirect event does not mean the vault was downloaded or opened in Aino. To measure trial-to-purchase conversion, these events are linked with a keyed HMAC-SHA-256 digest of the normalized email address; the growth-event table does not store the raw email address. Anonymous website analytics are off by default; declining them does not affect browsing, trials, or purchases. The server still records the trial and fulfillment events described above.
Trial usage analytics in Aino Desktop are also off by default. Only after a trial user opts in within the app do we record that choice, active app sessions, vault-open and capture/task-creation events, and server receipt times, linked by a keyed digest of the trial email. We do not send note content, file paths, or typed text. Users can turn this off at any time in the trial card to stop future events. Declining or turning it off does not affect the trial or local use.
Third-party services
If you connect optional third-party services, such as calendar providers, AI model providers, cloud storage, App Store billing, RevenueCat Web Billing, or Desktop purchase and activation services, your use of those services is governed by their own terms and privacy policies.
Contact
For privacy questions or requests, contact us at [email protected].