Beta draft — final versions publish with the Glass Overlay LLC launch

Recording Consent

DRAFT — NOT LEGAL ADVICE. Review with counsel. This is both the

guest-facing consent copy AND the product spec for where the gate lives.

Why it matters: many US states (CA, FL, PA, WA, IL, MD, etc.) and many

countries require all-party consent to record a conversation. Shipping

a recorder without a consent step is a real legal exposure (ship-audit P0).

The model (two layers)

1. Host warranty (in Terms of Service). When a host starts a recording they affirm they have obtained, or will obtain, the consent of all participants and have the right to record. The host is the controller; we are the processor.

2. Guest consent gate (in the join flow). Before a guest's audio/video is captured, they see a clear notice and must affirmatively proceed. This is the new build item.

Where the gate goes

• Web guest (browser): a consent step in the Green Room / join screen,

before the camera/mic publish and before any recording starts. Guest must tap "I understand and agree" to continue. (Currently the guest join path has no consent step — this is the gap to build.)

• iPad/iPhone companion: same gate in its join/Live-Call entry.
• Always-visible "REC" indicator: while recording, every participant sees

an unmistakable recording indicator (badge/dot), not just the host.

Guest-facing copy (short form, on the gate)

This session is being recorded.

The host is recording audio and video of this session for their podcast /

video production. By joining, you consent to being recorded and to your

recording being processed and stored by Glass Overlay on the host's behalf.

You can leave at any time. See our [Privacy Policy].

[ I understand and agree — join ] [ Leave ]

Host-facing copy (shown when starting a recording, first time / per session)

You're about to record everyone in this session.

Make sure every participant has agreed to be recorded. Where you are,

recording without everyone's consent may be illegal. You're responsible for

obtaining the consent you need. [Don't show again ▢] [ Start recording ]

Notes for implementation

• The web consent gate is the concrete new UI (guest join path). The host

warranty is text in the ToS + the host-facing reminder above.

• Keep the gate BEFORE capture (privacy-first — matches the app's "mute = stop

capturing" principle: don't capture anything before consent).

• Log/record that consent was shown + accepted (timestamp) for the host's

protection — but do not over-collect (a boolean + time is enough).

• Jurisdiction nuance (one-party vs all-party consent) is the host's

responsibility per the warranty; we provide the gate as a good-faith aid, not legal compliance on the host's behalf. Counsel should confirm this framing limits our liability appropriately.