Trust
What ComplianceVia MeetingProof does with meeting data.
This page states what is in development and what is planned. Nothing here is available yet. We will update the page as each item ships.
Consent
Consent captured on screen, tied to the meeting.
In development- Consent forms are versioned for each organization. A published version is locked. Changes create a new version.
- The exact text of each version is fingerprinted with a SHA-256 hash. The hash changes if a single character changes.
- A guest signs with a drawn signature, a typed name and a checkbox of intent. A guest is the person who books the meeting.
- Each signature is stored with the form version, the guest's identity and how the identity was confirmed, the meeting, the time, the IP address and the browser.
- Withdrawal is a signed record of its own. Future recording for that guest stops.
- Declined consent follows your policy: block the booking, or meet with recording off.
Privacy settings
Settings cascade. Locks hold.
In developmentSettings flow from organization to location to host to meeting. A locked setting can be replaced only by a stricter one. The more private choice always wins.
| Setting | Choices, most private first | Default |
|---|---|---|
| Recording | Off · On with consent | Off |
| Consent policy | Required to book · Meet without recording | Meet without recording |
| Guest identity | Allowed email domains · Business email · Any email, each with a one-time code | Business email |
| Follow-up poll | Off · On | On |
| Retention | Days, per record type | Set by your policy |
Guest email
Every guest's email confirmed at booking.
In development- Guests confirm their email with a one-time code at booking.
- Organizations can limit booking to allowed email domains or to business email.
- Every join link opens the check-in page first. The check-in page records the check-in. Then the guest's personal Zoom link opens.
- When your settings require it, the check-in page asks for a fresh code.
Audit log
A record that shows when anything changes.
In developmentThe audit log is append-only. Entries are added and never edited. Each entry is hashed together with the previous entry. A later edit or deletion breaks the chain. The break shows on review. Evidence records and consent records are hashed into the same chain. An evidence record is the finished record of one meeting: who joined, when, for how long and how each person was identified.
Tamper-evident means a change shows. Tamper-evident does not mean a change is impossible.
Evidence record
Illustrative- Record hash
- 3f9a…c21e
- Audit entries
- 14, chain intact
Data handling
Careful defaults, built in from the first release.
In development- Each organization's data is separated at the database level.
- Connection secrets for Zoom, Microsoft 365 and booking tools are encrypted with a key unique to each organization.
- Emails carry links only. No meeting topic, notes or summary appears in an email.
- Application logs use identifiers or masked values, never guest names or email addresses.
- Connections request the narrowest access each task needs.
- Guests can request an export of their own records.
- Support access to an organization is time-limited, requires a reason and lands in the audit log.
- Photos, when that option ships, are for a human visual check only. MeetingProof runs no face detection or face matching.
Where we stand today
| Item | Where MeetingProof stands |
|---|---|
| SOC 2 | Not yet. SOC 2 is an independent audit of security controls. Type I (controls at one point in time) is planned first. Type II (controls over a period) follows. |
| HIPAA | MeetingProof does not claim HIPAA compliance. HIPAA readiness is planned. Readiness includes agreements with each vendor that handles meeting data. |
| Accessibility | This website targets WCAG 2.1 AA. A VPAT (an accessibility conformance report) for the product is planned. |
| Higher-education reviews | HECVAT (the higher-education security questionnaire) is planned. |
| Data processing agreement, subprocessor list and hosting region | Shared with each organization before onboarding. |
| AI model training | Meeting data is not used to train AI models. |
Roadmap
Planned next.
Planned- Custom booking and email domains for each organization
- Transcripts and AI summaries, only with every attendee's consent
- SSO (single sign-on through SAML) for staff and guests
- Optional pre-join photo for a human visual check
- SMS reminders, with consent collected at booking and opt-outs honored
MeetingProof provides evidence that supports an organization's meeting and compliance records. MeetingProof does not certify compliance, guarantee admissibility or replace legal advice.
Bring your security questionnaire.
We will answer what is true today and mark what is planned.