Privacy
What Hangar knows about you
HangarAI runs on your computer. The one thing that can leave it for a server of ours is the optional Hangar account, and only once you sign in. This page says what that account stores, what it never stores, and how to delete it.
Last updated: 17 November 2026.
In short.
- Without an account, HangarAI never contacts the account server. The account is optional and off by default.
- With one, the server stores who signed in, the machines you linked, and, only if you turn the statistics sync on, usage totals per machine, day, model and project name.
- It never receives a file path, a transcript, a prompt, an answer or a line of your code.
- Delete my account, in Hangar's settings, deletes everything at once.
What this page covers
The Hangar account, served at account.hangarai.dev, and this website,
hangarai.dev. Both are run by simnJS, the author of HangarAI, who is
responsible for the data described here.
It does not cover Claude Code, which HangarAI runs on your computer under your own Claude account: what Claude Code sends to Anthropic is between you and Anthropic. Nor does it cover GitHub, which you use to sign in and which has a privacy policy of its own.
The Hangar account
A Hangar account links several of your machines, so that the usage statistics of all of them can be read from any of them. You create it by signing in with GitHub from Hangar's settings. Nothing in the app requires it.
What the server stores
-
Who signed in. What GitHub says about you when you sign in: its identifier
for you, your display name, your email address when it confirms it is verified, and the
address of your avatar. Hangar asks GitHub for
read:user user:email: your profile and your email address, nothing else. It cannot read your repositories, your files or your contacts. -
Your machines. For each machine you sign in from: its name, its operating
system (
windows,macosorlinux), an identifier Hangar drew at random for that install, the date it was linked and the date it was last seen. -
Usage statistics, only while the statistics sync is on. It is a setting of
its own, and signing in does not turn it on. For each machine, day, model and project name:
the number of input, output and cache tokens, what the API would have charged for them, the
active time and the number of sessions. The project name is the name of its folder
(
hangar), never its path. - Sign-ins in progress. While you are on GitHub's page: the machine's name and what is needed to bring you back to Hangar. Deleted when you come back, and after ten minutes if you do not. The one-time code that ends a sign-in is deleted within five minutes.
The token that keeps a machine signed in is stored on that machine only, in the operating system's keychain. The server keeps a hash of it (SHA-256), from which the token cannot be recovered.
What it never stores
- The paths of your files or folders.
- Your conversations with Claude: no prompt, no answer, no transcript, no session title.
- Your code, your files, your diffs, your commits.
- GitHub's access token. It is used once, to read your profile at sign-in, and is not kept.
- Your GitHub password, which Hangar never sees.
- Your IP address. The server keeps no request log. To limit abuse it counts requests per address in memory, for about a minute, and writes none of it down.
The server has no field to receive any of this, and refuses a project name that contains a path separator.
What it is used for
To show you your account, your machines and your statistics in Hangar, on each of your machines. Nothing else: no advertising, no profiling, no analytics, no newsletter. Your data is not sold, rented or shared with anyone, and is not used to train any model.
The basis for this processing is your consent: you give it by signing in, and withdraw it by deleting your account.
Where it is
On one server operated by simnJS, in a single database. Requests reach it through Cloudflare, which, like any network intermediary, sees the IP address a request comes from and handles it under its own privacy policy. Everything travels over HTTPS.
How long it is kept
- Your account, your machines and your statistics are kept until you delete them. Nothing expires on its own.
- Backups of the database are kept for 14 days at most. What you delete disappears from them as they are replaced.
Deleting your data
All of it is done from Hangar, in Settings, under Hangar account:
- Sign out destroys this machine's token. Its statistics stay on your account, so that signing in again finds them.
- Forget a machine deletes that machine and every statistic it sent.
- Delete my account deletes everything: the account, what GitHub said about you, every machine and its token, every statistic. It happens at once, and nothing is kept aside.
Turning the statistics sync off stops sending new totals; forgetting the machine or deleting the account removes the ones already sent.
To also withdraw the access you gave Hangar on GitHub, remove it from your GitHub applications.
Your rights
What Hangar shows you under Hangar account is what the server holds about you: your profile, your machines, your statistics. You can correct a machine's name there and delete any of it. If you live in the European Union you also have the right to ask for a copy of your data, to object to its processing, and to complain to your data protection authority. Write to us (below) and we will answer.
This website
This site sets no cookie, runs no analytics and loads nothing from another origin: no tracker, no font or script from a third party. Like the account server, it is served through Cloudflare. The theme you pick on the home page is not remembered.
Changes
If what the account stores changes, this page changes first, with its date. Its history is
public, like the rest of HangarAI:
every version of this page.
The code of the account server is public too, in
crates/hangar-cloud,
and its protocol is described in
docs/native/cloud.md.
Contact
For a question about your data, or a request you cannot make from the app, open an issue at github.com/hangar-ai/hangar (do not put personal data in it: say what you need, and we will reach you privately), or write to [email protected]. To report a security problem, use the repository's private security report.