Privacy policy
What Base Captain collects about you, why, for how long, who else handles it, and what you may ask of us.
Last updated
Who we are
Base Captain, LLC (its address is on Legal) is the controller of the data on this page: for this site, for users and sign-up, for the app recommended when you make a base, for how Base Captain is used, for the totals we count across the bases, and for the billing of businesses. Write to [email protected] about anything here.
For the data a business keeps in Base Captain, the business is the controller and we are its processor, under the data processing agreement. We are the controller of the app recommended for a new base, of how Base Captain is used and of the totals across the bases.
This site
- The server’s log.
- This site sets no cookie and keeps nothing in your browser. Our web server logs each request: your IP address, the page, the time, your browser’s name and the page you came from. To deliver the site and protect it from abuse and floods: our legitimate interest in a site that works (GDPR Art. 6(1)(f)). The log is kept for 14 days, then deleted.
- The visits, counted.
- To see how many people visit this site, where they come from and which pages they read, each page sends PostHog, our analytics provider: the page’s address and title, the page you came from, what you clicked, how long you stayed on a page and how far you scrolled, your browser, your operating system and your kind of device, the size of your screen and window, your language and time zone, and your country, which Cloudflare reads from your IP address. The code that sends it is part of this site: no script is loaded from PostHog or from any other company.
- A visitor for a day, with no cookie.
- With each of these, PostHog receives your IP address. From it and your browser’s name, PostHog makes on its servers a number that stands for one visitor for one day. The next day’s number is another one, and PostHog deletes what it would need to make the first again. The events it keeps hold no IP address, and nothing in them names you or links one day’s visit to another’s.
- What you start here, counted too.
- When you make a base, sign up or start to pay for the Pro plan, our server tells PostHog that it happened, with your IP address, your browser’s name and your time zone, so that PostHog counts it for the same visitor of that day. It holds no name, no email address, no base and nothing you wrote. When a base first pays for the Pro plan, PostHog also gets how the base’s maker found us (below, under “You as a user”), with no visitor’s number and no base. A page of this site opened by a signed-in person says only that the person is signed in.
- Why, on what basis and how long.
- Our legitimate interest in knowing how this site is found and read (Art. 6(1)(f)). PostHog keeps the events in the EU, in Frankfurt, for two years, then deletes them. It handles them for us alone, and is on Subprocessors.
- How to stay out of the count.
- A browser that sends Global Privacy Control or Do Not Track is not counted: its pages send PostHog nothing. You may object at any time (Art. 21), and turning one of them on is how. Nothing in the events names you, so we cannot find yours among them; for anything else, write to [email protected].
- Writing to us.
- When you email us, we keep your message and address to answer it, and for as long as the conversation needs, on the same basis, or to take the steps you ask for before a contract (Art. 6(1)(b)).
You as a user
- What we keep.
- Your name and email address; a salted hash of your password, if you choose one (a password is optional); a sign-in code we mail you, kept hashed and good for 15 minutes, then deleted; your two-factor secret, if you turn it on; your settings, such as language, time zone and theme; the bases you belong to and your role in each; and, for each session, when it started and your browser’s name, so you can see and sign out your sessions.
- Why, and on what basis.
- To let you sign in and use Base Captain: the contract with you or with the business that invited you (Art. 6(1)(b)), and our and that business’s legitimate interest in running it securely (Art. 6(1)(f)). Without an email address you cannot be a user.
- How you found us.
- With a base you make, we keep the site that linked you to us, the campaign’s tags of that link, the first and the last page of this site you opened, and your country, which Cloudflare reads from your IP address: to know which pages and links bring customers, our legitimate interest (Art. 6(1)(f)). It is kept with the base and deleted with it. A browser that sends Global Privacy Control or Do Not Track gives none of it, and you may object at any time (Art. 21): write to us.
- Repeated attempts.
- To refuse repeated wrong passwords, wrong sign-in codes and other repeated attempts, your IP address is counted in memory for up to an hour and never written down.
- The server’s log.
- When you use the dashboard or a base, our web server logs each request in the same way as for this site: your IP address, the page, the time, your browser’s name and the page you came from. It never logs your passwords, cookies or sign-in links. To deliver the service and protect it from abuse: our legitimate interest in a service that works (Art. 6(1)(f)). The log is kept for 14 days, then deleted.
- Errors in a page.
- When a page of a base fails, it sends the error to the base: the page you were on, your role, the error’s words and the named parts you clicked, the pages you opened and the requests made just before it, with no value you typed or saw. The base’s builders read it on its Errors page, and we see it too. The error can also note where it happened in our data on how Base Captain is used (below), which only we see. To find and fix faults: our and the base’s legitimate interest in a service that works (Art. 6(1)(f)). An error is kept until 90 days after it last happened, then deleted.
- Faults you report through the assistant.
- When you tell the assistant that Base Captain itself fails, and it cannot fix this in your base, it reports the fault to us: what fails, as it writes it from your words, and what it checked. We receive this report with the name of the base, the conversation’s number and the version of the base, but not your name or your email address. The AI agents that we use to build Base Captain read the report to repair the fault; they run at Anthropic (see the subprocessors). Write in the chat only what you want us to read. To repair a fault that you asked us to repair: our and the base’s legitimate interest in a service that works (Art. 6(1)(f)). The report is kept in the base until 90 days after it was last made, and in our record of the repair for as long as that record. A base that keeps its data from the assistant and agents sends no report to the agents.
- Emails we send.
- Sign-in codes, invitations and the other emails we send to users, emails about your base’s plan and its limits, and notifications from your bases, sent through Amazon Web Services.
- How long.
- For as long as you are a user. A session’s record goes when it ends. To stop being a user and have this data deleted, write to us.
The app recommended for a new base
- What we keep.
- When you describe your business in Create your base, or when you or your AI describe it to make a temporary base, so that Base Captain recommends an app, we keep what you wrote (at most 500 characters on the dashboard, 2,000 for a temporary base), the app and add-ons recommended and why, the message sent to the AI model and its answer, the cost of the call, and the base you made from it. We keep who asked: your user, or, for a temporary base asked without one, the IP address the request came from.
- Why, and on what basis.
- To answer your request with an app: the contract with you, or the steps you ask for before one (Art. 6(1)(b)). To limit how many recommendations one person or one address asks for in a day: our legitimate interest in a service that is not abused (Art. 6(1)(f)). And, from 4 November 2026, when no app fits what you wrote, to decide what to build next: we read those texts to find kinds of business that need an app of their own. This is our legitimate interest in building what people ask for (Art. 6(1)(f)), and it serves the purpose you wrote the text for, an app for your business. We weigh it against a short text that you wrote about your business, read without your name, your email address or your IP address.
- Who sees it.
- We read the recommendations. The AI model that answers the request receives what you wrote (its host is on Subprocessors). When no app fits, the AI agents we build Base Captain with, which run at an AI provider, read what you wrote and nothing else: not who asked, the IP address or the answer, and only texts written from 4 November 2026. They read them in our own base where they work, which holds them while the review runs and keeps them in that review’s history. They note the kind of business it describes in their own words, with how many asked for it, never your text, a name of a person or a name of a business.
- How long.
- For as long as you are a user: when your user is deleted, its recommendations go with it. A recommendation asked without a user stays until we delete it. Write to us to have yours deleted sooner. Backups keep deleted data for 90 days more, then it is gone.
- Your right to object.
- You may object at any time to our reading of your texts to decide what to build (Art. 21). Write to [email protected], from the email address of your user or with the text you wrote, and we delete your recommendations or keep them out of that reading.
How Base Captain is used
- What we use.
- We may use data gathered from how Base Captain and its apps are used to improve our products.
- Who sees it.
- We do not share this data with other companies; only the providers that host Base Captain for us keep it.
- On what basis.
- Our legitimate interest in improving our products (Art. 6(1)(f)).
- How long.
- At most 30 days. Backups keep deleted data for 90 days more, then it is gone.
- Your right to object.
- You may object at any time (Art. 21): write to [email protected].
The totals across the bases
- What we count.
- Besides the data on how Base Captain is used, above, we count per week, across the bases together, how many faults of Base Captain were reported through the assistant, and how many runs that agents made by themselves fell short, by reason (failed, hit a limit, asked a person, stopped without finishing, done again, changed by a person). Each total holds a number, how many bases it came from, the week and that reason. It names no base and no person, and holds no chat, no words and no item. A chat counts only when the assistant reports a fault in it, and then only as one more fault, never its words (the report itself reaches us as Faults you report through the assistant, above, says).
- What we do not count.
- Asks the assistant or an agent could not meet are not counted: nothing records them, and we do not read chats to find them. A person’s chat with an agent never counts as a run.
- Why, and on what basis.
- To find what fails in Base Captain and to decide what to repair and build next: our legitimate interest in knowing how our product works (Art. 6(1)(f)). To make the totals we read, once a day, how many such rows each base has; no AI model is used. We decide this purpose, so we are the controller of this counting, not the business whose base it is. We weigh this interest against totals that name nobody and hold no words.
- Who sees it.
- We read the totals, and the AI agents we build Base Captain with, which run at an AI provider, may read them. They may also read totals across bases made from the data on how Base Captain is used, above. From this counting only totals reach those agents; from a base, only the faults reported through the assistant, above, reach them. Of what you write, they read only the texts that no app fits, under The app recommended for a new base above.
- How long.
- Each total is deleted after ninety days. Backups keep deleted data for 90 days more, then it is gone.
- How a base stays out.
- A base that keeps its data from the assistant and agents, in Settings, AI settings, is not counted. When an admin turns that on, the base leaves the current week’s totals at the next daily count; the totals of weeks that have ended stay, since they cannot be taken apart. Temporary bases, review copies and our own bases are not counted.
What is in the bases
- Your business decides.
- What a business keeps in Base Captain, customers, orders, people and the rest, is that business’s. It is the controller and we process that data only on its instructions, under the data processing agreement. For your rights over that data, write to the business first; we help it answer.
- The assistant and agents.
- The assistant reads the messages of the chats where it listens: each public channel, a thread where it answered a mention, and a private channel, a group chat or a direct message where one of its users added it; an agent of the base that a user adds to a chat reads the messages of that chat too. Conversations with the assistant and with agents are kept with the base, and nothing deletes them on its own. You can delete your conversation with the assistant, one part at a time. Report this answer shares one conversation with us, or one part of it, only when you choose to.
- How long.
- For as long as the base has a plan. The Free plan lasts 30 days. When it ends, or when the Pro plan stops, the base becomes read-only, and 30 days later we delete its data and its files. An owner can also delete the base’s data at any time. The base’s own record stays, with its owners, its billing details and its invoices. Our backups keep deleted data for 90 days more, then it is gone.
Your AI (Claude, ChatGPT)
- What we keep.
- When you connect your AI, such as Claude or ChatGPT, to Base Captain and click Allow, we keep its name and ID, the IP address you allowed it from, the bases you let it reach and whether it can create bases, when you connected it and when it last worked in your bases. Its connection is an API token: we keep the token only as a hash, in our records and in each base it reaches; your AI holds the token. The code of the sign-in is kept hashed, used once and good for 10 minutes, then deleted.
- How long.
- Until you revoke its token in Settings, API tokens, at www.basecaptain.com or in any of your bases, until you leave the one base you let it reach, or until you stop being a user. When you connect the same AI again, the new connection replaces the old one. You may have at most 50 API tokens.
- What your AI receives.
- Only the results of the tools it calls, such as the list of your bases or the items it asks for. Each call is done as you, under your role in each base, so your AI receives only what you may see. Base Captain sends nothing to your AI on its own, and receives only the calls it makes, not your conversation with it. The company that runs your AI, such as Anthropic or OpenAI, processes what it receives under its own terms and privacy policy.
- Why, and on what basis.
- To do what you ask your AI to do in Base Captain: the contract with you or with the business that invited you (Art. 6(1)(b)). The IP address limits how many temporary bases one address makes: our legitimate interest in a service that is not abused (Art. 6(1)(f)).
- Without signing up.
- If you continue without signing up, we make an anonymous user, with no name or email address of yours, and keep the temporary bases your AI makes for it, with what you put in them, the IP address each was made from and whether you passed the check that you are a person. A temporary base closes 24 hours after it is made, and 48 hours after it is made it is deleted, with all its data, unless you keep it. Then the anonymous user and the connection of your AI are deleted too. When you keep it, it becomes your base and we delete the IP address it was made from.
We do not use what your AI reads or writes through Base Captain to train AI models (No training). Write to [email protected] about anything here.
Billing
- What we keep.
- For each base with a plan: its owner’s email and name, its country, its plan and its payments, and the details an invoice needs. Upgrade to Pro suggests your country; we keep only the country you choose.
- Your card is Stripe’s.
- Stripe, Inc. takes the card, charges it, keeps it and sends the receipts. We never see or keep the card’s number.
- Why, and on what basis.
- To charge for the Pro plan: the contract (Art. 6(1)(b)); to keep the accounts and invoices: the accounting and tax law we must follow (Art. 6(1)(c)).
- How long.
- Invoices and payments for as long as accounting and tax law requires; the rest for as long as the base exists.
No training
Nothing you or your bases hold is used to train AI models, by us or by the model hosts that answer the assistant and the agents.
Who else handles it
The companies that host, protect and send for Base Captain, that run its AI models and that take its payments, are listed with where they are on Subprocessors. We give data to authorities only when the law requires it.
Some of them are in the USA. Those transfers rest on the EU–US Data Privacy Framework where the company is certified under it, and on the European Commission’s Standard Contractual Clauses otherwise.
Your rights
- What you may ask.
- To see the data we hold about you, to correct it, to have it deleted, to limit how we use it, to receive it in a common format, and to object to what we do on the basis of our legitimate interest (GDPR Art. 15 to 21).
- How.
- Write to [email protected]. We answer within one month, and tell you if we need longer and why.
- Complaints.
- You may complain to the data protection authority where you live or work.
- No automated decisions.
- We take no decision about you by automated means alone that has legal or similar effects on you.
Changes
We publish changes to this policy here with a new date, and tell customers by email before a change that matters applies.