AIDE Privacy

Privacy
policy

What AIDE does with your data, what it keeps on the computer, what it sends over the network and when — and what it never does.

Revision of 16 November 2026

In short

  • The app collects no telemetry and keeps no usage statistics.
  • Your code stays on your disk.
  • Only a request to the model you chose leaves the machine — and only if that model is external.
  • Access keys live in the protected Windows store, not in project files.

Who is responsible for processing

AIDE and the site that distributes it are run by the project author, Abubakr Sanginov. He decides which data the app needs and is responsible for protecting it within his means.

Processing mostly happens on your computer. The app has no server side: there is no account and no server that would keep your projects.

What we do not collect

  • No telemetry and no usage analytics: the app sends no reports about what you opened or which buttons you pressed.
  • No contents of your projects, files or agent conversations to our servers — there are no such servers.
  • No list of installed programs, file names or browser history.
  • No advertising identifiers or advertising profiles.

What is stored on the computer

Everything the app needs to work lives locally:

Projects and files
In the folders you opened. The app writes there only on your command or with your permission.
Settings and chat history
In the app's data folder in your Windows profile: theme, language, font size, provider list, conversation history per project.
API keys
In the Windows Credential Manager, one record per provider. Project files never contain them.
Undo snapshots
Checkpoints taken before agent edits — temporary, used by the Undo button.

What leaves the machine

The only mandatory internet request is the call to the model you chose. It carries what you sent: the task text, attached files and the code or project fragments needed for the answer.

  • To whom. To the model provider you configured: OpenAI, Anthropic, Google or your own server. From there, their policy and their rules apply.
  • Update checks. The app reads the GitHub releases page to learn the number of the new version. That is a plain file request; project contents are not sent with it.
  • Pages the agent asks for. If a task needs a page from the internet, the address goes to that site — just as if you opened it in a browser.
  • Nothing beyond that. No background reports, counters or “anonymous statistics” are sent.

Access keys

An API key is a password to your account at a model provider. The app keeps it in the Windows Credential Manager, encrypted, separately for each provider.

  • The key is not written into project files, does not reach a repository and is not printed in logs.
  • The key is not forwarded to the model in the request text and is not shown in the interface after saving.
  • A key can be deleted in settings — the record is erased from the store.

Local models

If you connect a model running on this same computer (Ollama or LM Studio, for example), requests go to a local address and never leave the machine. In this mode the app can work entirely without internet — apart from the update check, which you may skip.

The site, cookies and logs

The site is static pages. It has no forms with personal data, no ad networks and no third-party counters: the pages' security policy forbids loading foreign scripts.

  • Cookies. The site sets no tracking cookies. Page preferences, such as the lite mode, live in your browser's localStorage and are never sent anywhere.
  • Hosting logs. The pages are hosted on Vercel. Like any host, it keeps technical request logs: page address, time, browser type, IP address. Those logs keep the site running and protected.
  • Language. The page language comes from the address, not from a visitor profile.

Downloading the installer

The installer is served from this site or from the GitHub releases page. While downloading, the host and GitHub see the ordinary technical data of a request. The installer contains no built-in counters and sends no installation report.

Sharing with third parties

We do not sell or share data with third parties, because we do not hold it. Technical site data is handled by the host, and model requests by the provider you chose; each follows its own rules.

Retention

Data on your computer is kept until you delete it: settings until the app is uninstalled, chat history until you clear it in the interface or delete the data folder, keys until you delete them in settings. Technical site logs are kept by the host for its standard period.

Your rights

Since processing mostly happens on your device, you control the data yourself: you can view, change and delete settings, history and keys at any time. If you believe processing violates your rights, write through the project page on GitHub — the request will be considered on its merits.

Security

  • Traffic to external services goes over an encrypted connection.
  • Updates are verified by cryptographic signature — a swapped file will not be installed.
  • File writes, terminal commands and network access happen only after your confirmation.
  • A checkpoint is taken before edits, so changes can be undone.

Children

The app is meant for developers and is not addressed to children. We deliberately collect no data about children — in fact we collect no personal data through the app at all.

Changes to this policy

The policy may be updated together with the app: for example, if a new feature that uses the network appears. The current revision is always on this page with the date at the top. Material changes are noted in the changelog.

Contact

Questions about data and privacy: the project page on GitHub, in the issues section. The author and the data controller is Abubakr Sanginov.

This page describes how data is handled and is not legal advice.