Cerium collects no telemetry or usage analytics. Your threads stay in a local SQLite database on your machine, and each coding harness talks directly to its own provider as usual. Anonymous crash reporting is enabled by default and can be turned off in Settings.
Below is everything Cerium stores or connects to outside your machine.
Optional account & sync
Signing in is completely optional. It exists so you can view and steer your desktop threads from your phone or another machine. Authentication is handled by Clerk (email and password, or Google, GitHub, or X), which receives your name, email address, and profile picture. Cerium never sees your password.
When you sign in, Cerium's relay at cerium.nonlooped.xyz stores the following for your account:
- Your name, email address, and profile picture from your sign-in provider
- Connected device metadata: device name, platform, Cerium version, update channel, last-seen timestamp, and a hash of the device key
- Synced thread copies from signed-in machines: messages, tool calls, and tool output (images excluded)
- Unsent message drafts and per-thread read positions
- Browser push subscriptions, if you enable notifications
When you control a machine remotely, the relay also proxies live traffic between devices. The relay runs on Cloudflare, which retains standard request logs. Your data is never sold or shared for advertising.
Deleting your data
Signing out a machine (or removing it in Settings → Account) deletes all of its synced thread copies from the relay. Deleting a thread deletes its synced copy immediately. To delete your entire account, open an issue on GitHub from the account you signed in with, or ask there for a private contact method.
Network requests
- Crash reports
- When the desktop app hits an unexpected failure (a UI render error, a backend crash, an unexpected harness exit, or a failed update), it sends an anonymized crash report to Sentry. Reports include the error type, a scrubbed error message (with all file paths, URLs, email addresses, IP addresses, and IDs stripped), the stack trace inside Cerium's code, Cerium's version and update channel, and your OS and CPU architecture. Reports never include your messages, files, folder or project names, thread titles, account details, machine name, or memory contents, and Cerium's Sentry project does not store your IP address. Turn this off anytime in Settings → General → Send crash reports.
- Updates
- Cerium checks GitHub Releases at launch and every six hours for new versions, and downloads updates only when you choose to install them. Opening Settings → Harnesses checks npm and GitHub for the latest version of each installed CLI.
- Dictation
- On first use, Cerium downloads the local speech runtime (from GitHub Releases, with Unpkg as fallback) and your chosen Whisper model (from Hugging Face). Both are cached locally, and all transcription runs on your machine.
- Artifacts
- Interactive HTML artifacts generated by agents can load external scripts over HTTPS (for example, charting libraries from cdn.jsdelivr.net), so viewing an artifact may fetch from those CDNs.
This website
This website runs no analytics, trackers, or ads. Signing in sets Clerk session cookies to keep you authenticated. Cloudflare serves the site and retains standard request logs. The theme you choose on the home page is saved locally in your browser only.