For companies · beta

Security and data

What is protected, what data is processed, where the boundaries are and how to report a problem. This document describes the current product version; technical details are in the encryption overview and the protocol.

Status: beta · encryption v1 · no independent external audit has been performed · updated 05.11.2026.

What is protected

• Communication content. In protected mode, messages, calls, meetings and files are encrypted on participants' devices.
• Keys. Keys are created on devices; Meeter does not receive them and does not store communication content.
• Access. Admission starts with an invitation from the company. A room password may additionally be required for a protected meeting, but it does not replace the invitation. A corporate ID is configured at launch through OIDC or the company account.
• Infrastructure. The company node relays encrypted data. Meeter manages the license, updates and node status, not communication content.

What Meeter sees

Meeter does not join meetings. Communication content is not used to operate the service; recordings and transcripts are created only by the company's decision. Metadata is data too: the service and the node see the fact of a connection, its duration and the volume of transferred data. Encryption hides content, not the fact of the meeting.

Data processing

• Purpose. Service data is needed for node operation, licensing, updates, support and incident prevention.
• Location. Communication content and the company database stay on the company server; Meeter does not receive a copy.
• Retention. Retention periods for service data are fixed by policy and contract. Recordings and transcripts are created only when explicitly enabled by the company.
• Access. The company manages access. A local administrator can export a backup; Meeter does not receive that backup.
• Deletion. The company controls retention and deletion in its own environment.

Data processing terms, DPA and review requirements are agreed in the contract. On request we provide a description of the data model and access boundaries.

Current limitations

• Beta. Behaviour and settings may change. Regulated data and legally significant meetings require a separate assessment.
• Encryption v1. No independent external audit has been performed; the specification is still being fixed. Internal reviews do not replace an external audit.
• Protected mode. End-to-end media encryption depends on the room's protected mode. Without it, the connection is protected in transit but not end-to-end.
• Modified node. The standard node does not decrypt the stream. But the company controls the machine: a modified node may collect technical data or read unprotected rooms.
• Recordings and transcripts. Not created by default. If the company enables this feature, separate retention and access rules apply.
• Screenshots. A participant can take a screenshot or record the conversation on their device; encryption does not prevent this.

Vulnerability disclosure

Write to security@meeter.me. A short description without third-party data is enough for the first email; we will agree on a secure way to transfer material.

Include the affected component, browser or app, what you expected and what happened, minimal verification steps and a contact. Do not send private keys, room passwords, links with a key, access tokens or content from other meetings. If you accidentally gain access to third-party data, stop, do not copy it and tell us.

Please do not publish details before coordination: we want to verify and fix the issue first. There is no guaranteed response time, but we will confirm receipt and give an initial assessment.

Permitted testing is on your own account, your own room and a test build, with synthetic data. Load attacks, spam, brute force, access to other rooms and data, modification or deletion of data, attacks on infrastructure and nodes are not permitted.

Audit and compliance

Internal reviews and tests have been performed. No independent external audit has been performed. Status, limitations and open questions are recorded in this section and in the documentation; we do not claim compliance with requirements that have not been verified.

Contact

• Access and pilot: hello@meeter.me
• Vulnerabilities and security: security@meeter.me
• Access request: meeter.me/access

← Documentation · Meeter Business overview · End-to-end encryption

Updated: 5 November 2026. Reviewed against the current model: company access, guest invitations, Android, iOS in development.