The four things that make it different
Clients join from a browser. No app, no account. Your client clicksgetrivet.ca/your-name, fills in their first name and
phone, and is in the waiting room. Chrome, Safari, Firefox, Edge — on a
phone, a tablet, a laptop. Nothing to install. See
Clients don’t install anything.
Your face stays on screen when you share.
When you share your screen (a worksheet, a safety plan, an EMDR target image),
the client still sees you in a corner tile. Most meeting tools replace your
camera with the shared content for the duration of the share. In a clinical
session that reads as withdrawal — a real cost in EMDR specifically.
See Sharing your screen.
EMDR and whiteboard live inside the call.
You don’t pivot to a second tool when a client needs bilateral stimulation
or a quick CBT diagram. Tap EMDR in the toolbar — the workspace opens.
Tap Share Screen → Whiteboard — the canvas mounts. The client sees a single
session, not a tool stack.
Sessions are never recorded.
There is no recording feature. There is no AI scribe listening in. The audio
and video are end-to-end encrypted using WebRTC’s DTLS-SRTP, peer-to-peer
when network conditions allow. Practitioner notes are separate and live in
the Notes section of the app — never derived from session audio.
How a session flows
You share your link once
Drop
getrivet.ca/your-slug into your intake email, your booking
confirmation, your email signature. It never changes.At session time, the client opens the link
They land on a public waiting-room page. First name, phone number, tap
Join. No download.
You see them waiting in the inbox
A “{Name} is waiting” pill lights up across the app. The thread shows a
green Start session button.
You tap Start. Both browsers connect
A pre-join screen lets each of you check camera and mic. Tap Join
Session. The WebRTC connection establishes.
The session runs in the workspace
Mic, cam, screen share, EMDR, whiteboard, end call. All in one toolbar.
What’s not in scope today
A few things are deliberately omitted — calling these out so you know what you’re working with:- Multi-party calls. Rivet video is 1:1 — one practitioner, one client. Couples and family work on a shared device works; a third browser joining is rejected with “session full.” Group video isn’t planned.
- Recording. No recording, no transcript-from-audio, no AI scribe. By design.
- Background blur. Not available — the current generation of in-browser blur looks acceptable for a casual chat and noticeably wrong for a clinical session.
- Native iOS/Android video. The video session today runs in the browser on every platform. Native softphone calling is in the Rivet app; video sessions stay in the browser for now.
Rivet video is end-to-end encrypted with WebRTC DTLS-SRTP. When your
network needs a relay server (about 5–10% of sessions, mostly behind
corporate or hospital firewalls), the relay forwards encrypted packets
only — it can’t decrypt the call.
Related articles
Your session link
The persistent slug URL and how to claim yours.
The session workspace
A tour of every control in the in-call toolbar.
EMDR in Rivet
Bilateral stimulation inside the same video call.
