Security
These are the controls built into Megvite visits today. This page describes how the product works; it is not a certification.
- Signed sign-in sessions
- Your sign-in is an HttpOnly cookie signed by the server with HMAC-SHA-256 and checked on every request. Signing out invalidates the sessions issued before it.
- Hashed visit and summary links
- Visit invitations and patient summary links are stored only as SHA-256 hashes, never as the link itself. Invitations expire, can be replaced by the clinic, and are claimed by one device.
- Encrypted audio and video
- Audio and video travel directly between the people in the visit over WebRTC, which encrypts media with DTLS-SRTP. The Megvite signaling service sets up the connection and does not receive the audio or video.
- Role-based clinical records
- Notes, review and sign-off are limited by clinic role. Writing a visit note requires a provider or owner. A patient sees only their own visit, through their own link.
- Recording requires consent
- A visit recording cannot start or be archived unless consent is on file for that visit. Everyone in the room sees when a recording is running. The clinician’s browser uploads the recording to storage, and each saved part is checked against its checksum.
- Audited Megvite actions
- Every action Megvite take is logged with the Megvite, the skill and the outcome. Clinical text, contact details and credentials are redacted from those logs.
- Rate-limited public booking
- Public booking requests are rate limited, so a clinic booking page cannot be flooded with requests.
- Hosted on Cloudflare
- Megvite runs on Cloudflare Workers, with visit data in Cloudflare D1 and files in Cloudflare R2.
Read the Business Associate Agreement. For product guidance, ask Megvite.