We’re not yet end-to-end encrypted — and here’s our roadmap
Honest about chat security. The expanded version of the callout that lives on our about page.
What we have today
Splivo includes a per-group chat for coordination (“who’s grabbing tonight?”). Messages travel encrypted in transit (TLS) between your device and our backend, and again from our backend to other group members. Messages are stored encrypted at rest in our managed Postgres database (Supabase).
What we do NOT yet have: True end-to-end encryption (E2EE) where the server cannot read messages even if compelled. Splivo group chat is encrypted in transit and at rest, but the server can technically decrypt.
We’re explicit about this because we’ve seen apps misuse “stored on device” to imply E2EE when sync is involved. We don’t.
What this means for you
Sharing dinner plans? Sure. Discussing a legal matter, a wallet seed phrase, or anything sensitive? Use Signal or another E2EE app for that. Splivo chat is for coordinating splits, not for confidential conversation.
We don’t read group chats. We have no automated content moderation, no analytics on chat content, no advertising signals derived from chat. The full data-handling commitments live in the Privacy Policy §3 (third-party data flow).
Why this matters — the risk register
This honesty is tracked formally as risk R-006 in our internal risk register: “Chat security claim mismatch with implementation.” Severity LOW — because we don’t make a false claim. If marketing copy ever claimed E2EE while the server can decrypt, the risk would escalate to consumer-protection / false-advertising territory. We have a copy-review process that bans the phrase.
The roadmap
- v1.0 launch: sustained encrypted-in-transit + at-rest. No E2EE for group chat. Direct 1:1 chat (when it ships) will use E2EE first.
- Post-v1.0 evaluation: Group chat E2EE depends on key management for groups, which is harder than 1:1. We’ll evaluate when group-chat usage justifies the engineering cost.
- Always: If our chat security posture changes, the change goes in the changelog with the verifiable date and the corresponding Privacy Policy update.
Want to read more about how we think? Browse the changelog for verifiable narrative.