This policy states what information the Astral application for macOS and the Astral website collect, why they collect it, who receives it, how long it is held and what you can require of us. It is given by Astral AI Inc. and covers no other company.
Last changed 21 August 2026. This version replaces every earlier version.
Astral AI Inc. makes Astral and is the company responsible for the information described in this policy. Where the words we, us and our appear here they mean Astral AI Inc. Where the words you and your appear they mean the person using Astral.
Claude and Claude Code are made by Anthropic, which is a separate company. We are not Anthropic, we do not act for Anthropic, and what Anthropic does with what you send it is governed by your own agreement with Anthropic and not by this policy.
Astral runs on your own computer. Your files, your code, the prompts you write, the replies your agents write, your keys and your file paths are not sent to us and we have no way to read them. What we receive is a small amount of information about how the application is used, how it is configured and how it fails. It is not attached to your name or your email address, because Astral has neither.
This section is a summary and nothing more. Sections 3 to 17 are the policy, and where the summary is less precise than they are, they govern.
Astral is a layer over the copy of Claude Code already installed on your computer. It reads your sessions from your own disk and runs them under your own user account. No server of ours stands between your computer and Anthropic, so your prompts reach Anthropic in the same way they do when you run Claude Code in a terminal, and we cannot see them at any point.
Astral has no sign in, no user account and no cloud copy of your work. We therefore hold no name, no password and no profile of you, and nothing in this policy should be read as saying otherwise. We hold no email address for you either, unless you type one into the feedback box yourself, which is described in section 5.4 and is never required.
We do not receive, and no future version of Astral will send us, any of the following.
This section is the binding limit of the whole policy. Every other section describes information received inside it, and section 5 may grow only inside it. If we ever intend to send anything named above, we will change this section before doing so and we will say in the application that it has changed.
A count records that something happened once. It carries no text that you or an agent wrote, no name, no path and no title. Astral sends the following counts today.
Astral is early and it changes quickly. We expect to measure more of how it is used than this over time, and when we do, this list is changed in the same release that changes the application. What may never grow is section 4, which is the promise this policy is built on. A new count tells us that a part of Astral was used. It will not tell us what you were working on.
The first time Astral runs it generates a random identifier and stores it in a file on your computer. Its only purpose is to let counts from one installation be read as one installation rather than as many. It is not your name, your email address or an account, it is not derived from anything about you or your hardware, and we hold nothing that would let us connect it to you. Removing Astral and its application data ends it. A fresh installation generates a new one, and we cannot tell that the two are the same person.
When Astral fails it prepares a report. The report says which of the ways the application can fail happened, when it happened, the installation identifier, the version of Astral, the release of macOS and the processor architecture, how long the application had been open, and the error itself, which is its name, its error code, the name of the system call that failed, its cleaned message and the failing lines of our own code.
Errors normally carry your home directory, your username and your folder names inside them. Reports are therefore cleaned on your computer, before anything is sent, rather than after they arrive. Paths are removed and only their depth is kept, the arguments to the failed system call are dropped in full, and stack frames outside our own application are counted and discarded. The finished report is then checked again, and a report that still contains anything private is not sent with the offending field removed, it is discarded in full and replaced by a note that a crash happened.
We tested this by breaking a real copy of Astral three ways on purpose and reading what came out. None of the three carried a path, a folder name or a task title.
Astral has a box for telling us what broke, what is missing or what you wish it did. Nothing in it is collected. It is sent only when you write something and press send, and if you never open it we receive nothing from it at any point.
What we receive when you do press send is this.
The address is optional and it is the one thing in Astral that can identify you, because you typed it. It is used to answer you about your message and for nothing else. It is not added to a mailing list, it is not used to advertise to you, and leaving it blank does not stop your message arriving.
Your message is written to a file on your own computer before it is sent, so that it is not lost if you are offline, and it stays there afterwards. A message that cannot be delivered is tried again the next time Astral opens, and after thirty days it is no longer tried and simply remains on your computer.
Section 4 governs this section as it governs every other. We do not attach your files, your code, your prompts, your keys or your paths to a feedback message, and a file you attach yourself is sent by its contents and its name, never by where it was on your computer. If you write any of those things into the box yourself, they reach us because you chose to send them.
We use what is described in section 5 to see whether Astral is used and which parts of it are used, to find and fix faults, to decide what to build next, and to count installations. We use it for nothing else.
We do not use it to build a profile of you, to target advertising, to score you, or to make any decision about you by automated means. We do not attempt to identify you from it and we hold nothing that would let us.
Where data protection law requires us to name a basis, we rely on our legitimate interest in understanding, maintaining and improving software we make. We consider that interest balanced against your privacy by the limit in section 4, which keeps everything of consequence off our systems entirely, and by the control in section 10.
You may object to this use at any time, and section 10 is how you do it without writing to anyone.
One outside service stores the counts and the crash reports for us and processes them only on our instructions and for no purpose of its own. That service is PostHog. No other company receives any of it.
We may disclose what we hold if the law requires it of us, such as under a valid legal demand, or where it is necessary to establish or defend a legal claim or to protect the safety of a person. If we are ever asked for information in a way we are permitted to tell you about, we will.
If Astral AI Inc. is sold, merged or reorganised, what we hold may pass to the buyer. The buyer would be bound by this policy until it gives notice of a different one.
What section 5 describes is stored by the service named in section 8, in the United States. If you use Astral from another country, using it sends that information there.
One setting in Astral controls all of it. It is on when you install Astral. Turning it off stops the counts and stops the crash reports, and nothing else about the application changes. There is no reduced or partial mode and no second setting to find.
Turning it off stops sending from that moment. It does not by itself delete what was sent before, which section 12 covers.
We keep what arrives only for as long as it is useful for building, fixing and understanding the use of Astral, and we delete it when it is not. We have not yet fixed a period, and when we do it will be stated in this section rather than left to practice.
Depending on where you live you may have the right to ask what we hold about you, to receive a copy of it, to have it corrected, to have it deleted, to object to or restrict how we use it, and to complain to your data protection authority. We will not treat you differently for exercising any of them, and there is nothing to treat differently, because Astral has no account and no paid tier that could be withdrawn.
Because Astral holds no account, what we receive is tied to the installation identifier in section 5.2 and to nothing else. To act on a request we need that identifier, since without it we cannot find your records among anyone else's, and we will not ask you for identity documents or any other personal information in order to answer. Requests are made in the way section 17 states.
Astral is a developer tool for adults. It is not directed at children under 13, we do not knowingly collect information from them, and if we learn that we have, we delete it.
What we receive is held on systems reachable only by the people who need them, and by the service in section 8 under its own security terms. No method of transmission or storage is completely secure and we do not claim otherwise.
The strongest protection in this policy is not a security measure. It is section 4, which means that the material that would actually matter if it were exposed is never on our systems in the first place.
We do not sell personal information and we do not share it for cross context behavioural advertising, as those terms are used in California law. We have never done either. We run no advertising in Astral, we place no advertising trackers in it, and we hand nothing to a data broker or to any third party for that party's own purposes.
Astral sets no cookies and there is no browser signal for us to honour, but if we ever add anything a Global Privacy Control signal would apply to, we will honour it.
The page you are reading loads no fonts, no scripts and no trackers from any other company, and sets no cookies. The company that hosts it keeps ordinary records of the requests it serves, including the network address a request came from, in the way every web host does. We do not use those records to identify anyone.
Astral changes quickly and this policy changes with it. Whenever we change what the application collects, sends or stores, this page is changed in the same release, not afterwards. The date at the top says when it last changed. Where a change materially reduces the protection this policy gives you, we will say so in the application rather than quietly editing this page.
A request under section 12, or a question that this policy is required to give you an address for, is sent in writing to savannah@astral.now.