Privacy Policy

Effective: [DATE] · Status: Beta

Before publishing: fill every [BRACKETED] value. §8 (international transfers) and the DPA need a lawyer's review — see the note about processing from Ukraine. Not legal advice.

[PRODUCT] is a hosted computer for professional AI work. Your tools, your logins, your quotas — on a machine that stays awake and that your teammates can reach.

• Your work stays on your machine. Files, prompts, model responses, and credentials live on the computer we host for you. We do not copy them into our systems.
• Your AI sessions are between you and your AI provider. You authenticate with your own account. We are not in the middle of that traffic and we do not store it.
• Our systems hold pointers, not content — who you are, what machines you run, and the labels and schedules you attach to them.
• We do not sell your data, share it with advertisers, or use it to train any model.

The rest of this document is the detail. One exception runs through it: our own website, the demo chat with Alex and Alex's Discord DMs and mentions are our surfaces, not your Computer. What you send there, we keep: §5 says what and for how long.

[COMPANY LEGAL NAME], a Delaware limited liability company, [ADDRESS]. Privacy contact: [PRIVACY EMAIL] [EU/UK representative under GDPR Art. 27, if appointed — otherwise delete]

Our roles. The Service is offered for business use only.

• For account data — your registration details, billing, and login records — we are the data controller.
• For the content you and your team put on your Machines, you are the controller and we act as a processor on your instructions. Our Data Processing Agreement governs that relationship; request it at [PRIVACY EMAIL].
• For what you send on our marketing surfaces (the landing page, the demo chat with Alex and Alex's Discord DMs and mentions, §5) we are the data controller. There is no processor relationship and no DPA for that data; you are not a customer there, you are a visitor.

Described by category rather than by feature, so it stays accurate as the product develops.

Account and organisation data — such as your organisation name, the people in it, their names and email addresses, authentication identifiers, roles and permissions, and billing records. Card details are handled by our payment provider; we never see or store them.

Machine records — such as the Machines you run, their identifiers, status, configuration, region, resource usage, and which people can reach them.

Labels and scheduling — the short names you give things, and when those things run. This includes titles of threads, automations, and projects, together with schedules, run history, and last-activity timestamps. It is limited to names and timing. It does not include the contents of anything named.

Operational records — such as request and error logs, security events, IP addresses, and audit records of administrative access.

Marketing-surface data — what visitors send us on the landing page, in the demo chat with Alex and in Alex's Discord DMs and mentions. It is the one category that holds content rather than pointers:

• Demo conversations. The transcript of each chat with Alex, held on our demo Computer, not in the platform database.
• Waitlist entries. Your email address, the optional note you add on the form, where the sign-up came from (the landing form, the chat with Alex, a Discord DM or the early-access wall), whether you confirmed it, where you heard about us (one value from a short list), and, if you accepted analytics in the cookie banner, the random analytics identifier from your browser so your confirmation is counted once. Nothing else identifies you.
• Waitlist profiles. What you told Alex about your work, attached to your sign-up: your job and your current workaround as short free text (200 characters each), and three answers from fixed lists: which agent harnesses you use, how often you want an agent running, and where you want to reach it. Alex notes these only when you sign up through him; the form never asks for them.
• Roadmap interest. Which roadmap item a visitor asked Alex about, and whether its absence is a dealbreaker, as a count. Each count carries the item and the answer from fixed lists and nothing else: no chat text, no email, no identifier that could join it to a conversation or a person.

We hold this because the Service needs it to authenticate you, render your interface, enforce who can reach which Machine, run things on schedule, bill you, and stay secure.

This list is exhaustive for your Computers and does not change as we add features. On the Computers we host for you, we do not store, copy, or retain:

• File contents on your Machines
• Message and session contents from your threads — including preview text shown in a thread list, which is fetched live from your Machine when you view it and held only in your browser
• Prompts, files, or responses exchanged with your AI provider
• Credentials you place on a Machine, including AI provider credentials
• Free-text bodies you write inside a session

Two consequences you will notice:

• When a Machine is offline we cannot show previews of what is on it. There is nothing on our side to display.
• Search covers titles, because titles are the only thread content our systems hold.

This section is about your Computers. Our demo Computer, the one Alex runs on, is ours, and what you send him is the exception, described in §5.

You authenticate to your AI provider using your own account and subscription. That traffic goes directly from your Machine to them, under their terms and their privacy policy. We do not proxy it, log it, or store it, and we have no access to your provider account.

Your relationship with your provider is your own. Read their privacy terms — they govern what happens to the prompts and files you send.

Alex is an AI. Our team reads conversations to improve the product.

Alex (@AlexFromSales) is an AI agent that answers the chat on our landing page and direct messages and mentions on Discord. He runs on a Computer we operate, the demo Computer. It is ours, so §3 to §4 do not apply to it: what you send Alex goes to us, and this section says what happens to it.

The AI provider is ours. §4 describes your Computer talking to your AI provider. Alex's Computer talks to ours: your messages to Alex are sent to OpenAI under our agreement with them, listed in §9, not under yours. Do not send Alex anything you would not send a sales team.

Transcripts stay on the demo Computer. Every conversation with Alex is kept as a transcript on the demo Computer. Members of our team who administer that Computer can read them, and we do, to see where Alex misleads, where the product confuses people and what people ask for. We do not copy transcripts into our database, and we do not use them to train any model.

Discord keeps its own copy. A DM or mention on Discord is also held by Discord under Discord's privacy policy, which we do not control.

Joining the waitlist through Alex. Only when you ask Alex to add you and type your own address does he submit it. Your sign-up is the same double opt-in as the form: you are on the list only after you click the link in the confirmation email. With a sign-up made through Alex, he also notes what you told him about your work: your job, your current workaround, the harnesses you use, how often you want an agent running and where you want to reach it. The free-text answers are capped at 200 characters each; the rest are values from fixed lists. They are stored with your waitlist entry, in our database, and nowhere else: they are not sent to our analytics tool, and they are deleted with the entry or earlier on request (§11). Alex does not ask you to agree to this separately; the notice under the chat input says it before your first message, and this section says it in full.

Roadmap counts. When you ask Alex about something we have not built, he records that someone asked about that item and whether its absence is a dealbreaker. The record is a count under a fixed item name with a fixed answer. It carries no chat text, no email, no browser or account identifier and no link to the conversation: nothing in it identifies you, and we do not join it to conversations. It is sent from the demo Computer, not from your browser, so the cookie banner neither enables nor disables it (§13).

Discord mentions in public channels. Alex never asks for an email address where other people can read it. He invites you to a direct message instead.

Keeping and deleting it. Transcripts, waitlist entries and waitlist profiles are kept for up to 12 months (§10). To have yours deleted earlier, write to [PRIVACY EMAIL] (§11).

Machines run on infrastructure operated by our hosting sub-processors.

Stated plainly: we operate the hosting layer, so we hold technical administrative access to the underlying infrastructure. What we commit to is when we use it.

We do not access the contents of your Machine. There are exactly two circumstances in which we do:

• You grant it. Support access requires your explicit grant. It is time-limited, logged, and you can revoke it at any time.
• We are legally compelled. Where we are permitted to tell you first, we will.

Security incidents are handled without accessing your data. Where a Machine poses an active security threat to you, to other customers, or to third parties, we may suspend it. Suspension halts execution and network access; it does not involve reading the Machine's contents. We will notify you. We may preserve a suspended Machine's disk without examining it, and will not examine it without your grant or a legal order.

We do not browse, index, scan, or train on the contents of your Machines.

Storage is encrypted at rest. Traffic between you and your Machine is encrypted in transit.

Where we rely on legitimate interests on our marketing surfaces, we keep the footprint small on purpose: we tell you before your first message, free text is capped, nothing you say reaches our analytics tool, retention is fixed (§10) and we delete on request (§11).

We are a US company. Our infrastructure sub-processors operate in [REGIONS]. Our personnel access administrative systems from [COUNTRIES, INCLUDING UKRAINE].

For transfers of personal data out of the EEA or UK we rely on [SCCs / UK IDTA / other mechanism — CONFIRM WITH COUNSEL]. A copy of the relevant transfer mechanism is available on request at [PRIVACY EMAIL].

We use third-party providers for hosting and infrastructure, database services, transactional email, payment processing, error and performance monitoring, and the AI model provider that runs Alex on our demo Computer.

Our current list is published at [SUB-PROCESSOR PAGE URL]. We post notice there before adding a new sub-processor.

We do not sell personal data. We do not share it with advertisers. We do not use it to train any model.

We disclose data to authorities only where legally required. Where we are permitted to do so, we will notify you before disclosing your data in response to legal process.

We keep your data while your account is active and delete it within a reasonable period after closure, except where law requires us to retain records.

• Deleting a Machine destroys its disk. Backups are purged on our standard cycle.
• Labels and schedules are deleted with the Machine or item they belong to.
• Operational logs are kept for a limited period.
• Transcripts of conversations with Alex are kept on the demo Computer for up to 12 months after the conversation's last message, and deleted earlier on request.
• A waitlist entry and its profile are kept together for up to 12 months, and deleted together on request.
• Roadmap counts are kept in our analytics tool for [its standard retention]. They identify nobody, so deletion requests do not reach them.

Specific retention windows are set out in our Data Processing Agreement.

Depending on where you are, you may have the right to access, correct, delete, export, or restrict processing of your personal data, and to object to processing based on legitimate interests.

Contact [PRIVACY EMAIL]. We respond within [30] days and do not charge for reasonable requests.

Where we process data on behalf of your employer, we will refer your request to them — they are the controller.

You may lodge a complaint with your local supervisory authority. If you are in the EEA, a list is available from the European Data Protection Board.

California. If you are a California resident, you have rights under the CCPA/CPRA including access, deletion, correction, and portability. We do not sell or share personal information as those terms are defined. We will not discriminate against you for exercising these rights.

We apply commercially reasonable technical and organisational measures, including encryption in transit and at rest, tenant isolation enforced at the database level, deny-by-default access controls, and audit logging of administrative access. Details are on our Security page.

Our strongest protection is architectural. What we hold centrally is limited by design, so the impact of any failure in our systems is bounded by the categories in §2. The contents of your Computers and your AI sessions are not among them. Conversations with Alex are, and they live on one Computer we operate, under the same controls as any other.

This is beta software. No system is perfectly secure and we cannot guarantee our measures will prevent every failure. If a breach affects personal data we will notify you and the relevant authorities as required by law.

Report a vulnerability: [SECURITY EMAIL].

We use two categories of cookies and similar browser storage:

When you first visit, a banner asks whether to allow analytics. Until you choose Accept, the analytics tool is not loaded: it sends nothing and stores nothing in your browser. Choosing Decline keeps the Service fully usable.

You can change your choice at any time with Cookie settings in the site footer. Withdrawing consent stops analytics immediately and deletes the analytics identifiers stored in your browser. It does not affect processing that happened before you withdrew.

The banner governs analytics in your browser. Two things it does not govern, because they use no cookie and no browser storage: the counts our servers record when a sign-up is submitted or confirmed, which carry no personal data, and the roadmap counts Alex records from the demo Computer (§5). Both run whether you chose Accept or Decline.

The Service is for business use by adults. It is not directed to anyone under 18 and we do not knowingly collect their personal data.

We post changes here and update the effective date. For material changes we notify account holders by email at least [14] days in advance.

[PRIVACY EMAIL] · [COMPANY LEGAL NAME] · [ADDRESS]