AetherGet Aether

Privacy

Your data, clearly explained.

Privacy policy for the Aether desktop app, cloudunit.uk and associated hosted workflows.

Effective 12 October 2026 · Aether / CloudUnit · California, United States

Who this policy covers

Aether / CloudUnit is operated by an individual developer based in California, United States. This policy covers the Aether desktop app, cloudunit.uk and hosted workflows on this domain. Questions and privacy requests can be sent to aethersupervisor@outlook.com.

This policy describes current features. It does not assume that online Aether accounts, cloud synchronization, payments or subscriptions already exist. Those features will need additional notices before they collect information.

The information involved

The information Aether handles depends on the features and connections you use:

  • Workspace records: conversations, prompts, model responses, plans, project paths, selected file context, tool results, checkpoints and browser feedback.
  • Settings and connections: preferences, model endpoints, model choices, integration settings and credentials you configure.
  • Project search: local file indexes and search information. If you enable remote embeddings, code or text chunks are sent to your configured embedding service.
  • Profiles: a display name you choose and optional Google identity information described below.
  • Operational information: local diagnostic and performance records, website request information and hosted-workflow records.
  • Support: your email address and the messages, attachments or logs you choose to send us.

Aether can work with personal information contained in project files or task content you select. Do not submit information you are not authorized to use or disclose.

What stays on your device

Aether is local-first. Conversations, settings, profile information and other workspace records are stored on your device. Local models can process requests through your own model server. A local configuration can still contact external websites, tools or download services when you use those features.

Private Values uses supported operating-system-backed encryption for its stored values. This does not mean every conversation, file, setting or backup is encrypted. Device security, access permissions, external runtime configuration and backups also affect how information is protected.

Records can be included in device backups or folder synchronization you enable. Resetting preferences or uninstalling Aether does not necessarily remove saved conversations or application data.

Models, tools and browser activity

When you select an external model provider or agent runtime, requests can include prompts, conversation context, code, file excerpts, plans and tool results. The selected service receives that content and ordinary connection information. Its account terms, retention settings and privacy policy govern its processing.

MCP servers, plugins, hooks, tools and agent runtimes can access or send information needed for the work and permissions you give them. Executable integrations may have their own storage and network behavior. Review each integration before enabling it.

Browsing in Aether contacts the websites you visit. Those websites may set cookies, receive network information and store account activity under their own policies. Screenshots, page content or feedback you attach to a conversation may be sent to the selected model.

Aether / CloudUnit does not receive all desktop conversations merely because you installed the app. Information reaches our hosted services when you use a workflow that sends it there, or when you send it to us directly.

Optional Google connection

Connecting Google requests only openid, email and profile. Google provides an account identifier, verified email address, name and, when available, a profile picture URL. Aether stores those details and the connection date locally to identify and display your profile.

Google profile information is not sent to AI models, used to train AI models, used for advertising or sold. The connection does not request Gmail, Drive, Calendar or Contacts access. It currently does not create a server-side Aether account or synchronize your work.

Authorization runs through Google in your system browser. OAuth tokens are used temporarily by the desktop app to fetch identity information; they are not saved in your profile file or sent to cloudunit.uk. Loading your Google avatar contacts Google and exposes ordinary network information such as your IP address.

Disconnecting in Settings → Profile removes the saved Google identity locally. Separately revoke consent through Google account connections. Google manages its own account and authorization records.

Website and hosted workflows

Cloudflare hosts cloudunit.uk and processes requests for delivery, security and troubleshooting. Information can include IP addresses, request times, URLs, browser details and diagnostic information. Workers invocation logs are enabled. Avoid putting secrets or sensitive information in URL query strings.

This public site has no advertising, third-party analytics, external fonts or embedded sign-in widget. The site itself does not set cookies or browser storage. Cloudflare can process security information and may use essential security cookies.

Separate hosted agent-workflow endpoints accept events, function requests, chat messages and responses. These can store submitted content, arguments, tool-call information, site/session identifiers, timestamps, browser details and hashed IP addresses in Cloudflare KV. Visiting this website or connecting a Google profile does not automatically submit those records.

Why information is processed

Workspace information supports the tasks, context, search, history and tools you ask to use. Profile information displays your chosen identity. Hosted records deliver configured workflows. Operational records support reliability, abuse prevention and troubleshooting. Support messages help us respond to your enquiry or request.

Where a law requires a stated lawful basis, optional Google connection relies on your consent; providing requested services can rely on performing a contract or taking requested steps before a contract. Necessary website operation, security and support can rely on legitimate interests in running and protecting the service, balanced against your rights. A legal obligation can require specific records or disclosures. Aether / CloudUnit does not use these records to make automated decisions with legal or similarly significant effects about you.

Recipients and international processing

Recipients depend on your actions: selected model providers and agent runtimes, integration operators, browser destinations, Google, Cloudflare, and Microsoft for messages sent to our Outlook address. Information may also be disclosed to comply with applicable legal requirements.

Cloudflare, Google, Microsoft and your selected providers may process information in the United States or other countries where they operate. Applicable provider terms and data-protection arrangements govern their processing. Where transfer safeguards are required for information under our control, the applicable safeguards must be established for that transfer; contact us for details of an affected hosted workflow.

Read the Cloudflare privacy policy, Google privacy policy, Microsoft privacy statement, and the notices of any other service you choose.

Retention and deletion

  • Local records: remain until you delete them, remove their stored application data, or the relevant local feature removes them. Device backups may retain copies. We cannot remotely erase files that are only on your device.
  • Google identity: remains locally until you disconnect or remove the profile data. Disconnecting does not delete other conversations, settings or Google account records.
  • Workers logs: currently have a maximum seven-day retention, depending on Cloudflare plan. Other Cloudflare security records follow its applicable policies.
  • Hosted workflow records: have no automatic expiry in the current endpoints and remain until the operator deletes them. Request removal using the relevant site or session identifier.
  • Support and privacy requests: are retained as needed to respond, resolve follow-up issues and meet applicable recordkeeping obligations. Retention depends on the nature of the request and any legal requirement.
  • External providers: retain information according to their own policies and account settings. Deleting local Aether records does not delete their copies.

Your choices and privacy rights

Google connection is optional. Choose your providers, review integration access, disconnect accounts and remove local data you no longer need. Where consent is the basis for processing, you can withdraw it; this does not undo prior lawful processing.

Depending on applicable law, you may have rights to access, correct, delete or receive a copy of information, restrict processing, or request information about recipients. You may object to processing based on legitimate interests. California residents may have additional rights under applicable California law, including rights concerning sale or sharing when those laws apply. This site does not sell personal information or share it for cross-context behavioral advertising.

Send requests to aethersupervisor@outlook.com. We may need proportionate information to locate the records and verify the request. Do not send an API key or sensitive project content as proof. You can use an authorized representative where the law allows. Exercising a privacy right does not require accepting the terms, and we will not penalize a lawful request.

You can complain to the appropriate regulator, including the California Attorney General or, where applicable, the UK Information Commissioner. Responses and exceptions follow the law applicable to the request.

Children and policy updates

Aether is a development and productivity workspace and is not directed at children. If you believe a child has sent personal information to our hosted services, contact us so we can investigate and remove it where appropriate.

We will update this policy as data handling changes. Material new processing, such as online accounts, synchronization or payments, will be described before introduction, with additional notice or consent where required. The effective date identifies this version.