Skip to content
ConceptForOperatorWith or without Foxden Admin

Where your data lives ​

This page tells you where Foxden keeps your data on your server, what leaves the server and to whom, and which key protects what, so you can answer your own security and privacy questions.

Foxden runs on a server you control. Everything a person writes stays on that server unless a feature you turn on sends it somewhere, and each of those features is listed below.

On your server ​

WhatWhere it is kept
Each app's recordsThe app's own Postgres 17 database, in its own container and Docker volume. No app reads another app's database.
Each app's settings and secretsA settings file (.env) in the app's install folder under /opt, readable by root only.
Facts shared by several apps/etc/foxden/suite.env (the domain, the email sender, the Google and Microsoft clients, the AI key typed at install), copied into each app that uses them.
The box key/etc/foxden/box.key, made once by foxden init. The secrets that link one app to another (Arctic to Fennec, each app's files to Library) are derived from it.
FilesLibrary's file store: a Docker volume, or an S3-compatible bucket when you set Library's four S3 keys. It holds Library's own files and those of Fennec, Corsac, Pampas, Culpeo and the assistant gateway once the server links them to Library. An app that is not linked keeps its files in its own volume.
Meeting recordingsArctic keeps a meeting's video in its notetaker's own volume when recording is turned on in Arctic's settings.
Call recordingsCape keeps them in its own data volume.
Meeting transcriptsArctic transcribes on your server with its own speech-to-text service; the model is part of the image, so no audio leaves the server for transcription.
BackupsEach night, each app writes a backup to the backups folder in its install folder and keeps 14 days of them. Library's backup also holds the files the other apps keep in Library.
Update snapshotsBefore each update, the app's updater takes a copy of its database and keeps the last two, to roll back a failed update.

The company's people, their access, the company's name and brand, sign-in records, AI usage and the record of what assistants did are in Foxden Admin's database. Each app also keeps its own users table and its own activity log; Admin keeps a copy of each app's log entries (who, what action, on which record and when, never the content). See Security and trust.

What is encrypted, and with which key ​

WhatEncrypted with
BackupsA passphrase file that foxden init makes in /etc/foxden/. A backup refuses to run without one. It is the only key to every backup, so keep a copy off the server. Two copies are the exception: Library's copy of its file store and Cape's copy of its recordings are kept as plain files, and leave the server only to an encrypted (rclone crypt) remote you set up yourself (LIBRARY_FILES_REMOTE, CAPE_RECORDINGS_REMOTE).
Admin's signing keys, AI provider keys, directory tokens, event subscription secretsAES-256-GCM, each under its own key derived from Admin's APP_SECRET.
An app's stored Google and Microsoft tokens, and similar secrets it keeps in its databaseAES-256-GCM under a key derived from the app's own secret in its .env (APP_SECRET in most apps).
Arctic's transcript textAES-256-GCM under a key derived from Arctic's own secret (CALENDAR_TOKEN_KEY, or AUTH_SECRET when that is not set).
Corsac's seal certificateIts private key is encrypted under Corsac's APP_SECRET.
Sessions, invitations, sign-in links and assistant keysNot stored at all: the app keeps a keyed hash and compares against it.
TrafficHTTPS from the browser to the proxy. Apps listen on the server's loopback address only.

Because of this table, three things must move with a server, or be restored with it: each app's .env (its secrets are in no backup), the backup passphrase files, and /etc/foxden/box.key. Restoring Admin with a different APP_SECRET leaves its signing keys, provider keys and directory tokens unreadable. See Back up and restore.

What leaves your server ​

Nothing below happens until you set it up, except the last two items.

Where it goesWhat is sentWhen
The AI providers you add in Admin (Anthropic, OpenAI, Google, Groq, xAI, DeepSeek, Moonshot, OpenRouter, Voyage AI)The text of each AI request, the audio of Fennec's and Cape's calls for transcription, and the text of Cape's spoken prompts. Every app's AI goes through Admin; no app holds a provider key.Only after an Owner adds a provider key. With none, AI is off in every app. See Turn on AI.
Your email service (Resend, or your own SMTP server in the apps that offer it)The emails the apps send: sign-in links, invitations, signing requests, notifications.Once email is set up. See Set up email.
Google and MicrosoftSign-in at Admin, and, for each person who connects an account, reads of their calendar, mail or directory profile. Only a person who turns on booking links gives an app the right to write calendar events.Once you add a Google or Microsoft client and people connect.
Meeting platformsArctic's notetaker joins the meetings it is asked to record.When a person sends it to a meeting.
Timestamp authorities (DigiCert, then Sectigo)A hash of each sealed document, never the document, to get a trusted timestamp.Each time Corsac seals a document, unless TSA_ENABLED=false.
Addresses you configureEvents (ids only, never content), Corsac and Pampas webhooks, Slack messages, off-site backup copies.Once you set a destination.
The container registryRequests for new builds, and a check whether a newer build exists: when an update page asks, and once an hour when automatic updates are on.Always, unless you set UPDATER_CHECK=0 for an app.
Let's EncryptRequests for certificates for your addresses.When you use public certificates (the default).

If you choose the free hosted address when you install, foxden also sends your server's IP address to Codefox's address service to create the DNS records, and the server renews the address every six hours.

Foxden is open source under Apache-2.0.