Active today
Core safeguards
- Firebase authentication for account identity.
- EU-region Cloudflare storage for configured user files.
- Server-side usage, budget and protected-state checks.
- Provider keys stay encrypted and server-side.
Security
Your data stays under your control.
Tavory separates account identity, protected server checks, provider access and visible costs. This overview distinguishes what is active from what depends on setup.
Data flow overviewNo secrets shown
Browser
Authenticated request
Tavory server
Rights, keys and budget checks
AI provider
Only the selected request path
Answer
Usage and result return
Provider keys are handled server-side. The browser never receives a provider secret.
Status by layer
What is active, setup-dependent or planned.
Setup required
Depends on account
- MFA and device-session controls when enabled in Firebase.
- Team administration and connected providers after setup.
- Plan access and model permissions for each account.
Planned / not claimed
Be precise
- Swiss hosting is planned, not current storage.
- SSO, SCIM and audit-log claims require verified availability.
- No certification is implied by this overview.
Authentication
Identity is checked before protected account actions.
Provider keys
Keys are never returned to browser code.
Budgets
Usage is connected to plan limits and visible costs.
File storage
Configured user files are stored in Cloudflare’s European region.