Security and privacy
What we keep, where, and for how long
A summary for compliance and IT teams at programs, courts and agencies. Members choose what to share, and every view is logged.
We sign a Business Associate Agreement
If your program is covered by HIPAA, we will sign a BAA with you. If your program is also covered by 42 CFR Part 2, tell us on the call so we can go through your consent requirements together.
The data
What MeetingSlip keeps
- Account name and email for members and staff.
- For each check-in and check-out: one location reading, the meeting, the times and the distance.
- After an ID check: the name as printed on the ID, birth year, type of ID, issuing country, expiry date, and the result.
- Who on your team opened which record, and when (an access log that cannot be edited).
What it never keeps
- ID photos, selfies, face data, ID numbers, addresses or full dates of birth.
- Face ID or fingerprint data. The phone checks it; we only learn whether it passed.
- Location in the background, or anything about other people at the meeting.
- Data for ads. No ad or analytics tools in the app, and we never sell data.
The details your team will ask about
- Who sees a member's records
- Only the people the member shares with, after they tap Allow in the app. They can stop sharing at any time, and they can see who opened their records.
- The ID check
- Our ID verification partner compares a photo of a government ID with a live selfie, in its own page. We receive only the result and the details above. When a member deletes their account, we ask the partner to delete its copy, and keep asking until it confirms.
- Retention
- Records, reports and ID details are kept while the member's account exists, and erased when they delete it. Database backups roll off on our provider's schedule, and we never restore a deleted account from them.
- Where data is stored
- In the United States: the database runs in Supabase's US West (Oregon) region. The website and server run on Cloudflare's network.
- Encryption and access
- All traffic is encrypted (HTTPS). Passwords and session keys are stored only as hashes. The public can't reach the database directly.
- Tamper-evident records
- Every check-in, check-out and report is signed with an Ed25519 key only our server holds, and chained with SHA-256. The database refuses edits and deletions of attendance entries. Anyone can check a signature with our public keys.
- Reports in your records
- Staff can download a signed PDF report for any date range. Once you file it, your own policies govern that copy.
- Breaches
- If we learn of a breach that affects your data, we'll tell you as the law and our agreement with you require.
Companies that help us
They may handle data only to provide their service to us. The privacy policy has the full list.
- Cloudflare
- Hosts meetingslip.com and the app’s server, and protects them from attacks.
- Supabase
- Hosts the database, in its US West (Oregon) region.
- ID verification and payment provider
- Runs the ID check in its own page and handles monitor payments.
- Resend
- Sends password resets and the alert emails a monitor chooses.
- Sentry
- Reports errors. Verification codes are removed first.
Questions from your compliance team?
Book a 45-minute call. We'll go through the BAA, the ID check and how records are kept, and set up a pilot when you're ready.