Security and privacy
The security we ship, described precisely.
Encrypted transport for every call, optional end-to-end encryption for meetings and conversations, enterprise identity, an audit log and the option to run everything on your own servers. Here is exactly what each one does, and what it doesn’t.
Encryption
Encrypted in transit, end to end when you need it.
- In transit, always
- Audio, video and screen sharing use DTLS-SRTP between devices and the media server. App traffic uses TLS.
- End-to-end encrypted meetings
- Tick “End-to-end encrypted” when starting a meeting, or let an administrator require it for every meeting. The key is created on the host’s device and travels in the part of the link after #, which browsers never send to a server. Media is encrypted frame by frame on each device (AES-GCM), so the media server forwards frames it cannot read. Phones and browsers join the same encrypted call.
- End-to-end encrypted conversations
- Direct messages, group conversations and private channels can be end-to-end encrypted. Each device has its own key pair; messages, edits, files and voice messages are encrypted on the device (AES-256-GCM), and the server stores only ciphertext. Keys rotate when a member leaves, safety codes let people verify each other’s devices, and a passphrase-protected key backup restores history on a new device.
- What changes when content is encrypted
- The server cannot see it, so recording, transcription, live captions, AI, search, mentions and link previews are switched off for that meeting or conversation, and encrypted files can’t be scanned for malware.
- What is not end-to-end encrypted
- Meeting chat, polls and the whiteboard pass through the server as in any meeting, and the app says so. Metadata such as who joined and when is kept by the server.
Identity and access
Enterprise identity and access.
- Single sign-on with OpenID Connect (Okta, Microsoft Entra ID, Google Workspace, Keycloak, Auth0) or SAML 2.0
- Optionally require single sign-on for everyone on a verified domain, with owner break-glass access
- SCIM 2.0 provisioning: deactivation suspends the membership and ends sessions
- Verified domains through a DNS TXT record
- Multi-factor authentication and passkeys
- Roles, invitations and policies for guests, recording, transcription, file sharing and retention
- Meeting lobby, passcodes, locking and host moderation
- Session revocation, and session tokens never appear in URLs
Audit and data
A record you can check, and data you can take with you.
- Audit log
- Administrative changes, data exports, AI calls and approvals are written to an audit log with a tamper-evident trail.
- Audit evidence
- Administrators can download an evidence file (configuration, access review, security events and an integrity check of the audit trail) mapped to SOC 2 and ISO 27001 controls. ToriMe is not certified: a certificate needs an independent auditor and an audit period.
- Data export
- Administrators export the organization’s data; everyone can export their own personal data (GDPR Articles 15 and 20). Download links expire after five minutes and are logged.
- Deletion and retention
- People can delete their account from Settings or a public page, which revokes their sessions. Organizations set retention policies.
- File safety
- Optional malware scanning with ClamAV. A file that couldn’t be scanned stays unavailable until a scan succeeds.
- Outbound safety
- Webhooks and connected tools only reach public addresses, checked after DNS resolution, unless an on-premises operator allows private networks.
Deployment
Your servers, if you want them.
Self-host ToriMe with Docker Compose or Kubernetes, including in air-gapped networks, and keep messages, meetings, recordings, files and AI processing on infrastructure you control.
Questions
Security, answered.
Is ToriMe end-to-end encrypted?
Optionally. All calls use encrypted transport (DTLS-SRTP), and app traffic uses TLS. On top of that, meetings and conversations can be end-to-end encrypted so that only participants hold the keys, and administrators can require end-to-end encryption for every meeting. In an end-to-end encrypted meeting, recording, transcription and AI features are switched off, because the server cannot see the content.
Is ToriMe GDPR compliant?
ToriMe is built in Germany by NotaNovice UG (haftungsbeschränkt) and designed for GDPR requirements: personal data exports for access and portability requests (Articles 15 and 20), self-service account deletion, retention policies, an audit log, AI that is off by default, optional end-to-end encryption, and self-hosting so an organization can choose where its data lives. Compliance also depends on how a deployment is run: when you self-host, your organization is the controller. ToriMe does not claim a GDPR certification.
Is ToriMe certified (SOC 2 or ISO 27001)?
Not yet. ToriMe includes an audit evidence export with a tamper-evident audit trail, mapped to SOC 2 and ISO 27001 controls, to prepare for an audit. A certificate requires an independent auditor and an audit period, and ToriMe does not hold one today.
Does ToriMe support single sign-on and SCIM?
Yes. ToriMe supports single sign-on with OpenID Connect (for example Okta, Microsoft Entra ID, Google Workspace, Keycloak or Auth0) and SAML 2.0, SCIM 2.0 user provisioning, verified domains and organization data exports.
Collaboration you can explain to your security team.
Create a workspace for free, or plan a self-hosted deployment.