Trust
Last updated October 22, 2026
The short version for a security review. The detail is on Security and Privacy.
Where your data lives
Accounts, rooms, messages, AI replies and uploaded files are stored in Supabase: its Postgres database, its sign-in service and its file storage. The app itself runs as one server we operate with our hosting provider. The master key that protects saved API keys is held in AWS’s hardware key-management service and never leaves it.
In a room with more than one member, the room’s AI can send a member a private note, and a member can whisper to an AI. Other members see that it happened, not what it says. It is stored in the same database as other messages, goes to the AI’s provider as part of the conversation, and can be read by the people who run splitscreen when needed to run, secure or support the service. Once a chat contains private content, web search, images, code, notes and polls are turned off in that chat.
Who processes it
These companies process data for us, each for one job. We add no third-party analytics, ad trackers or data brokers, and we sell nothing.
Anthropic · Claude replies
The messages someone pointed at Claude, with the earlier asks and replies and the recent messages in that chat sent as context, display names, and attachments on those messages. In a room where Claude follows along, the messages posted there without a tag too. Private notes and whispers in that chat go too, when Claude is asked.
OpenAI · GPT replies
The messages someone pointed at GPT, with the earlier asks and replies and the recent messages in that chat sent as context, display names, and attachments on those messages. In a room where GPT follows along, the messages posted there without a tag too. Private notes and whispers in that chat go too, when GPT is asked.
Google · Gemini replies, and Google sign-in
For Gemini, the same as above with Gemini in place of Claude, on paid tier access. For sign-in, the Google sign-in itself, if you choose it.
Supabase · Database, sign-in, realtime and file storage
Everything the product stores: accounts, rooms, messages, replies and files.
Stripe · Payments
Your card details, which Stripe collects directly. We never see the card number.
Resend · Email delivery
The recipient address and the email we send.
GitHub · Repository features, for rooms that connect one
What a commit needs: the proposed files, a commit message, the branch, and who asked in which room.
Expo · Push notifications for the phone app
The device push token and the notification: one line of title and a short preview, with anything that looks like a credential hidden.
Cloudflare · Network: DNS, encryption and delivery for every request to splitscreen.chat; bot check on sign-up and the contact form (Turnstile)
All traffic to and from the site while in transit, including your IP address. It caches only public code and font files.
Amazon Web Services · Key management (KMS)
Requests to wrap and unwrap the data keys that seal API keys, with the account or workspace id each is bound to. Never an API key, and never a message.
ImprovMX · Forwarding mail sent to our contact address
Email sent to contact@splitscreen.chat: the sender, the message and any attachments, passed on to our inbox.
Our hosting provider · Runs the app server
Requests in transit and short-lived server logs, which carry no message bodies or keys.
How API keys are protected
- Each saved key is encrypted with AES-256-GCM under its own data key. That data key is wrapped by a master key in AWS KMS and bound to your account, so a key copied to another row fails to decrypt.
- A copy of our database alone cannot reveal a key. Keys are decrypted in server memory for one request, never logged, and never sent to a browser.
- After saving, only the last four characters are ever shown, to anyone, including you.
- splitscreen’s own provider keys, used when you pay with credits, are sealed the same way and can never be swapped for a member’s.
No model training
splitscreen does not train AI models on your content. Under Anthropic’s, OpenAI’s and Google’s API terms, content sent through their APIs is not used to train their models by default, and splitscreen uses paid tier Gemini access, which is not used to improve Google’s products.
Chat nobody pointed at an AI reaches a model provider through us in three cases. When someone asks an AI, the recent messages posted in that chat go with the question as context, unless the room’s owner turned that off. A message you ask us to translate, when your browser cannot translate it on the device, goes to a model the room allows, on our account, including in rooms that pay with a company key. And in a room where “AI follows along” is on, messages posted without a tag go to that room’s AI so it can decide whether to reply. It is on by default in a personal room with no other members, using the room’s default AI, and the owner can turn it off. In a room with more than one member it is off until the owner turns it on. It is not offered in rooms a workspace pays for.
Access and spending controls
- Every table is behind row-level security, and budget changes run only through database functions the browser cannot call.
- Budgets and caps are reserved in the database before any AI call starts, so a reply cannot cost more than what is left.
- Two-factor sign-in with an authenticator app, in Settings.
- Workspaces with roles (owner, admin, billing, member) and email domains proved by a DNS record.
- Single sign-on (SAML) for verified domains. Workspace owners and admins set it up themselves, at no extra charge. Support is needed when SSO is not yet switched on for the server, or to finish making “Require SSO” apply beyond the sign-in page.
- Room owners see who joined, left, was removed or changed settings, for 90 days.
- Workspace owners and admins get an activity log they can filter and export, and can stream it to their own webhook, Splunk or Datadog. Webhook requests are signed.
How long we keep things
- Messages, replies and files: until you or a room owner deletes them, or a workspace’s retention period removes them. Deleting your account removes every room you own. Messages you posted in other people’s rooms stay, with your account id cleared.
- A room’s activity record (joins, removals, settings changes): 90 days.
- A workspace’s activity log: 1 year.
- What a connected agent did (tools, rooms, costs, never a message): 30 days.
- A workspace owner can set a retention period of 30, 90, 180 or 365 days, and place a legal hold that stops held content from being deleted.
- Product analytics events: 180 days, never with message content.
- Records of purchases: 7 years after the sale, as tax law requires, with nothing that says who you were once your account is deleted.
- Files sent to a code sandbox: uploaded to the provider with a one-hour expiry and never reused.
- Server logs: short-lived request logs kept by our hosting and network providers, with no message bodies or keys.
- Messages sent from the contact page: one year.
Deleting your account and data
You can delete your account yourself, in Settings under Account, and it is permanent. The one exception is a legal hold placed by a workspace you belong to: while it lasts, the account cannot be deleted. Revoking an API key takes effect immediately. If you have a subscription or unused credit to refund, email contact@splitscreen.chat from the address on the account and we cancel, refund and delete together within 30 days. The privacy page lists exactly what goes and what stays.
Compliance and contracts
- SOC 2: preparing. We are putting the policies and controls an audit checks in place. A report will be available on request once an audit is complete.
- Data processing addendum: a draft DPA for business customers, with standard contractual clauses. Contact us to sign.
- EU data residency is not offered today. Talk to us if you need it.
- Security questionnaires: email contact@splitscreen.chat and we will answer from this page and our internal policies.
Report a security issue
Email contact@splitscreen.chat. We read security mail first, and will credit you if you want. The same address is in our security.txt.