Closed beta
Trust & Transparency
TELVRIX syncs your mailboxes using your own IMAP/SMTP credentials. It doesn’t read, analyze, or sell your email content. Here’s exactly what it does — and what it doesn’t.
Credentials encrypted
IMAP and SMTP passwords are encrypted at rest using AES-256-GCM. Never stored in plaintext.
Your data, isolated
Message data lives in your deployment’s PostgreSQL database with row-level security. No shared data pools.
Your servers, your mail
TELVRIX connects to your mail provider with your credentials. Mail stays at your provider — it is read and indexed, not moved.
No cross-user access
Row-level security ensures each user’s data is only readable by that user.
No email analysis
Email content is never analyzed for advertising. No content scanning, no behavioral profiling.
Admin privacy
Operators can see mailbox health and sync status. Message bodies, subjects, and credentials are never shown in admin views.
What TELVRIX stores
When you connect a mailbox, TELVRIX syncs your emails into your deployment’s database so you can search, label, and manage them from any device. That database belongs to your deployment — it is not shared with other instances.
It stores:
- Message metadata (sender, subject, date, flags, folder)
- Message body text and HTML (for display and search)
- Attachments: names and content-types only — not the file content
- Your IMAP/SMTP credentials, encrypted at rest
- Labels, drafts, contacts, signatures you create
Decrypted credentials are never stored — they are decrypted in memory only when making a connection.
Third-party infrastructure
A TELVRIX deployment relies on the following services:
| Service | Purpose | Data involved |
|---|---|---|
| Supabase | Auth, database, storage | All synced mail data |
| Redis | Background jobs (optional) | Job and mailbox identifiers only |
| Hosting platform | Serving the application | HTTP request data, logs |
Beta limitations
TELVRIX is in closed beta. This means:
- No SLA or guaranteed uptime
- Data may be reset during significant schema migrations (advance notice given)
- Not suitable for legally regulated email (HIPAA, PCI, GDPR-critical workflows) yet
- SOC 2 and formal compliance certifications are planned, not current