Astral AI Inc.

Privacy policy

This policy states what information the Agentbox application for macOS, Agentbox Cloud and the Agentbox 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 15 November 2026. This version replaces every earlier version.

1

Who we are

Astral AI Inc. makes Agentbox 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 Agentbox.

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.

2

The short statement

Agentbox 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. Unless you sign in, it is not attached to your name or your email address, because Agentbox then has neither. There are two exceptions, and both are your choice. Signing in backs up your threads to your account, which section 5.8 describes, and Agentbox Cloud runs tasks on computers we rent, which section 5.7 describes. Each section says exactly what is sent and what is kept.

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.

3

How Agentbox works, which decides most of this policy

Agentbox is a layer over the copy of Claude Code 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.

If neither Claude Code nor Codex can run on your computer when you first open Agentbox, setup asks which plan you pay for and installs the tool that plan needs. It runs that tool's own installer, published by Anthropic or by OpenAI, and then starts that tool's own sign in, which opens Anthropic's or OpenAI's page in your browser. You sign in on that page. Agentbox never sees your password and receives no key or token, and nothing about the installation or the sign in is sent to us. If the Claude or ChatGPT application on your computer already carries a copy of the tool, Agentbox uses that copy and installs nothing.

Agentbox also supports Codex using your own Codex account. When you request conversation compaction, the installed Codex summarizes the existing conversation through its configured provider. That provider processes the conversation under your agreement with it. Agentbox keeps the command status on your computer and does not send the conversation or its summary to us. Compaction does not grant an agent any additional permissions.

Agentbox managed Codex workers disable automatic loading of Codex apps and plugins. A project worker may still use the local Agentbox store connection supplied for that task. This does not change the integrations in your separate native Codex sessions.

Messages you send while an agent is working are forwarded to the existing Claude Code or Codex conversation through your configured provider account. Agentbox keeps the reply and delivery state locally. Your provider processes these messages under your agreement with it. The messages and their contents are not sent to us.

The built-in terminal runs a local shell under your computer account in the selected task folder. Terminal input and output are not sent to us. Agentbox retains a limited amount of output in memory while it runs. Your shell and the programs you run may keep their own history, write files or communicate with services you choose. Those services process information under their own policies.

In personal Claude Code conversations, requests that need your approval can be shown in Agentbox. The request and your decision are kept locally so the waiting agent can receive your answer. This approval channel does not give the conversation access to Agentbox task store tools and does not send approval records to us.

Commands you invoke can also request code review, manage conversation goals, or inspect the connected provider and local project. Provider commands use your existing provider account. Review may send project content to that provider as part of its normal operation. Command results, model and effort choices, and the available Claude Code command names are kept locally. These results and command names are not sent to us.

When you enable Remote Control for a Claude Code conversation, the installed Claude Code connects that conversation to Anthropic so you can continue it in Claude on another device. Anthropic receives the conversation history and subsequent messages under your agreement with it. Tool execution remains on your computer. Agentbox stores remote replies and connection state locally and does not receive a cloud copy of the conversation. Turning Remote Control off disconnects access through this local session. It does not promise deletion of records held by Anthropic.

Agentbox asks you to sign in when you first open it, and you can skip that. If you skip it and do not choose Agentbox Cloud, Agentbox has no user account and no copy of your work anywhere but your computer. We then hold no name, no password and no profile of you, and no email address either, and the feedback box described in section 5.4 has nowhere to type one. Sections 5.7 and 5.8 say what changes if you do sign in.

Agentbox can also use the services you have connected to Claude Code, such as Slack or Linear. When an agent reads from one of them, the request goes from your computer to that service through Claude Code, signed in as you, under your own account with that service and its own terms. Agentbox holds no password, key or token for any of them, and nothing an agent reads there reaches us. In this version an agent can only read from a connected service. It cannot send or post anything through one, and a version that can will change this policy and section 7 of the terms before it is released.

4

What never leaves your computer

We do not receive, and no future version of Agentbox will send us, any of the following, except for what you yourself choose to back up by signing in, which section 5.8 describes in full, and a task you yourself choose to run in Agentbox Cloud, which section 5.7 describes in full.

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. The two exceptions are section 5.7, which applies only to a task you send to Agentbox Cloud yourself, and section 5.8, which applies only while you are signed in. Neither applies to anything else Agentbox does. If we ever intend to send anything named above in any other way, we will change this section before doing so and we will say in the application that it has changed.

5

What Agentbox does send

5.1 Counts of what happens in the application

A count records that something happened once. It carries no text that you or an agent wrote, no name, no path and no title. Agentbox sends the following counts today.

Agentbox 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 Agentbox was used. It will not tell us what you were working on.

5.2 The installation identifier

The first time Agentbox 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 Agentbox and its application data ends it. A fresh installation generates a new one, and we cannot tell that the two are the same person.

5.3 Crash and error reports

When Agentbox 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 Agentbox, 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 Agentbox three ways on purpose and reading what came out. None of the three carried a path, a folder name or a task title.

5.4 The feedback box

Agentbox 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.

There is nowhere to type an address, so nothing you send from the box tells us who you are unless you write it in the box yourself. The installation identifier described in section 5.2 is not sent with a feedback message.

Your message is not written to a file and it is not held anywhere for sending later. It is sent when you press send, and if it cannot be sent, Agentbox says so and leaves what you wrote in the box so you can send it again. Nothing is tried again on its own, and closing the box without sending discards what is in it.

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.

5.5 Checking whether there is a newer version

Agentbox keeps itself up to date. A few times a day it asks GitHub whether a newer version has been released, and if there is one it downloads it in the background and waits for you to restart. Nothing is installed until you say so, and restarting is a button you press.

That question goes to github.com, which is a separate company, and not to us. We receive nothing from it. GitHub receives what any website receives from a request, which is your network address and which file was asked for. It carries no identity, no account, no key and none of the counts described in section 5.1, and it is not joined to anything else in this policy.

Section 4 governs this section too. Nothing about your files, your code, your prompts, your keys or your paths is sent in order to ask whether there is a new version.

A copy of Agentbox run from its source code asks a different question in the same way. Every half hour it asks the GitHub repository it was copied from whether newer code has been published there, using the ordinary git fetch that copying it used. If there is newer code it says so and waits for you to restart, and restarting is a button you press. A copy whose folder holds changes of your own, or that follows no repository, does not offer to update at all. GitHub receives the same things as above and nothing more, and section 4 governs this question as it governs the other.

5.6 Installing Claude Code or Codex during setup

When you choose a plan during setup and the tool it needs is not on your computer, Agentbox downloads that tool's installer from claude.ai, which is Anthropic's, or from chatgpt.com, which is OpenAI's, and the installer downloads the tool from the same company. This happens only when you choose a plan.

That request goes to Anthropic or to OpenAI and not to us. We receive nothing from it. The company receives what any website receives from a request, which is your network address and which file was asked for. The sign in that follows happens on that company's own page, under your agreement with it.

Section 4 governs this section too. Nothing about your files, your code, your prompts, your keys or your paths is sent in order to install either tool.

5.7 Agentbox Cloud, if you choose it

Agentbox Cloud is optional. It runs some of your tasks on computers we rent from Amazon Web Services instead of on your own computer. Nothing in this section happens unless you sign in to Agentbox Cloud, accept its terms and send a task to it. Turning it off in the application stops anything new being sent to it.

When a task runs in Agentbox Cloud, the following leaves your computer for that run.

Each run gets a computer of its own, which no other person's run shares, and that computer is stopped when the run ends. What the run produces, its commits, its changes, its conversation and what it wrote to the documents folder, comes back to your computer. The copies a run leaves in Agentbox Cloud are deleted seven days after it.

Your Claude or Codex sign in for Agentbox Cloud is made on Anthropic's or OpenAI's own page, from inside Agentbox Cloud, and it is kept there so that later runs can use it. It is never sent to your computer, and the application lets you remove it at any time. An agent running with it can read it, as it can on your own computer.

For as long as you have an Agentbox Cloud account we also keep the identifier and the email address of the account you signed in with, its name and picture if it has them, the name of each computer you signed in to it from, the plan you are on, when you accepted the terms, and for each run when it started, when it ended and how long it ran. We keep these to hold your plan's limits and to charge you correctly.

If you choose a paid plan, you pay on a page run by Stripe, and Stripe takes your card or other payment details. We never see or hold your card number. Stripe tells us which plan you chose and whether it is paid, and we keep that with your Agentbox Cloud account, together with the reference numbers Stripe gives your customer record and your subscription.

Only the systems that run Agentbox Cloud read what a run carries. Nobody at Astral AI Inc. looks at it, unless you ask us to in order to fix a problem with your run or the law requires it.

5.8 Your account and its backup, if you sign in

Agentbox asks you to sign in when you first open it, with Google or with an email address and a password. Signing in is optional. If you skip it, everything else in Agentbox still works on your own computer and nothing in this section happens. Signing out stops anything new being sent.

While you are signed in, Agentbox backs up your work to your account and keeps the copy up to date, so that you can read and answer your threads from the Agentbox app on your phone, including while your computer is closed. The following leaves your computer for that.

Before a thread is copied, Agentbox hides any text in it that looks like a key, a token or a password. Your repositories, your terminal and the rest of your files are not copied.

For the account itself we keep its identifier, the email address you signed in with, and its name and picture if it has them.

Only you can read the copy, along with anyone you share a project with, who can read that project's threads. Nobody at Astral AI Inc. looks at it, unless you ask us to in order to fix a problem or the law requires it. We do not use it to train any model, and we do not sell it. Deleting your account deletes everything in this section.

5.9 Reading your Codex usage when you press Refresh

Settings shows how much of your Codex plan's limits you have used. Most of the time it reads that from what Codex has already written on your computer, which sends nothing. When you press Refresh on the Codex page, Agentbox asks the Codex installed on your computer for your current usage, and Codex asks OpenAI, signed in with your own Codex account. This happens only when you press Refresh.

That request goes to OpenAI and not to us. We receive nothing from it. OpenAI receives what Codex sends for any request on your account, under your agreement with OpenAI, and returns how much of each limit is used and when it resets. Agentbox keeps the answer on your computer.

Section 4 governs this section too. Nothing about your files, your code, your prompts or your paths is sent in order to read your usage.

6

Why we collect it

We use what is described in section 5 to see whether Agentbox 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.

What sections 5.7 and 5.8 describe is used only to run the service you chose and to show your work back to you and to the people you share it with.

7

Our legal basis, for people in the United Kingdom and the European Economic Area

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.

For Agentbox Cloud, described in section 5.7, and for the backup described in section 5.8, we rely on the need to provide the service you asked for under its terms.

8

Who else receives it

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.

A feedback message takes a different path and passes through two other companies, which receive only what is in the feedback box and nothing else in this policy. Supabase hosts the small program the application sends it to, and Resend delivers it to us as an email. Both act only on our instructions, neither keeps it for any purpose of its own, and neither receives the counts or the crash reports.

The three things that go anywhere else are the question in section 5.5, which asks GitHub whether a newer version of Agentbox has been released, the download in section 5.6, which asks Anthropic or OpenAI for its installer when you choose a plan during setup, and the usage question in section 5.9, which Codex asks OpenAI when you press Refresh. None of those companies is storing anything for us, and none receives the counts, the crash reports or anything from the feedback box.

Agentbox Cloud, described in section 5.7, uses three more. Amazon Web Services runs its computers and holds what a run carries, Supabase holds your Agentbox Cloud account, and Stripe takes payment for a plan. Amazon Web Services and Supabase act only on our instructions and for no purpose of their own. Stripe also keeps its own record of each payment, as the law requires of it, under its own privacy policy. If you sign in with Google, Google tells us which Google account signed in, under your own agreement with Google.

The backup described in section 5.8 is held by Supabase, which acts only on our instructions and for no purpose of its own.

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.

9

Where it is held

The counts and the crash reports described in sections 5.1 to 5.3 are stored by the service named first in section 8, in the United States. If you use Agentbox from another country, using it sends that information there.

A feedback message is not stored by that service at all. It passes through the two companies named after it in section 8 and arrives with us as an email, which we hold in our own mailbox.

What Agentbox Cloud carries and keeps is held by Amazon Web Services and Supabase in the United States. Stripe holds the record of your payments under its own privacy policy.

The backup described in section 5.8 is held by Supabase in the United States, encrypted while it is sent and while it is stored.

10

Turning it off

One setting in Agentbox controls all of it. It is on when you install Agentbox. 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.

The check for a newer version in section 5.5 is not part of that setting and keeps running, because it is how Agentbox repairs itself and how a fault you reported reaches you fixed. It sends us nothing either way.

Turning it off stops sending from that moment. It does not by itself delete what was sent before, which section 12 covers.

11

How long we keep it

We keep what arrives only for as long as it is useful for building, fixing and understanding the use of Agentbox, 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.

Agentbox Cloud is the exception, because there the periods are fixed. The copies a run leaves are deleted seven days after it. Your Agentbox Cloud account and its records are kept until you delete the account, apart from what the law requires us to keep for billing.

The backup described in section 5.8 is kept while you have an account. A thread you delete on your computer is deleted from it, and deleting your account deletes all of it.

12

Your rights

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 we will not withdraw an Agentbox Cloud plan because you did.

Unless you sign in, Agentbox holds no account, so what we receive from the counts and the crash reports 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.

If you sign in or use Agentbox Cloud, what we hold about you there is tied to the account you signed in with, and a request about it is made in the same way. Deleting your account deletes what sections 5.7 and 5.8 say we keep, apart from what the law requires us to keep for billing.

13

Children

Agentbox 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.

14

Security

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, unless you send it to Agentbox Cloud.

In Agentbox Cloud each run has a computer of its own that no other person's run can reach, what a run leaves behind is deleted after seven days, and your Claude or Codex sign in is never handed to your computer or to anyone else's.

15

Selling, sharing and advertising

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 Agentbox, 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.

Agentbox 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.

16

This website

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.

17

Changes to this policy, and how to reach us about it

Agentbox 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@agentbox.ac.