Privacy policy

1. Who we are

Cassius is a spatial AI workspace, currently in private beta. It is run by Cassius Chat LLC, a Washington limited liability company, which decides how the information in this policy is used (in privacy law, the controller). This policy explains what we collect, why, where it is stored, who else handles it, how long we keep it and what you can ask of us.

It covers cassius.chat and the Cassius application. Where a feature has not launched yet, this policy says so and describes how it will work when it does. Our privacy contact is support@cassius.chat; it reaches the person responsible for personal information at Cassius.

2. Information we collect

Your account

When you create an account we collect your email address and an account identifier, and from your first sign-in we hold a record of each active session. You may give us a name to show in your sidebar; it is optional, you can clear it at any time, and if you do not give one we show the first part of your email address instead. We do not ask for a phone number, a company or a postal address.

We also store your preferences, so they follow you to any device: your theme, the dot floor, the interface scale, the media volume, the sidebar’s state, width and side, your key overrides, favourites and chat defaults, and which hints and switches you have turned on or off.

If you joined the waitlist, or asked us on the pricing or status page to email you when a plan opens or about the service’s status, we hold the address you gave us, what you asked to hear about and the date you gave it.

When you send us a report from the feedback form, we store it, and any screenshots you attach to it, with your account. We also store the address of the page you sent it from and your browser’s description of itself (its user-agent), to help us reproduce the problem. A screenshot shows whatever was on your screen, so leave out anything you do not want us to see.

Your workspace

When you are signed in we store the arrangement of your workspaces: their names, the order you keep them in, which ones you have pinned, which one you were last looking at, and where each pane sits on the floor. That is what comes back when you sign in again, on any device. It is held in our database, hosted by Neon, and it is attached to your account and to nobody else’s.

Your conversations and notes

When you are signed in we also store what is inside those panes: your conversations (the messages you send and the replies the model gives, along with each conversation’s title and which model you chose), the text of the notes you write and the whiteboards you draw (their shapes, their text and where they sit). They are held in the same database, attached to your account and to nobody else’s, and they are what comes back when you reload or sign in on another device. A conversation belongs to you rather than to a workspace, so deleting a workspace does not delete the conversations you were reading in it. Section 6 says how long each is kept.

When you are signed in we also store the files you add to a workspace or attach to a message (images, PDFs, audio and video), and for some of them a small preview picture, so they come back when you reload or sign in on another device. They are held by Cloudflare, attached to your account and to nobody else’s. Before an image is stored, the location and camera details its file carried are removed from it. Every image we store is checked by Microsoft’s PhotoDNA service, which compares it with known child sexual abuse material and does not keep it; an image stored before that check was available to us is checked as soon as it is. When you are signed out, the files you open are held in your browser only. If you open a file’s eye, or attach a file to a message, its contents are also sent to the model you chose, through the provider named in section 5, as part of that message; no file is sent to a model otherwise.

If you open the eye on a whiteboard or a note, its name and what it holds (its text, its shapes and where they sit, and for a model that reads images it may include a picture of it) are sent with each message you send from a chat on that floor while the eye stays open, to the model you chose, through the provider named in section 5. If you ask a chat about part of a whiteboard, that part is sent with that one message. Neither is sent otherwise.

While a whiteboard’s eye is open, each message also carries a short fixed note telling the model how to draw on a whiteboard. It holds nothing of yours.

When you are signed out we store nothing on our servers: your workspace lives in the tab and ends with it. The one exception is the moment you sign in from a signed-out floor, when your browser keeps that floor for up to thirty minutes so it can be offered to your account.

Sending to a model

What you send to a model is carried to it so it can answer you. We do not use your content to train any model, and we train none. Section 5 names the provider that carries it and says what the model’s own provider may keep.

Your plan and payments

If we give your account a plan without charge, we store which plan it is, that we gave it rather than you buying it, and when it began. It is attached to your account and to nobody else’s, and it is removed with your account. It decides which models you can use and how large your usage allowance is.

If you buy a plan, Stripe takes your payment. Your card details go to Stripe and never reach us. We keep Stripe’s identifiers for you and your subscription, the plan and billing period you chose, its price, its status and its dates, and the invoices it has paid, so we know which plan you are on.

Usage records

When you are signed in, every request we make to a model for you is recorded as a usage record. That includes replies you stopped or that failed, and the short requests that name a new workspace for you. A usage record holds when the request was made, whether it was for a reply or to name a workspace, which plan you were on and whether the request counted against your usage allowance, which model and which of its providers handled it, how many tokens it used, what it cost us and the most it could cost, which we set aside before it runs, whether it ran on our own account with that provider and, if so, what the provider billed us directly, how it ended, and the provider’s identifier for that request. It holds no message text and no identifier of the conversation, workspace or message it came from. Deleting a conversation does not remove its usage records; they are removed on the schedule in section 6.

We also keep, for your account, when your latest usage session started. A usage session is the five hours that begin with your first request after the last one ended, and when it started is how we know when your allowance resets. It is removed with your account.

Sign-in records

When you sign in, we store one record of that session on our servers: a random session identifier, a reference to your account, and the times the session was created and last used. We do not store your device name, your browser’s user-agent string, or your location alongside it. When you sign out, we delete it. When you reset your password, we delete every one of them, on every device, so a reset locks out anyone who had access.

Our hosts see the internet address and browser details of every request, as any website’s do. We use the address, held only in memory and never with your account, to slow down repeated sign-in attempts and other abuse.

Voice

Voice input uses the speech recognition built into your browser. Depending on your browser and its settings, the browser may send your audio to its maker’s speech service, such as Google for Chrome, Apple for Safari or Microsoft for Edge, or it may recognize speech on your device. Your audio never reaches our servers, and we do not store it. Replies read aloud are spoken by your browser’s own voice, which may run on your device or send the words to your browser maker’s speech service. Nothing about a reply is sent to our servers to read it aloud.

On your device

A cookie is a small piece of data a site asks your browser to keep and hand back on later requests. Cassius uses cookies for five things, and every one of them is necessary to operate the service: remembering that you entered the beta code, keeping you signed in, showing who is signed in before a page has finished loading, carrying a sign-in that is halfway through, and recognizing a browser that has signed in to your account before, so someone guessing your password elsewhere cannot keep you out. Six cookies do that work and all six are ours: four are kept 30 days, and two are kept 10 minutes. We set no analytics, advertising or tracking cookie of any kind, we run no analytics, trackers, advertising pixels or session recording today, and none of them lets a third party access any of your information.

Cassius also keeps things in your browser’s own storage, for you and nobody else: your theme, dot floor, interface scale, volume and sidebar settings, so the page is right before your account answers; while signed in, copies of your files and of edits not yet saved, so nothing is lost if the connection drops; and the floor described above while you sign in. None of it is used to track you. Deleting your account clears it from your browser, except your theme, which stays so the next page does not flash.

Features that have not launched yet

These are planned for the beta or soon after. Until each launches, none of what follows is collected.

• Shared workspaces. You will be able to invite people to a workspace by a link, which anyone holding it can use to join while it is valid, or by email, in which case we send an invitation to the address you enter. Everyone in a shared workspace sees its panes, conversations, notes, whiteboards and files, the display name of each member, who is present and where their cursor is, which member sent each message, and how many members there are. A member’s open eye sends a note or whiteboard with that member’s own messages to the model they chose. A shared workspace’s owner decides who stays in it.
• The agent. An assistant that acts inside your workspace when you ask it to: it reads what you point it at, and it can create and change panes, notes and whiteboards for you. What it reads is sent to the model it runs on, as for a chat. How much it can do depends on your plan.
• Image generation, in a chat and in its own pane. Your prompt, and any image you give it, are sent to the image model you choose. Generated images are stored and checked like any other image.
• Web search, for paid plans. When a reply needs a search, the search words are sent to a third-party search provider, which we will name in section 5 when it launches, and the results go to the model.
• Memory. If you turn it on, Cassius will remember things about you from your conversations, such as your preferences and projects, and give them to the model in later conversations. It will be off until you turn it on; you will be able to see, edit and delete what it remembers, and turning it off deletes it.
• Product analytics, through PostHog, to learn which parts of Cassius are used and where people get stuck. It will set no cookie and keep nothing on your device, it will record what you do in the interface (such as which commands you run) but never what you write, upload or receive from a model, and you will be able to turn it off in settings.
• More ways to sign in, such as GitHub and Microsoft. Like Google, they will give us only your email address and whether it is verified.
• A link to book a call with the founder, which opens a third-party booking page under its own privacy policy.

3. How we use information

We use what is described above only to provide and secure the service: to create your account, to sign you in and keep you signed in, to deliver your requests to the model you chose, to show you how much of your usage allowance you have used and to stop requests once it is used, to decide which models your plan includes, to take payment for a plan you buy, to store your files and check the images among them, to check what our model provider bills us against what we recorded, to work out what the service costs to run, to answer you when you write to us, to protect the service from abuse, to improve it, and to make the report section 6 describes.

We do not sell your information. We do not share it for advertising. We do not use your content to train models, and we train none. We make no decision about you by automated means alone that has a legal or similarly significant effect; automatic limits that refuse a request, such as a usage allowance or a sign-in slowdown, can be reviewed by writing to us.

Our legal reasons

Where the law asks for a legal basis (for example in the United Kingdom), ours are: performing our contract with you, for running your account, storing your work, sending your requests to models and taking payment; our legitimate interests, for keeping the service secure, preventing abuse, checking images, answering you, and understanding and improving the service; our legal obligations, for tax records and the report section 6 describes; and your consent, for memory and anything else we ask you to turn on, which you can withdraw at any time.

When we look at your account

Cassius is run by a very small team. The people who run it can see accounts, workspaces, conversations and files, and they look at them only when needed: to keep the service running and fix faults, to keep it safe and investigate abuse or a report, to help you when you ask, to understand how the service is used so we can improve it (never from health information, section 9), and when the law requires. They do not browse your work out of curiosity, sell it, or use it to train models, and they are bound to keep it confidential. We read the feedback you send us.

4. Google user data

This section describes what we do with data obtained from your Google Account when you choose to sign in with Google. It applies in addition to the rest of this policy, and our use of that data adheres to the Google API Services User Data Policy, including its Limited Use requirements.

What we access

Your email address, whether Google has verified it, and an opaque account identifier issued by our authentication provider. We do not receive your name, your profile picture, your contacts, your calendar, your files, or anything else in your Google Account.

How we use it

For one purpose: creating your Cassius account and signing you in. We use it for nothing else.

Where we store it

Your identity and your sign-in tokens are held by our authentication provider, WorkOS. Your email address, your account identifier, your sign-in records and your workspace arrangement are held in our database, hosted by Neon. We never receive or store your Google password.

What we share

Nothing beyond the processors named in section 5, each of which handles it only to operate the service on our behalf, and the report the law requires that section 6 describes. We never sell Google user data, never transfer it to anyone for advertising, and never use it for advertising ourselves.

How to have it deleted

Delete your account from inside Cassius: open the command palette and choose “delete your account”. You will be asked to type your email address to confirm. Section 6 says exactly what is removed. You can also email support@cassius.chat from the address on your account and we will do it for you.

5. Service providers

We use seven service providers, and this is the complete list. Each processes data only to operate the service on our behalf.

WorkOS

Authentication. Holds your identity, your password if you set one, and sends the mail our sign-up and password-reset flows produce. It receives the internet address and browser details of each sign-in, to protect your account.

Neon

Our database. Holds your account, your workspaces, conversations, notes and whiteboards, and your usage records.

Vercel

Hosting. Every request to Cassius arrives through Vercel, except the files you store, which go to and come back from Cloudflare.

Cloudflare

File storage. Holds the files you store while signed in and sends them back to you. Cloudflare keeps them in the United States; while sending one, it may keep a short-lived copy closer to you.

Microsoft

Image checking. Its PhotoDNA service compares each image we store with known child sexual abuse material, and does not keep it.

OpenRouter

Model routing. Carries what you send to a model to that model’s provider, and the model’s reply back.

Stripe

Payments. Takes payment for a plan you buy, sends your receipts and lets you manage or cancel your subscription. For fraud prevention and its own legal duties Stripe acts on its own account, under its own privacy policy.

The model you choose is run by its own provider, such as Anthropic, OpenAI, Google, xAI, Mistral, Meta, DeepSeek, Alibaba, Moonshot, Z.ai, MiniMax or Xiaomi, or by a company hosting that provider’s model. OpenRouter does not keep what you send unless we turn on its logging, which we have not. A model’s provider receives your message and may keep it for a limited time, commonly up to thirty days, to detect abuse, and some hosts may use it to improve their models; what it does is governed by its own policy and not by this one. Some providers and hosts process requests outside the United States, including in China and Singapore; the model list in Cassius shows whose model you are using.

Your browser’s speech recognition service, if it uses one for voice input, is your browser maker’s and not ours, and is governed by your browser maker’s policy.

Cassius also includes open-source software written by others, which runs in your browser and sends nothing to its authors. Its licence notices are at licenses.txt.

6. How long we keep it

We keep your account information for as long as your account exists. When you delete your account we remove it and everything attached to it: your workspaces, your conversations and every message in them, your notes, your whiteboards, your usage records, when your latest usage session started, your plan if we gave you one, the reports you sent us from the feedback form, the files you stored, every signed-in session, your waitlist entry if you have one, your customer record at Stripe, which cancels any subscription at once, and your identity at WorkOS. That happens while you wait, not on a schedule, and it is not a mark: the rows are gone. The files themselves are erased from storage within a few days. What Cassius had put in your browser is cleared from it at the same moment, apart from your theme, and every other tab you had open is signed out. There is no undo. A waitlist address you never turned into an account is held until the beta ends or until you ask us to remove it.

Stripe keeps its records of your payments and invoices for as long as tax and accounting law requires, even after your account is deleted. Our database provider keeps a restorable history of the database for up to seven days, so a removed row can remain there for up to seven days before it is gone for good.

Your workspace arrangement, your conversations, your notes and your whiteboards are kept for as long as your account exists. When you delete a workspace or a conversation we mark it deleted immediately and stop serving it, and the same goes for the notes and whiteboards on a workspace you delete. When you close a note or a whiteboard, we mark it deleted within eight days, once no workspace of yours has shown it for seven. Either way, the rows are removed automatically, every day, once they have been marked for more than thirty days. The window is a safety net for a deletion you did not mean, not a feature, and nothing in the product offers to bring a deleted item back.

Files you add while signed in are kept for as long as your account exists and a workspace, a conversation or a feedback report of yours holds them. A file you remove from all of them is marked deleted once nothing of yours has held it for seven days, removed once it has been marked for more than thirty, and erased from storage within a day after that. A feedback report holds the screenshots attached to it for ninety days. Files you open while signed out never reach us, and a file you send to a model is carried to it and not kept.

Usage records are removed automatically, every day, once they are more than thirty-five days old. We also keep daily totals for each model, split by kind of request (a reply or naming a workspace), by plan and by whether it ran on our own account with the provider: what was spent on it, how many requests it served, how many tokens it used and how many characters of prompt text were sent to it on a given day. They hold no account identifier, and they are kept after an account is deleted.

A sign-in record lasts until you sign out, until the session’s own thirty-day lifetime ends, or until a password reset or account deletion removes it, whichever comes first. Cookies expire on the schedule in section 2.

One thing overrides the rest of this section. If an image matches known child sexual abuse material, we refuse it, or stop serving it if it was already stored, report it to the National Center for Missing & Exploited Children as United States law requires, and keep that image, the details of the account that added it and, where we have it, the internet address it came from, apart from everything else and with access restricted, for one year, as the law requires, even if the account is deleted. We may also disclose information when the law requires it, or to protect someone from serious harm.

7. Security

Every request to Cassius is served over an encrypted connection, and our responses instruct browsers never to use an unencrypted one. Your session cookie is encrypted and authenticated before it is set, so neither a script in your browser nor a party in transit can read or alter it. We never receive or hold a plaintext password: passwords are handled by WorkOS, which stores them hashed. Your workspaces, conversations and files are not end-to-end encrypted: our systems can read them, which is how they reach a model and come back to you.

No system is perfectly secure and we do not claim otherwise. Cassius is beta software and should be treated as such. If a breach puts you at risk, we will tell you and the regulators the law requires us to tell.

8. Your rights

You can delete your account yourself, at any time, from the command palette inside Cassius. You can also ask us for a copy of the information we hold about you, in a form you can take elsewhere, ask us to correct it or delete it, ask us to stop or limit a use of it, object to a use based on our legitimate interests, and withdraw any consent you gave. Email support@cassius.chat from the address on your account. We answer within a month, and we may need to confirm it is you first. There is no charge.

We give these rights to everyone, wherever you live. Depending on where you live you may have further rights under local law, and we will honour them. If you are unhappy with how we handled your information, please tell us first; you can also complain to your regulator, such as the Information Commissioner’s Office in the United Kingdom, the Office of the Privacy Commissioner of Canada, or the Commission d’accès à l’information in Québec.

Your browser may send a Do Not Track or Global Privacy Control signal. We track no one across other sites, so there is nothing for it to turn off; when product analytics launch, we will treat either signal as turning them off.

9. Consumer health data

Cassius does not ask about your health, but you may write about it in a conversation, a note or a whiteboard, add a file that shows it, or a model may infer something about it from what you send. That can be anything about your physical or mental health, such as symptoms, conditions, diagnoses, medicines, treatment or therapy, and what a model says about it. Washington’s My Health My Data Act, and similar laws in other states, call that consumer health data. This section is our policy for it; the rest of this policy applies to it as well.

It comes only from you and from the replies a model writes for you. We collect it as part of what you choose to store or send, and use it only to provide the service you asked for: to keep it for you and show it back to you, to send it to the model you chose and return the reply, to check images as section 2 describes, to fix faults, to keep the service secure, and to help you when you ask. We do not use it to improve the service, for advertising or to train models, and we never sell it.

We share those same categories only with the providers in section 5 that hold or carry your content (Neon, Vercel, Cloudflare, OpenRouter and, for images, Microsoft), with the provider of the model you chose, and, as section 6 describes, with the National Center for Missing & Exploited Children or others when the law requires it or to protect someone from serious harm. A model’s provider may keep what it receives for a limited time, and some hosts may use it to improve their models, as section 5 says; choose your model with that in mind. We will ask for your consent before collecting or sharing it for any other purpose.

You can ask us whether we collect or share your consumer health data, for a copy of it with a list of the providers we have shared it with and how to reach them, to delete it, and to withdraw any consent you gave. You can delete what you stored, or your whole account, yourself, as section 6 describes, or write to support@cassius.chat; we answer as section 8 says. If we decline a request, reply to appeal and we will answer within 45 days; if you still disagree, you can complain to the Washington State Attorney General.

Cassius is not a medical service, and we suggest you keep health records that others regulate, such as a patient’s records, out of it.

10. Where your information is processed

We are in the United States, and your information is stored and processed there by us and the providers in section 5, and by a model’s provider wherever it operates. If you live elsewhere, that means it leaves your country, and courts, law enforcement and national security authorities in those countries may be able to reach it under their law. Where the law of your country requires a safeguard for that transfer, we rely on the standard contractual terms our providers offer, where they offer them; not every model provider does, so choose your model with that in mind. Write to us for a copy of what applies.

11. Age

Cassius is for people aged 18 and over, and is not directed at children. We do not knowingly collect information from anyone under 18. If we learn that an account belongs to someone under 18, we close it and delete its information as section 6 describes. If you believe that has happened, write to us.

12. Changes to this policy

When our practices change we change this page and the date under its title. If a change matters, such as using your information in a new way, we will tell you in Cassius or by email before it takes effect, and we will ask for your consent where the law requires it. We will never start using what you have already stored to train models without asking you first.

13. Contact us

Cassius Chat LLC, a Washington limited liability company. Email support@cassius.chat.