A CLEARER LOOK AT YOUR DATA

Your device.
Your stored workspace.

Here is how the current Schizo Terminal web application handles your account, device workspace and exchange connections.

What is stored on your device

Exchange credentials, layouts, chart drawings, templates and preferences are saved in an encrypted device vault. The browser stores the vault and a nonextractable AES-256-GCM device key in IndexedDB. These vault contents are not uploaded to the shared community database.

This protects the stored workspace, but it does not protect it from someone who controls your browser profile, a malicious extension or code running inside the terminal. Clearing browser data deletes the vault and its device key. An encrypted backup is the way to move or restore a workspace.

What passes through the exchange relay

Exchange requests are signed on your device. Signed requests, API-key identifiers and exchange responses pass through this application’s exchange relay in memory. They are not saved as a server-side exchange-key vault. This is device-only credential storage, not a zero-knowledge relay.

The relay uses allowlisted exchange destinations. Supported requests have broker attribution removed before signing; requests that cannot be made without it are blocked.

Your identity and browser session

Auth0 handles signup, login and email verification. The terminal uses the verified identity to select the correct device workspace. An encrypted, HttpOnly web-session cookie contains basic identity and session timestamps, not exchange credentials or Auth0 access tokens.

The web session remembers this browser for 60 days from sign-in. Signing out clears the browser session and closes its live exchange connections. Encrypted workspace data remains on the device so it can open again after sign-in.

Community messages

Community nicknames and messages are stored in a separate Neon PostgreSQL database so other signed-in members can see the conversation and its saved history. Community authors use opaque identifiers; private email addresses are not displayed as chat names.

Messages are shared with signed-in community members. Exchange credentials, device vaults, email addresses and Auth0 tokens are not stored in that community database.

News and other services

The terminal uses Tree News’s public HTTPS history and WebSocket feed. History is cached temporarily on the terminal server. An optional Tree key is stored with your device workspace and sent only to Tree’s WebSocket. News and exchange services receive the connection information needed to respond to requests.

The application is hosted on Render. Hosting, identity, exchange and news providers process network connections under their own policies. The public marketing pages add no advertising trackers or third-party analytics scripts; their fonts and product images are served from this site.

Backups and signing out

Use Encrypted Backup to export a password-protected file and Restore Backup to import one. Keep the backup and its password private. Signing in on a different browser does not automatically sync the original device’s workspace.

These notes describe the current development preview. Last updated 17 October 2026.