H33 / Session / Metadata Exposure Analyzer
Your calendar invite leaks more than you think.
Paste any Zoom, Teams, or Google Meet invite below. We’ll count the metadata fields it exposes about your meeting — subject, attendees, organizer, recurrence, vendor extensions, and more — and show you what an H33 Session reveals instead.
Paste the raw .ics contents, or drop a .ics file.
No data leaves your browser. The parser runs locally; we don’t POST your invite anywhere.
Your invite
H33 Session
The meeting still happens. The metadata doesn’t.
An H33 Session emits a verifiable receipt — proof that the meeting was scheduled, who was authorized to join, and that it occurred — without revealing the subject, the attendee list, the recurrence cadence, or the organizer’s domain. The handle is independently verifiable, offline, even if H33 disappears.
Three receipts per session: Scheduling · Attendance · Completion. Each is a .h33pqv.json artifact you can drag into the public verifier.
Why metadata matters
An organizer email + attendee list + recurrence rule reveals deal flow, M&A activity, litigation cadence, executive routines, and outside counsel relationships — before a single word of the meeting is spoken.
Why a handle is enough
The 74-byte handle encodes authority binding, instruction tag hash, recipient root, and a timestamp anchor. Authorized holders resolve the rest. Everyone else sees a handle and a time window.
Why offline-verifiable
The handle is self-verifiable with the H33 verifier WASM. No API call to H33. No vendor dependency. Receipts survive even if H33, your auditor, or your scheduling tool is gone.