Encryption
Encryption guidance matters most when your team needs to explain how live meeting content and follow-up artifacts are protected throughout their lifecycle. In Hyper, this is not only about the call stream but also about the derived artifacts that come from the meeting.
Use this page when evaluating how encryption fits with search, summaries, translations, and other post-meeting capabilities.
Wireframes
Section titled “Wireframes”┌──────────────────────────────────────────────────────────────────────┐
│ Hyper app.hyper.video/security/permissions │
├──────────────────────────────────────────────────────────────────────┤
│ │
│ Artifact permissions │
│ │
│ Applies to: recap, transcript, recording, shared files │
│ │
│ ┌──────────────────────────────────────────────────────────────┐ │
│ │ Audience Members of Product and selected guests │ │
│ │ External share Disabled by default │ │
│ │ Link access Sign-in required │ │
│ │ Retention 180 days for recordings │ │
│ └──────────────────────────────────────────────────────────────┘ │
│ │
│ Exceptions │
│ - Hosts can grant per-meeting access │
│ - Admins can enforce stricter workspace defaults │
│ │
└──────────────────────────────────────────────────────────────────────┘
Encryption is strongest when paired with explicit visibility, export, and retention policy.
When to use this
- Security reviews, customer questionnaires, regulated deployment planning, and internal rollout signoff.
- Any workflow where the meeting content remains sensitive after the meeting ends.
Before you start
- Confirm which environments, clients, and integrations are in scope for your review.
- Review artifact sharing and retention alongside encryption so the overall data flow is accurate.
Settings and options
Operational interpretation
- Treat encryption posture and artifact visibility as related but separate controls.
- Validate how downstream exports or integrations change the security boundary for your workflow.
- Use participant verification or workspace identity controls when the concern is trust in who joined the meeting.
What this feature helps with
Zero-knowledge architecture
Hyper servers never see your decrypted data. Encryption keys are generated and stored only on participant devices.
Always on
E2EE is not a setting you enable — it's the default for every call, every time. No configuration, no exceptions.
Verified participants
Verify that the person on the other end is who they claim to be with cryptographic identity verification.
How to work with it
Start or join a meeting
- E2EE is active from the moment the call begins
- No setup or configuration required
Keys are exchanged
- Encryption keys are generated on each participant's device
- Keys are exchanged directly between participants, never through Hyper servers
Everything is encrypted
- Audio, video, screen sharing, and chat are all encrypted
- Data is decrypted only on participant devices
Verify if needed
- Use security codes to verify participant identity
- Confirm no man-in-the-middle interference
Where it fits well
Sensitive discussions
- Board meetings with confidential information
- Legal consultations requiring privilege
- HR discussions with private employee data
- Strategic planning with competitive intelligence
Regulated industries
- Healthcare calls with patient information (HIPAA)
- Financial services discussions (SOX, PCI)
- Government and defense communications
- Legal firms with client confidentiality
Global teams
- Cross-border communications with data sovereignty
- Protection from regional surveillance
- Consistent security regardless of location
- Compliance with international privacy laws
What to expect
- E2EE by default
- Zero-knowledge architecture
- Cryptographic identity verification
- No server-side decryption
- Open protocol
- Covers audio, video, chat, and files
Questions that come up often
Can Hyper access my meeting data?
No. With end-to-end encryption, only the participants in a meeting hold the decryption keys. Hyper servers relay encrypted data but cannot decrypt it.
Does E2EE affect call quality?
No. Our encryption is optimized for real-time communication. You won't notice any difference in call quality or latency.
How can I verify encryption is active?
Every meeting shows an encryption indicator. You can also verify participant identity using security codes displayed in the call.
Related tasks
Limitations and rollout notes
- Some downstream systems may impose different security guarantees than the core Hyper workflow.
- Policy interpretation should include storage, export, deletion, and integration scope, not only transport.
Troubleshooting
A reviewer asks whether AI and search change the security model
- Explain the relationship between encryption, on-device or protected processing, and artifact permissions.
- Document which outputs stay inside Hyper and which can be sent downstream.
- Review the specific workflow instead of answering only at the transport layer.