Privacy Policy

Aethel, a Lucin Solutions LLC product Last updated: 2026-09-17

This policy explains how Aethel handles your data. We've written it in plain language because we want you to actually read it.

The short version: Aethel runs entirely on your own computer. We don't run servers that hold your data. We don't see your calendar, your email, your Telegram messages, or anything you ask Aethel to do. The AI engines you bring to Aethel (Claude, Codex, Antigravity) see whatever you send them, under their own privacy policies, but we're not sitting in the middle.

Limited Use commitment. Aethel's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

1. Who we are

The company behind Aethel is Lucin Solutions LLC ("we", "us", "Lucin Solutions"). Aethel is the desktop app sold under the Aethel brand. If you have privacy questions, write to [email protected] or whatever address is listed at the top of tryaethel.com on the day you read this.

EU and UK users with GDPR or UK GDPR questions can write to [email protected]. We have not yet appointed a named EU/UK Representative under GDPR Article 27. If we do, we will list the representative here.

2. What data Aethel handles, and where

Aethel processes data in three places. We tell you about each so you know exactly what's happening.

2.1 On your computer (local)

Aethel reads, writes, and stores the following on the computer where it's installed:

• Configuration, your preferences, the AI engine you've chosen, the Telegram bot token you provided, your timezone, etc. Stored at:
  • macOS: ~/Library/Application Support/Aethel/config.yaml
  • Windows: %APPDATA%\Aethel\config.yaml
• Chat history with Aethel, every message you exchange with the Aethel agent over Telegram or web chat. Stored in agent/chat_history.json alongside the config above.
• Scheduled task definitions and run logs, what tasks you've set up, when they last ran, what the AI returned. In agent/scheduled_tasks/ and .task_runs/.
• Long-term memory, what Aethel remembers so you don't repeat yourself: facts and preferences you share, short pages about the people, projects, and topics that come up, and running recaps of past conversations. Stored locally in a database (agent/memory.db). You can browse, search, and delete any of it in the Memory section; it never leaves your computer.
• Optional activity observations (off by default; you enable individual ones under Settings, System, Data Sources). When on, Aethel notes patterns from your own activity to be more helpful, for example recurring email senders and recipients, likely bills and subscriptions, mail sitting unread that may need a reply, calendar habits, sites you visit often, download categories, and coarse location. These are privacy-hardened: email observations store senders, counts, and short subject fragments but never message bodies; filenames only and never file contents; location is saved as a place name (or a rounded map point) rather than precise coordinates; and banking, healthcare, and government sites are blocked outright. If you have linked more than one Google account, the email and calendar observations cover every linked account unless you narrow the selection in Settings, System, Data Sources; each observation is labeled with the account it came from. When proactive nudges are enabled, Aethel's nightly assistant may open a relevant email or calendar event in the moment to word a nudge accurately (for example, naming the bill that is due); what it reads this way is used only to compose that message and is not stored. Observations are stored only on your computer, in the same memory database, and are never sent to Lucin Solutions.
• Optional remote access (off by default; you turn it on under Settings, Web Chat). When enabled, your web chat is reachable from the internet at your personal address, behind your password, through a tunnel service that forwards the connection to your computer. The conversation itself still lives only on your computer.
• Reminders, watchers, location updates, .reminders/, .watchers/, agent/user_locations.json.
• Media you've sent to or received from Aethel, voice notes, photos, documents. In agent/media/.
• Application logs, diagnostic information at aethel.log.
• License cache, confirmation that your Aethel license is valid. In .license and .aethel_state.
• Files you ask Aethel to work with. When you direct Aethel to read, create, edit, or delete a file (for example, "summarize this PDF", "save this report to my Drive folder", "tidy up this spreadsheet"), it can reach any file your computer account can, not only its own workspace folder, so it can work with your real documents wherever they live. Those files stay on your computer. A file's contents leave only if you ask Aethel to send or upload it somewhere, or when you ask the AI to act on the file and the relevant excerpt is included in the prompt to the AI engine you chose (the same prompt path described in 2.2). Aethel asks you to confirm before it deletes or overwrites anything.

We do not transmit any of this data to Lucin Solutions servers. It exists only on your computer until you delete it, and uninstalling Aethel does not automatically delete it (you have to remove the data directory yourself).

2.2 With third-party services you authorize ("sub-processors")

Aethel's job is to drive other services on your behalf. Each integration you turn on becomes a sub-processor that sees the data you direct Aethel to send through it. You decide which to enable; Aethel never enables one silently.

The current sub-processor list:

When the AI engine is asked to act on your Google Workspace data (for example, "summarize this email", "schedule a meeting based on these threads", or "find a contact's number"), the relevant excerpt of that data is included in the prompt sent to the AI engine you selected. That prompt path is the only way Google data leaves your computer, other than the calls Aethel makes back to Google's own APIs to fulfill your request.

We list the sub-processors above so you can read each one's privacy policy yourself. Their use of your data is governed by their own terms, not by this policy.

If we add or change sub-processors, we'll update this list and note the change date at the top of this file. For material changes (a new sub-processor that sees data it didn't see before), we'll surface a notice in the app.

2.3 By Lucin Solutions (us)

We see almost nothing. Specifically, we receive:

• Purchase records from Lemon Squeezy, your name, email, country, and order details, so we can issue licenses and answer support emails.
• License validation pings, when Aethel checks "is this license still valid?", Aethel hits Lemon Squeezy's API. The fingerprint of the installation (a hash of hardware identifiers, not the raw identifiers) and the license key go to Lemon Squeezy. Lucin Solutions does not run a license server; we rely entirely on Lemon Squeezy.
• Support emails you send us, the contents of those emails, plus any logs or screenshots you choose to attach.
• Problem reports you choose to send. If you tell Aethel to report a problem to the dev team, it sends us a diagnostics bundle: your Aethel version, operating system and hardware type, your processor model, whether the Microsoft runtime components Aethel's voice and search features need are installed, the AI engine and model in use, a timestamp, the email on your linked Google account (so we can reply), a plain-language description of the problem, your full local log, and a copy of your settings, both with tokens, keys, passwords, and other people's emails stripped out. A report also carries a short technical record of how Aethel last stopped running, so that a crash can be told apart from a normal shutdown: Aethel's own crash log, the times your computer started up, shut down or signed in and out over the previous two weeks, whether Aethel was set to start automatically, any crash records Windows holds for Aethel itself, and, if the voice recogniser on your computer has been crashing, a short note of what it was and how it failed. It does not include crash records for any other program on your computer. A report can also include files you agree to attach, such as a screenshot of the problem or a file that came out wrong: Aethel names each file and asks before sending it, and it will not attach files that hold credentials or private data, such as your settings file, sign-in tokens, keys, or Aethel's own databases. The log, settings and any attachments are stored as files on our hosting provider for up to 90 days, then automatically deleted; the report itself becomes an issue in our private source repository that links to them. This is opt-in per report, Aethel always asks first, and it never includes your chat history, prompts, calendar, email, files, or memory unless you attach them yourself.
• Software-update checks. To keep itself current, Aethel periodically contacts our website to ask "is there a newer version?" and, if so, downloads the installer. This is an ordinary web request for a public file: it carries no account, license, name, or personal data, only what any download involves (your device's network address and standard request details, which our hosting provider may log briefly for security). You can turn automatic checks and downloads off under Settings, System, Software update and news. Installing an update is always something you start yourself.
• Aethel news. About once an hour Aethel reads a short announcements file we publish, so it can pass on things like a new feature or a cheaper AI model. This is the same kind of request as the update check: an ordinary read of a public file, carrying no account, license, name, or personal data. We are not told who read it or what they read, and nothing about you is sent. Announcements go to the account owner as a message. You can turn this off under Settings, System, Software update and news, and when it is off Aethel makes no request for it at all.
• Usage statistics. Once a day, Aethel sends us a small summary so we can see how many installations exist, keep the product working well, and know who to help. It contains: a random installation ID created on your computer (not a hardware serial number), the email address and display name of the account owner as already set up in Aethel (so we know which installation is whose), your Aethel version, operating system and hardware type, the AI engine selected, which features are turned on, daily counts of activity (for example, how many messages were exchanged and how many scheduled tasks ran), the general reason for any AI errors Aethel ran into that day (a one-word category such as "signed out", "rate limited" or "network", never the error message itself and never what you were doing at the time), whether Aethel stopped unexpectedly that day and roughly how long it had been running when it did, and the country the request came from (from the network connection, never from GPS or your precise location). Counts only, never content: it does not include your chat history, prompts, calendar, emails, tasks, memory, file names, locations, or anything you or the AI wrote. We also publish a few combined totals from these summaries on our website (such as the overall number of installations); those public numbers are aggregates across everyone and never identify anyone. This reporting is part of how Aethel works and does not have an in-app switch; if you object to it, contact us (section 12) and we will remove your installation's records, or you can stop using Aethel and ask us to delete what we hold (section 6).

We do not receive: your chat history, your prompts to AI engines, your calendar, your emails, your tasks, your reminders, your location, your files, or any content created by Aethel without your explicit say-so. The usage statistics above are counts and settings facts, never the content of anything.

3. Google Workspace data, what each scope accesses, and why

When you connect a Google account during the onboarding wizard, Aethel asks Google for four OAuth scopes. Aethel can connect more than one Google account; each is a separate OAuth grant that you approve individually, and if you are the admin you control which of your authorized users is allowed to reach each account. Everything in this section applies identically to every connected account. Below is, scope by scope, exactly what Aethel can see and do with that grant, what user-facing features rely on it, where any of that data ends up, and how long it stays.

Throughout this section, "Aethel" means the local desktop application running on your computer. Lucin Solutions LLC, the company that makes Aethel, does not access, receive, or store any Google data. The OAuth grant is between your Google account and the binary on your machine. We say more about this in §3.5.

We obtain your affirmative consent through Google's standard OAuth consent screen, which lists each requested scope individually before you grant access. You decide which scopes to approve at that moment, and you can revoke them at any time (see §3.5).

Aethel uses Google Workspace data solely to deliver the user-facing features described in §3.1 through §3.4. We do not use it for advertising, ad targeting, data brokering, credit assessment, or any purpose beyond fulfilling the request you made.

3.1 Google Calendar (https://www.googleapis.com/auth/calendar)

• What Aethel reads: the list of your calendars; events on those calendars including title, description, location, start/end times, recurrence rules, attendees and their responses, and any incoming invitations.
• What Aethel writes: creates new events on your behalf, updates existing events, deletes events, and accepts / declines / tentatives invitations.
• Why (user features): "What's on my calendar today?", "Schedule a 30-minute meeting with a colleague on Tuesday afternoon", "Find me an hour free on Friday before 4 PM", "RSVP yes to the team standup", the daily Morning Briefing scheduled task, the calendar-summary watcher.
• Where the data goes: stays on your computer. When the calendar detail is relevant to the request you made, Aethel may include the relevant event text in the prompt it sends to whichever AI engine you've configured (Anthropic's Claude, OpenAI's Codex, or Google's Antigravity). That AI engine processes the prompt under its own privacy policy.
• Retention: Aethel does not maintain a local mirror of your calendar. Each read happens in real time against Google's API in response to a user action or scheduled task. The AI engine's reply may quote calendar text back to you; that reply is stored in Aethel's local chat history file (agent/chat_history.json) on your computer like any other conversation, and you can delete that file at any time.

3.2 Google Tasks (https://www.googleapis.com/auth/tasks)

• What Aethel reads: your task lists and the tasks within them (title, notes, due date, completion state, parent/child relationships).
• What Aethel writes: creates new tasks, updates existing tasks (rename, change due date, edit notes, set parent), marks tasks complete or incomplete, deletes tasks.
• Why (user features): "Add 'pick up dry cleaning' to my task list", "What do I still have to do today?", "Mark the proposal draft as done."
• Where the data goes / retention: same as §3.1, local-only, with task text included in AI-engine prompts only when relevant to the user's request, no separate Aethel-side store.

3.3 Gmail (restricted scope): https://www.googleapis.com/auth/gmail.modify

• What Aethel reads: message metadata (sender, recipients, CC, BCC, subject, date, labels, snippet), full message body in plain text and HTML, attachment metadata (filename, MIME type, size), and attachment bytes when you explicitly ask Aethel to download one. Aethel can search your inbox using Gmail's standard query syntax in response to your requests.
• What Aethel writes: sends emails on your behalf, creates and manages drafts, replies (including reply-all and reply-to-thread) with full threading headers preserved, forwards messages, modifies labels (mark read / unread, archive, star, apply / remove custom labels), moves messages or threads to Trash, and operates in batch on multiple messages at once. Send-from-alias is supported when you have verified send-as addresses configured in Gmail.
• Why (user features): "What's in my inbox today?", "Reply to that thread saying yes", "Email a colleague the project files", "Forward this to my accountant", "Delete all the promotional emails from last week", "Mark everything from billing@ as read", the inbox-watcher feature, the daily-briefing inbox summary.
• Where the data goes: stays on your computer. Email content relevant to your request (an excerpt the AI is summarizing, the thread you're replying to, etc.) is included in the prompt sent to the AI engine you've configured. Attachments you ask Aethel to download land on your local disk under agent/media/received/documents/. Outbound messages and drafts are sent to Gmail's servers via Google's API as you would expect.
• Retention: Aethel does not maintain a local mirror, archive, or index of your Gmail. Each search and read is a real-time call against Google's API in response to a user action or scheduled task. The AI engine's replies, which may quote email text, are stored in your local chat history on your computer.

3.4 Google Contacts (read-only scope): https://www.googleapis.com/auth/contacts.readonly

• What Aethel reads: contact records (names, email addresses, phone numbers, organization, notes, structured fields).
• What Aethel writes: nothing, this scope is read-only and Aethel does not create, modify, or delete contacts.
• Why (user features): "Email a colleague the design files" → Aethel looks up the colleague's email address; "What's a contact's phone number?"; contact-aware behavior in scheduled tasks.
• Where the data goes / retention: same as §3.1, local-only, contact details included in the prompt to the AI engine only when relevant to your request, no separate Aethel-side store.

3.5 What does NOT happen with your Google data

To be unambiguous about the things Google's verification policy asks us to disclose:

• Lucin Solutions LLC servers do not receive any of your Google data. We do not run a backend that proxies, observes, or stores calendar events, emails, tasks, or contacts. The OAuth grant is between your Google account and the Aethel binary on your computer. The license-validation pings we describe in §2.3 carry only your license key and a machine identifier, no Google data ever rides on those calls.
• Your Google data is not used to train any AI/ML models. Aethel does not train models, period. The AI engines you bring to Aethel (Claude, Codex, Antigravity) process your prompts under their own privacy and training policies, read those at the providers' sites if you want to control how each treats prompt data. Aethel itself adds no training pathway.
• Your Google data is not sold, rented, or shared with third parties beyond the specific AI engine you've selected and the Google APIs Aethel calls back to fulfill your requests. The list of sub-processors that ever see any data flowing through Aethel is in §2.2; the only one in that table that ever sees Google data is the AI engine you chose.
• Aethel only reads when you ask it to. Every Gmail / Calendar / Tasks / Contacts call is made in response to a specific user message, a scheduled task you set up, or a watcher you armed. Aethel does not poll your inbox, scan your calendar, or scrape your contacts on its own.
• What happens when you ask Aethel to delete something. When you ask Aethel to delete an email, calendar event, or task, it carries out the request immediately and does not pause to re-confirm. You already asked. Importantly, Aethel only requests scopes that allow reversible deletion: emails go to Gmail's Trash (recoverable for 30 days from your Gmail UI), calendar events go to Google's recoverable-deleted-events bin, and tasks can be restored from Google's Tasks history. Aethel does not request the elevated scopes (such as https://mail.google.com/) that would let it permanently destroy mail. Contacts is read-only, Aethel cannot delete a contact at all. If you want Aethel to require explicit confirmation before any deletion, tell it so in chat and it will pause for a "yes" on each one for the rest of your session.
• You can revoke access at any time. Disconnecting Aethel from your Google account at <https://myaccount.google.com/permissions> invalidates the OAuth refresh token immediately; from that moment on, Aethel can no longer reach any of these APIs and you'll see explicit "not authorized" responses if you try to use a Google-related feature. Your locally cached AI chat history is unaffected by revocation; delete it manually if you want it gone.

3.6 AI/ML training disclosure (Google Workspace APIs)

This section addresses Google's AI/ML training disclosure requirement for Workspace APIs explicitly.

Aethel does not use Google Workspace data (Gmail, Calendar, Tasks, Contacts) to develop, train, or improve any generalized or non-personalized machine learning or artificial intelligence models, including large language models. Lucin Solutions LLC operates no model training pipeline of any kind, on Google data or on any other data.

Aethel does not have humans review your Google Workspace data on Lucin Solutions' side. The Aethel binary processes that data on your own computer to fulfill your requests. No engineer, support agent, or contractor at Lucin Solutions has access to your Google content.

When you choose an AI engine (Anthropic Claude, OpenAI Codex, or Google Antigravity), Aethel may include relevant Workspace content in the prompt sent to that engine so it can answer the request you made. Each engine processes prompts under its own published terms. Consult the providers' privacy and data use policies for how they treat prompt content, including whether they use prompts for model training. Aethel itself adds no training pathway, retains no copy on Lucin Solutions servers, and gives no human at Lucin Solutions access to the prompt or the Workspace data inside it.

3.7 Exporting your data (data portability)

Everything Aethel keeps locally is in plain text or standard formats: chat history is JSON in agent/chat_history.json, downloaded attachments are their original files in agent/media/received/, scheduled task definitions and run logs are JSON files. To export, copy the entire Aethel data directory listed in §2.1 to wherever you want it. No proprietary format, no Aethel side database, nothing to unwind.

Your original Google source data (the actual contents of your Calendar, Gmail, Tasks, and Contacts) lives in your Google account, not in Aethel, and remains exportable through Google Takeout at <https://takeout.google.com>.

4. Cookies and tracking

The Aethel desktop app and the local web chat interface do not use any analytics, advertising, or tracking cookies. We don't operate a behavioral-analytics pipeline on you.

When the web chat page cannot reach Aethel on your computer, it keeps a short technical note in your browser about the failure itself, for example whether the request was refused or timed out, whether your device was online, and how long the page had been open. That note is sent to Aethel on your own computer and written to the local log, so that it can be included if you later choose to send a problem report. It never contains your messages, your attachments, any file name, or any address you typed, and it is never sent to us or to anyone else on its own.

The marketing site at tryaethel.com uses no third-party analytics, no advertising pixels, and no cross-site trackers. It does keep one small note about where visitors arrive from, so we can tell which places are worth posting in:

• Where you arrived from. If you follow one of our links, it carries a short word naming where we posted it, for example instagram. If you arrive without one, the site works out a single word from the address your browser says you came from: the name of a search engine, the name of a site that linked to us, or simply "direct" when your browser says nothing at all. That one word is kept in your own browser for 90 days, because people often look today and get in touch next week. It is the only thing we store there for this purpose, it never leaves your browser except as described in the next point, and it is never combined with anything else about you.
• A count of visits. When you arrive, we add 1 to a tally for that one word. The tally is a number per word per day and nothing else. No address, no device, no identifier, no record of which pages you looked at, and nothing that could be traced back to a person.
• If you ask for early access. The name and email address you type into the request form are stored with that same one word so we know which of our posts reached you, and we are sent a copy by email. We use them to send you your download link and beta license, to reply to you, and to see which channels are working. If the same address asks again we tell you so on the page and send nothing more. You can ask us to delete them at any time (section 12), and asking costs you nothing.

If you install Aethel with the same email address you used on that form, we match the two so we can see that a request became an installation. That match is between your own signup and your own installation; it tells us nothing further about you.

If we ever add a general analytics tool, we'll list it here.

5. Lawful basis (GDPR / UK GDPR)

We process the limited data we do receive under the following lawful bases:

• Contract performance, issuing your license, validating it, providing support, Article 6(1)(b).
• Legitimate interest, preventing license abuse via fingerprint validation, and the daily usage statistics described in section 2.3 (understanding how many installations exist and how the product is used, so we can support it), Article 6(1)(f). You can object via the rights below.

We do not process data for marketing without consent.

6. Your rights

If you're in the EU, UK, California, or another jurisdiction with privacy rights, you have the right to:

• Access, ask what data we hold about you.
• Rectify, ask us to correct inaccurate data.
• Delete / Erase, ask us to delete your data.
• Port, ask for a machine-readable copy.
• Object / Restrict, object to processing under legitimate interest.
• Withdraw consent, for anything we processed under consent.
• Complain, to a supervisory authority (e.g. your country's data protection authority, or the California Attorney General).

To exercise any of these, email [email protected]. We'll respond within 30 days. Because we hold so little data, basically just your purchase record, most of these requests are quick to fulfill.

We don't sell your personal information. If you're a California resident: we have not sold or "shared" your data in the prior 12 months.

7. International data transfers

Lucin Solutions is based in the United States. Data we receive (purchase records, support emails) is processed in the US. For users in the EU/UK, this transfer relies on Lemon Squeezy's Standard Contractual Clauses for billing, and on legitimate-interest balancing for support emails (you chose to write to us).

You decide which sub-processors Aethel uses; their cross-border practices are governed by their own policies.

8. Children

Aethel is not designed for or directed at children under 13 (or under 16 in some EU jurisdictions). We don't knowingly process data from children. If you believe a child has used Aethel, contact us and we'll delete any related records.

9. Security

We protect the small amount of data we do hold using:

• TLS for all communication with Lemon Squeezy.
• Bcrypt hashing for the local web-chat password (stored on your device).
• AES-GCM encryption for the locally-cached license state.
• HMAC integrity protection on license payloads from Lemon Squeezy.
• Limited data retention, purchase records as long as required by tax law (typically 7 years), then deleted; support emails for 2 years.

We can't promise no breach will ever happen, but we'll notify you under GDPR / state-law timelines if one does and you're affected.

10. Retention

11. Changes to this policy

If we change this policy, we'll bump the "Last updated" date at the top and, for material changes, surface a notice in the app on next launch. You'll never see a sneaky change.

12. Contact

Lucin Solutions LLC Privacy questions: [email protected] General contact: [email protected] Mailing address: listed at tryaethel.com

This policy is governed by the laws of the State of Oklahoma in the United States. Disputes will be handled per the Aethel Terms of Use.