Glyphi TeamsTeams
Your data stays yours.That is the whole design.
Self-hosted deployments
The Teams edition is designed to run inside your company. The backend is a Supabase migration and one Edge Function deployed to your own project, in your own region. In that setup Glyphi Teams receives nothing: no account, no usage row, no message, no diagnostic ping.
What the backend stores
- An email address and a name per member, plus a password hash. Passwords are hashed with bcrypt; plaintext is never stored.
- One row per member per day: the date, a token count, an estimated cost and the split per tool.
- Chat messages as ciphertext and an initialisation vector. The key is derived in the app and never sent.
- A per-member daily token cap, set by the manager.
What is never stored
- Prompts, completions, transcripts or model answers.
- Source code, file paths, repository names or project names.
- API keys or credentials for the coding tools being measured.
- Message plaintext, on the server or in any backup it keeps.
Retention
A member can stop sharing at any time, which deletes the rows already shared. Removing a member deletes their usage rows and their messages. Deleting the team deletes both tables for that team. On a self-hosted deployment the retention policy is whatever your database keeps.
Hosted plans
If you would rather not run a database, Pro Max includes a hosted deployment on infrastructure operated for Glyphi Teams. In that case the same rules apply: daily totals, capped messages and account email only, never prompts or code.
Contact
Data questions, a DPA, a security questionnaire or a deletion request: email us.