Privacy policy
MeetingSlip privacy policy
Effective October 15, 2026
MeetingSlip proves you were at a meeting. To do that it saves a GPS reading when you check in and check out. Nobody sees your records unless you share them. If you share them with a monitor, you first verify your ID with our ID verification partner. We don't sell your data and we don't use it for ads.
MeetingSlip is operated by The Coaching Platform LLC. "MeetingSlip," "we," and "us" mean The Coaching Platform LLC. MeetingSlip uses the SobaSearch meeting directory. "You" means the person using the MeetingSlip app. This policy covers the MeetingSlip app and this website, meetingslip.com (formerly verifiedpresent.com, which now redirects here), including its verify pages. The SobaSearch privacy policy covers sobasearch.com.
At a glance
This is the short version, in the same terms the App Store and Google Play use.
| Data | Collected? | Why | Who can see it |
|---|---|---|---|
| Precise location | Yes Only while the app is open. Saved only when you check in or out. | To confirm you are at the meeting | You, and anyone you give a code to |
| Name and email | Yes | Your account; your name appears on records | You. Shared records show your name and a masked email |
| Meetings you attended | Yes | This is the record itself | You, and anyone you give a code to |
| Device details | Yes Phone model, OS and app version, a scrambled device ID | Evidence and fraud prevention | Model and versions: you, and anyone you give a code to. Device ID: only us |
| Report details | If you add them Recipient and case number | Printed on the report | You, and anyone you give the report to |
| Face ID, fingerprints, or other biometric data from your phone | No MeetingSlip needs Face ID or a fingerprint for every check-in, but your phone checks your face or fingerprint itself. We get only a yes or no and a signature from your phone. | To show each check-in was confirmed on your enrolled phone | Whether a check-in was confirmed: you, anyone you give a code to, and anyone you share with in the app |
| ID verification | Only to share with a monitor Our ID verification partner takes a photo of your ID and a selfie and compares the faces. We keep your name as on the ID, your birth year, the type of ID, the country that issued it, its expiry date, and the result. Never the photos or the ID number. | So a monitor knows the account belongs to you | Name and date of the check: you, and monitors you share with. That you were verified, and when: anyone you give a code to |
| Contacts, photos, camera, microphone | No The MeetingSlip app never uses your camera. The ID check runs in our ID verification partner's own web page. | — | — |
| Background location | No | — | — |
| Other people at the meeting | No | — | — |
| Ads, tracking, in-app analytics | No | — | — |
We do not sell your data, share it for advertising, or track you across other apps and websites.
1. What we collect
Your account
A MeetingSlip account is its own account. It is separate from any SobaSearch account, even one with the same email, and signing in to one never signs you in to the other. We keep your name, your email address, your password, your time zone, and when you created the account. We never store the password itself, only a scrambled version (a hash) that can't be turned back into it.
Each time you sign in we create a session. For each session we keep a scrambled copy of its key, the time it started and expires, and the app name your phone reports. Sessions last up to 30 days.
If you ask to reset your password, we email you a link and keep a scrambled copy of its key until it's used or an hour has passed.
Your location
MeetingSlip asks for location access "while using the app." It reads your location at two moments:
- When the Today screen is open, to list in-person meetings within a mile of you. Your position is sent to our server to find those meetings. We don't save it with your account or in your records.
- When you tap Check in or Check out. Your phone takes one reading and sends it to our server. That reading is saved as part of your attendance record.
MeetingSlip never reads your location in the background, and it can't, because the app does not ask for that permission.
Each check-in and check-out
When you check in or out, the record saves:
- Your GPS latitude and longitude, how accurate the phone says the reading is, and your altitude if the phone provides it.
- The time on your phone, and the time on our server. The server's time is the one that counts.
- Your distance from the meeting, worked out by our server.
- Whether your phone reported a fake ("mock") location.
- Your phone's platform (iPhone or Android), operating system version, model (for example "iPhone16,1"), and the MeetingSlip app version.
- A device ID. On first launch the app makes a random number and keeps it in your phone's secure storage. Only a scrambled version of it (a SHA-256 hash) ever leaves your phone. It is not your phone's advertising ID or serial number. We keep it to ourselves. The signed record holds only a one-time stand-in made from it, which is different on every check-in, so no one who sees your records can recover the device ID or use it to link one record to another.
- A copy of the meeting as it was listed at that moment: its name, program (for example AA or NA), address, map location, schedule, and time zone. We copy it so that later changes to the listing never change your record.
- A verification code, such as PRS-7K3Q-M9XD, and the digital signature described under Security.
Face ID or fingerprint confirmation (required)
MeetingSlip needs Face ID, Touch ID, or a fingerprint to work. You set it up when you first open the app, and the app asks for it each time you check in or out. A check-in or check-out without it is not recorded. We require it so that every record shows the phone's enrolled owner was the one who checked in. If your phone has no Face ID, Touch ID, or strong fingerprint sensor, or none is set up, you can't use MeetingSlip until you set one up in your phone's settings.
- Your face and fingerprints never leave your phone. Face ID and fingerprint matching happen inside your phone's operating system. The MeetingSlip app never sees, stores, or sends an image of your face, a fingerprint, or any measurement of either. Neither do we, and neither does anyone you share with.
- What the app does get: a yes or no from your phone. Setting it up makes a key inside your phone's secure hardware (the Secure Enclave on iPhone, the Keystore on Android). Your phone uses that key only after its own Face ID or fingerprint check passes. The private part of the key never leaves the phone.
- What we keep: the key's public part, which kind of check the phone uses (face or fingerprint), your phone platform, when you set it up, and proof from Apple or Google that the genuine MeetingSlip app made the key in secure hardware: on iPhone, an Apple App Attest key for this app on your phone (its public part and a counter); on Android, the certificate chain the phone gives for the key. If that proof is missing or doesn't check out, your records say the app reported the check but it couldn't be independently verified. Each check-in also keeps a one-time code we sent and your phone's signature over it.
- When Face ID or fingerprints change. If someone adds or removes a face or fingerprint on your phone, your phone destroys the key. The app tells you and asks you to set it up again before your next check-in. We record that the key was replaced and why, and the next record says the enrollment changed.
If you cancel or it doesn't recognize you, nothing is recorded and you can try again as many times as you need, while check-in is open.
A confirmed check-in shows the phone's enrolled owner unlocked it at check-in. On its own it doesn't tell us whose face or fingerprint was enrolled on the phone, and it can't tell if someone else's face or fingerprint was added to the phone before you set it up. That is what ID verification is for.
Reports
When you make a report, we save the date range, the records in it, your name, a masked version of your email (like j•••@example.com), and, if you type them, who the report is for and a case or reference number. Your full email address never appears on a record or report.
When you contact us
If you email us, we keep the email and our reply so we can help you.
On your phone
The app keeps your sign-in key and the random device ID in your phone's secure storage, plus one setting that remembers you've seen the Reports intro. The Face ID or fingerprint confirmation key lives in your phone's secure hardware, and the app remembers which key it registered. When you share a PDF report, your phone makes the file itself.
2. What we don't collect
- No background location. No location history between check-ins.
- Nothing about anyone else at the meeting: no names, no photos, no nearby phones.
- No contacts, photos, camera, microphone, calendar, or health app data. The ID check uses your camera in our ID verification partner's web page, not in the MeetingSlip app.
- No face, fingerprint, or other biometric data. Face ID and fingerprint checks happen on your phone; we only learn whether they passed. For ID verification, our ID verification partner compares your selfie with your ID photo; we get only the result, never the images or the face data.
- No ID photos, ID numbers, or full date of birth.
- No advertising ID. No ads. No ad or analytics tools inside the app.
- No crash-reporting tool inside the app.
- We don't sell your data or trade it with anyone.
3. Why we collect it
- To make the record. A record is only worth something if it shows where and when. Location, times, and distance are the proof.
- To catch cheating. The mock-location flag, GPS accuracy, device details, and device ID help show whether a record is believable. Everyone who checks a record sees the same facts.
- To confirm who is sharing. Face ID or a fingerprint shows the phone's enrolled owner checked in. ID verification shows a monitor the account belongs to the person named on it.
- To run your account. Your name and email let you sign in, and your name goes on the records you share.
- To keep the service secure and working. Session details help us spot misuse of accounts.
We don't use your data to build an advertising profile, and we don't use it for anything unrelated to MeetingSlip.
4. Who can see your records
You. When you're signed in, you can see all of your records and reports.
Anyone you give a code or link to. Every record and every report has its own verification code, printed with a QR code. The code works like a key. Anyone who has it can open that record or report at meetingslip.com/verify, without signing in. A report's code also opens each record inside it. Older sobasearch.com/verify links send you to the same page.
Treat a code like a house key. Give it only to the people you want to see that record, such as your monitor. Right now you can't switch a code off once you've shared it.
Someone with a record's code can see:
- Your name (or "Name not provided") and masked email.
- The meeting's name, program, address, and scheduled time.
- When you checked in and out, your distance from the meeting, the GPS accuracy, and your position rounded to about 11 meters.
- Your phone platform, app version, and whether a mock location was reported.
- That the check-in was confirmed with Face ID or a fingerprint, and since when that phone's enrollment has been the same. Confirmed check-ins name the same phone key, so someone with several of your codes can tell they came from the same enrollment.
- If you had verified your ID when you checked in, that your identity was verified with a government ID, and the date. Not your ID, its details, or your birth year.
- Under "Technical details," the full signed entry, so an expert can check the signature. That entry also contains your exact coordinates, altitude, phone model, operating system version, phone time, and a random ID the app made for that check-in. In place of your device ID and account number it holds one-time stand-ins that change with every check-in. They can't be turned back into either, and they don't link one record to another.
Someone with a report's code also sees the date range, the totals, and the recipient and case number if you added them.
Nobody who opens a code sees your full email address, your device ID, or your account number.
Monitors you choose to share with. A monitor is someone you choose to share your attendance with, such as a probation or parole officer, a court or treatment program, a case manager or counselor, a sponsor, or a family member or friend. If you pair with a monitor in the app and tap Allow, they (and anyone on their monitor account, such as colleagues at the same agency or program) can see your name, your records (with their codes, and how each check-in was confirmed with Face ID or a fingerprint), your streaks and totals, and reports they make, until you stop sharing. Before you can share, you verify your ID (see ID verification); your monitor then sees "ID verified as" the name on your ID, and the date. They never see your ID photos, your selfie, your birth year, or your ID number. They never see your full email address, password, device ID, or account number. You can see each time they looked, and stop sharing at any time in Sharing on the Account tab. If you stop, they see only that sharing stopped, and when.
Email alerts and summaries for monitors. A monitor can choose to get emails about your check-ins: an email for each check-in, an email when you haven't checked in for a number of days, and weekly or monthly summaries. These emails contain only what the monitor can already see in the MeetingSlip web app. Each email that includes your records appears in your access log, like a visit to the web app. They stop when you stop sharing.
Our team. MeetingSlip staff may access account and attendance data to provide support, handle billing, keep the service secure, and respond to legal requests. Every time staff open your account or records, or take an action on an account, it is written to an access log that can't be edited or deleted. We don't browse your records.
When the law requires it. We may have to hand over records if a court order, subpoena, or other legal process requires it. We will push back on requests that are too broad, and, where the law allows, we will tell you first.
If SobaSearch changes hands. If SobaSearch is sold or merged, your data may move to the new owner, who must keep honoring this policy.
5. ID verification
You need to verify your ID only to share your attendance with a monitor. You can use MeetingSlip on your own without it. We ask for it so a monitor knows the account belongs to you, the person named on it.
Who does the check
An identity verification provider does the check for us. It acts as our service provider. The check runs in the provider's own web page, which opens inside the app. That page links to the provider's privacy policy and its identity verification notice, which explain how the provider handles your data.
What the provider collects
- A photo of the front and back of your driver's license or ID card, or of your passport.
- A selfie, taken with your phone's camera.
- To check the selfie matches the ID, the provider makes a scan of the face in each photo (face geometry) and compares them. This is biometric data. The provider also reads the details printed on the ID.
Your consent
Before the check starts, the app explains what the provider collects, why, and how long it is kept, and asks you to tick a box to agree. You can't start the check without agreeing. We record your agreement, with the date and the exact text you agreed to, as a signed entry in your account. If you don't agree, you can still use MeetingSlip on your own; you just can't share with a monitor.
What MeetingSlip keeps
The provider tells us the result. From it we keep only:
- your first and last name as printed on the ID;
- your birth year (not your full date of birth);
- the type of ID, the country that issued it, and its expiry date;
- whether the check passed, when, and, if it didn't, the provider's reason code;
- the provider's reference number for the check;
- which monitor's pairing code led to the check, so that monitor pays for it;
- your account name at the time, so we can tell if it changes.
We never receive or keep your ID photos, your selfie, the face data, your ID number, or your address. Nobody you share with sees them either.
How long it lasts
A check counts for two years. After that, or if you change the name on your account, you verify again before you share with a new monitor.
How long it is kept
- At the provider. The provider keeps the photos, selfie, and details under its own retention policy. When you delete your MeetingSlip account, we ask the provider to delete (redact) every verification you made. If the provider can't be reached, we keep asking until it confirms.
- At MeetingSlip. The details listed above are kept while your account exists and erased when you delete it. Your signed consent entry is erased with the rest of your records.
We don't sell, rent, or trade your ID data or face data, and we don't use it for anything except confirming that the account belongs to you.
6. The public verify page
The verify page, meetingslip.com/verify/code, is built to keep codes private:
- It loads no analytics. In fact, no page on meetingslip.com does.
- It tells search engines not to list it.
- It tells browsers not to pass the address along when someone clicks a link away from it.
- Our error monitoring removes verification codes before any error report leaves our server or the browser.
7. Health information
Going to a recovery meeting can reveal something about your health, such as a history with alcohol or drugs. Records include the meeting's name and program. We treat all of it as sensitive:
- It's private by default. Only you decide who gets a code.
- We never use it for ads, never sell it, and never share it with data brokers.
- The app's name, icon, and screens never mention a program or recovery, so it stays discreet on your phone.
SobaSearch is not a doctor, clinic, treatment program, or health plan. That means we are not a "covered entity" under HIPAA, the US health privacy law, and HIPAA's rules don't apply to MeetingSlip. We protect your data because it matters, as this policy describes. If your treatment program or court keeps a copy of a record you gave them, their own rules govern that copy.
8. Companies that help us
We use a few service providers. They may handle your data only to provide their service to us.
| Company | What it does for us |
|---|---|
| Cloudflare | Hosts meetingslip.com, sobasearch.com, and the app's server, protects them from attacks and abuse, and keeps short-lived request logs. |
| Supabase | Hosts our database, where accounts, records, and reports are stored. |
| Identity verification and payment provider | Checks your ID when you share with a monitor (see ID verification). Also handles monitors' payments, which hold no data about you. |
| Resend | Sends the password reset emails you ask for, and the alert and summary emails a monitor chooses to get. It receives the address each email goes to and the email itself. |
| Sentry | Tells us when a web page or our server hits an error. Verification codes are removed first, and it is set not to collect personal details. It is not in the app. |
| Fathom Analytics | Counts visits to sobasearch.com without cookies. It does not run on meetingslip.com, on any verify page, or in the app. |
| Apple and Google | Deliver the app through their stores. The map in the app is drawn by Apple Maps on iPhone and Google Maps on Android, which receive the map area on screen to draw it. |
Members never pay for MeetingSlip. Monitors, such as agencies, treatment programs, counselors, sponsors or family members, pay us through our payment processor, including a one-time setup fee for each member they monitor, which covers that member's ID check.
9. How long we keep it
- Records and reports are kept for as long as your account exists, and erased when you delete it. They are append-only: nobody, including us, can edit one in normal operation. A correction is added as a new, signed entry. This is what lets a court trust them.
- Your account details are kept until you delete your account. Deleting it erases your records and reports too (see Deleting your account).
- ID verification details are kept until you delete your account. Our identity verification provider keeps its copy under its own policy, and we ask it to delete that copy when you delete your account (see ID verification).
- Nearby-meeting lookups are not saved by us. Our hosting provider's request logs may hold them briefly.
- Sessions expire after 30 days or when you sign out.
- Support emails are kept as long as we need them to help you.
Signing out of the app does not delete anything. Your records are still there when you sign back in.
10. Deleting your account
You can delete your account yourself, at any time. In the app, go to Account, then Delete account at the bottom. You'll re-enter your password and type DELETE to confirm. If you forgot your password, reset it from the sign-in screen first. If you can't sign in at all, email hello@sobasearch.com from the address on your account and we'll do it for you once we've confirmed it's really you. Deleting your MeetingSlip account doesn't touch a SobaSearch account, if you have one.
Deletion happens right away and can't be undone. We erase:
- your name, email address, password, time zone, every signed-in session, and any unused reset link;
- your registered Face ID or fingerprint confirmation keys and any unused one-time codes;
- your ID verification details (name on the ID, birth year, ID type, country, expiry, and result), and we ask our identity verification provider to delete (redact) its copy of each verification;
- every check-in, check-out, and report: the meeting details, the GPS readings (position, accuracy, and altitude), the phone details, and any recipient or case number you added to a report;
What we keep. For each verification code you were given, we keep a short note: the code, whether it was a record or a report, the date it was issued, and the date it was deleted. Nothing in that note says who you are or which meeting it was. We keep it so that anyone who opens a code you shared sees "This record was deleted at the member's request on (date). It can no longer be verified," rather than "No record found," which could look like a fake code.
Before you delete, know this: once your records are gone, no code you've shared can be verified, including codes on PDF reports you've already handed over. If you may still need proof, make and save a report first, and keep your account until you no longer need it.
Backups. Our database provider, Supabase, keeps backup copies of the database. Deleted data stays in those copies until they roll off on Supabase's backup schedule, and we never restore a deleted account from them. If the law requires us to keep something, for example because of a court order, we'll keep only that and tell you, unless the law forbids it.
11. Security
- All traffic between the app, the website, and our server is encrypted (HTTPS).
- Passwords and session keys are stored only as hashes. On your phone, the sign-in key is kept in the system's secure storage.
- Every check-in, check-out, and report is digitally signed with an Ed25519 key that only our server holds. Each entry includes a SHA-256 fingerprint of the one before it, so a missing or changed entry is easy to spot. Our public keys are published so anyone can check a signature without trusting us.
- The database refuses edits and deletions of attendance entries, and the public can't reach it directly. The one exception is deleting your account, which erases all of your entries at once and nothing else.
No system is perfectly secure. If we learn of a breach that affects your data, we'll tell you as the law requires.
12. Your choices and rights
- Location. You can turn off location for MeetingSlip in your phone's settings at any time. You won't be able to check in without it.
- Sharing. You choose which records and reports to share, and with whom.
- ID verification. You choose whether to verify your ID. Without it you can still use MeetingSlip, but you can't share with a monitor in the app.
- A copy of your data. You can see every record in the app and make a report for any date range. Email us for a full copy.
- Corrections. Records can't be edited, but if one is wrong, email us. A correction is added as a new signed entry.
- Deletion. See Deleting your account.
Some states, such as California and Washington, give you extra rights over personal and health data, including the right to know what we hold, get a copy, have it deleted, and not be treated differently for asking. We honor these requests for everyone, wherever you live. Email us to make one. If we say no, you can ask us to reconsider.
13. Age limit
MeetingSlip is for adults 18 and older. Records are often used by courts and probation offices, and we don't want to hold this kind of record about a child. If we learn that someone under 18 has an account, we'll delete it. If you think a child has signed up, email us.
14. Where we operate
SobaSearch is based in the United States, and MeetingSlip is meant for use in the United States. Our providers may process data in the United States and other countries.
15. Changes and contact
If we change this policy, we'll post the new version here and update the date at the top. If a change matters, such as a new use of your location, we'll tell you in the app or by email before it takes effect.
Questions, requests, or concerns: email hello@sobasearch.com. We read every message.
See also the MeetingSlip terms of use.