Account

Storage backends

Every attached file (tickets, confirmations, scans) is stored in a chosen backend. There are two, and the difference is whose cloud the bytes live in.

The two backends

Constellations storage. Files live in storage run by Constellations. No setup, ready on first upload, with an account quota (100 MB by default). Settings → Cloud storage shows usage.

Google Drive. Files are uploaded to your Google account, count against your Drive quota, and remain yours even after leaving Constellations. Only references are stored on the Constellations side.

The Google connection uses the narrowest Drive permission there is (drive.file): only files you explicitly pick, or that were created for you, are visible to Constellations. The rest of your Drive can't be browsed, searched, or read.

Choosing a default

Connect one or both backends under Settings → Cloud storage, then mark one as the default. That's where new uploads and auto-saved email attachments go. The default can change at any time.

Switching doesn't move existing files: anything already uploaded stays where it is and keeps working. There's no migration between backends.

Auto-save from forwarded emails

The "Auto-save email attachments" toggle on the same page controls whether attachments from recognised forwarded confirmations are saved to the default backend automatically. With it off, or with no default set, forwarded attachments aren't stored.

Which to pick

  • Zero setup, light usage: Constellations storage.
  • Files in your own cloud, with your own quota and retention: Google Drive.

The privacy trade is symmetrical: Constellations storage means trusting Constellations with the bytes; Drive means granting narrow access into a Google account. Either way, who can see a file inside the app is governed by where it's attached. See Storing documents and passes.