How it works
How a check-in becomes a record you can trust
Three checks work together. The ID check ties a member to their legal name. Face ID ties each check-in to the phone's owner. The phone's location and our server's clock tie it to the meeting.
- 01Government ID matched to a live selfieOnce, before anyone shares with you.
- 02Face ID or fingerprint at check-in and check-outThe phone's owner, every time.
- 03Within 200 meters of the meeting's addressOur server works out the distance.
- 04Our server keeps the time, not the phoneFrom 15 minutes before to 30 after the start.
- 05Anyone can verify a recordSigned, unchangeable, with a public check page.
The ID check
Before a member shares with anyone, MeetingSlip checks their government ID, once.
A photo of the ID
A driver's license, state ID card, or passport.
A live selfie
Taken on the spot and matched to the photo on the ID.
Shown on the caseload
"ID verified as" the name on the ID, with the date. Every record made after the check says so too.
The check runs in our ID verification partner's own page. MeetingSlip never receives the photos, the ID number or the full date of birth. A check counts for two years, and members never pay for it.
✓ ID verified
Jordan Ellis
ID verified as Jordan Ellis on Oct 1, 2026
A government ID matched to a live selfie. A new check is due after two years.
Checking in
Open MeetingSlip at the meeting
Check-in opens 15 minutes before an in-person meeting starts and closes 30 minutes after.
Tap Check in
The phone must be within about 200 meters of the meeting. Our server checks the time and the distance, not the phone.
Confirm with Face ID
Face ID, Touch ID, or a fingerprint at every check-in and check-out. The phone's secure hardware signs it, and Apple or Google confirms the key belongs to the real MeetingSlip app. MeetingSlip never sees a face or fingerprint.
Check out when leaving
Checking out adds how long they stayed. At least 75% of the meeting counts as full attendance.
Get a signed record
Our server signs the record, and no one can edit it, including us. It has its own code and QR code, and anyone with the code can check it hasn't changed.
MeetingSlip · Verified recordSample
Meeting attendance record
Verification code PRS-7K3Q-M9XD
✓ Verified: signature valid, record unchanged
- Member
- Jordan Ellis ID verified as Jordan Ellis on Oct 1, 2026
- Meeting
- Quiet Time Meditation (AA) 12 C St E, Salt Lake City, UT
- Scheduled
- Tue, Oct 13, 2026, 7:00 to 8:00 PM
- Checked in
- 6:50 PM 34 m from the meeting · Face ID confirmed
- Checked out
- 7:52 PM 31 m from the meeting · Face ID confirmed
- Full attendance
- Yes, present for at least 75% of the meeting
What a record shows, and what it doesn't
Every verify page lists the same limits, so anyone who reads a record knows them too.
A record shows
- Our server recorded the check-in and check-out times with its own clock, not the phone's.
- The phone was within 200 meters of the meeting's listed address at each step, after allowing for GPS accuracy.
- Check-in happened between 15 minutes before and 30 minutes after the scheduled start.
- How long they stayed. At least 75% of the scheduled meeting counts as full attendance.
- The phone's enrolled owner unlocked it with Face ID or a fingerprint at check-in and check-out.
- Whose government ID was verified, and when.
- That no one has changed the record since. Each record is signed and can only be added to.
It does not show
- Whose face or fingerprint was added to the phone before the person set up MeetingSlip. The ID check ties them to their ID, but it can't see what else is enrolled on the phone.
- That they took part in the meeting or stayed in the room. MeetingSlip verifies presence near the location, not participation.
- That the phone's GPS wasn't faked in a way the phone didn't report. Reported fake locations are refused.
- That the meeting took place as listed. Meeting details come from the SobaSearch directory.
How to check a record
Scan the QR code on the record or report with any phone camera, or type its code below or at meetingslip.com/verify.
Look for the green banner: "Verified: issued by SobaSearch and unaltered." A red banner means the record failed a check. Don't rely on it.
Compare the details with the paper or screen in front of you: name, meeting, date, and times.
The verify page needs no account, loads no analytics, and isn't listed in search engines.
Verify a record
Questions
- Could someone check in from the parking lot?
- Check-in works within about 200 meters of the meeting's address, so a record shows the phone was near the meeting, not inside the room. It also shows when they arrived and left, and how long they stayed.
- Could someone use another person's phone?
- Every check-in and check-out needs Face ID, Touch ID, or a fingerprint from the phone's enrolled owner, and the member's government ID is matched to a live selfie before they share. MeetingSlip can't see whose face or fingerprint was added to the phone before they set it up.
- What about phones without Face ID?
- MeetingSlip needs Face ID, Touch ID, or a strong fingerprint sensor set up on the phone, so phones without one can't use it. For anyone whose phone doesn't, keep your current method for that person.
- Which meetings count?
- In-person and hybrid meetings with a street address in the SobaSearch directory, such as AA, NA, Al-Anon, and SMART Recovery. Online-only meetings can't be verified by location.
- What if a meeting is listed wrong?
- Listings come from meeting groups and public sources, and sometimes they are out of date. Email hello@sobasearch.com and we will look into it.
- How is a record signed?
- Every check-in, check-out and report is signed with an Ed25519 key that only our server holds, and each entry includes a SHA-256 fingerprint of the one before it. Our public keys let anyone check a signature without trusting us.
Try it with your team
Book a 45-minute call with Dave Liloia. We'll show you the caseload, answer your questions, and set up a pilot that fits your program.