last updated September 3, 2026
splitscreen holds credentials that can spend your money, so the security model is the product. Here is how it actually works — specifically, not vaguely.
Every key is encrypted with AES-256-GCM under its own data key; that data key is wrapped by a master key held in a hardware KMS and bound to your user account, so ciphertext moved to another row fails to decrypt. Recovering any key requires both our database and live KMS credentials — a database dump alone is worthless. Keys are decrypted in memory, per request, and never logged. The database table holding them accepts no client reads at all, even from you.
A reply paid with credits runs on splitscreen’s own provider accounts rather than on a key you saved. Those credentials are sealed with the same envelope encryption as your keys, under a distinct encryption context, so a house key and a member key can never be substituted for one another even by someone holding both ciphertexts. They are decrypted in server memory for the length of one request and never reach a browser.
Budgets are reserved atomically in the database before any request starts, and the maximum length of the AI’s reply is derived from your remaining budget — a cap isn’t advice, it’s the physical ceiling of what a request can cost. Every completed reply is committed to an append-only ledger at your provider’s own reported usage.
We recommend keys scoped to a provider workspace with its own spend limit — an Anthropic Workspace limit, or an OpenAI project budget. That limit is enforced by the provider that issued the key, outside our systems entirely — so even a total compromise of splitscreen is bounded by a number you chose.
Every table is behind row-level security: members see their own rooms and nothing else, and realtime channels verify membership at the database before admitting a listener. Budget mutations run only through database functions the client cannot call.
Message sizes, key-validation attempts, and AI turns per day are all rate-limited, and every key use is recorded in an append-only audit log.
Found something? contact@splitscreen.chat — we read security mail first and will credit you if you want.