Skip to content

Security and privacy

Starfarer runs in your home and keeps what's yours there. This page is the plain version; the full model, with what the code enforces, is The security model.

What stays on the Starbase

  • The AI's brain: every model runs in Ollama on the Starbase. No cloud AI is used.
  • Conversations, memory, journals, the crew, voiceprints, files and the Cargobay.
  • Saved passwords and keys (mail accounts, tool server tokens, Module secrets): scrambled and locked to the Starbase computer. On Windows the key is held by Windows itself (it opens with or without anyone signed in, and survives password changes); a copied data folder or backup can't open them. Turn on BitLocker (or your system's disk encryption) against a stolen drive.

What goes out is only what you ask for: a web search, a page to read, your mail server, the sites a video Module searches, and downloads of models and voice files from their own projects.

Who sees what

  • Adults' conversations are private, even from the Captain. Cadets' and Guests' can be read by the Captain under oversight, and each read is logged.
  • Mail, calendar, house messages, lists, tasks, files and the Cargobay are each person's own, the Captain included.
  • The personas are separate people: one AI never sees your conversations with another.
  • Shared speakers say only who and what kind ("Kim, your timer's done"), never the content.
  • Private conversations sit behind your PIN.

What protects the controls

  • Permissions are checked by Starbase on every request, never left to the AI: an AI can't be talked into giving someone more than their rank allows.
  • The PIN approves anything that changes something important. The Never list stops the worst things for everyone.
  • Sign-in limits: password guessing is throttled; two-step sign-in is required from outside the home.
  • HTTPS on the home network, with Starbase's own certificate.
  • Only the Captain promotes, demotes, installs Modules, and reads under oversight. Modules install only from publishers the Captain trusts, and only exactly what they signed.
  • The audit log records who did what, for 400 days.
  • Content the AI reads (a web page, an email, a document) is never taken as instructions.

Things to do

  1. Keep Ollama on the Starbase only (its default).
  2. Turn on two-step sign-in before outside access.
  3. Back up to another drive.
  4. Only trust Module publishers you'd let run code on your machine.
  5. Never open Starbase's own port on your router: use a tunnel or proxy (Domain).

Found a security problem? See Reporting a vulnerability.