The phone call to verify pickup doesn’t scale.
Kiddypin gives schools a verifiable way to confirm exactly who is authorized to pick up each child, with a record of every check.
Approved — OK to release
Release Tolu Bello to Ada Bello.
Approved for pickup. · Logged at 4:12 PM
Kiddypin is launching soon.
Join the waitlist for early access. We’re opening school by school, and we’ll let you know when Kiddypin is ready at yours.
Parents
Tell us you want it, and which school. Interest from parents helps us bring a school on.
Schools
Get early access to verified pickup, with a record of every check.
The problem
A phone call can’t confirm who’s standing at the gate. Most schools find that out the hard way, not the safe way.
Not verifiable
A phone call confirms a voice, not an identity. There is no record of what was actually checked.
No audit trail
If a pickup is ever questioned, there is nothing to point to — no log, no timestamp, no record of who authorized it.
Doesn't scale with class size
Front-desk staff calling parents one by one works for a handful of children. It breaks down at scale.
How it works
Three ways a pickup gets authorized.
Every child has one or more of these on file. Gate staff check against them at the point of pickup, not over the phone.
Registered guardians
Parents pre-approve the people authorized to collect their child. Gate staff check them against ID at pickup.
One-off codes
For someone not on the standing list, a parent issues a single-use code for that one pickup. It expires after use.
Legal-hold override
A flagged restriction — for example, a custody order — blocks release to a specific person, regardless of any code or guardian match.
Every pickup, the same three steps.
Find the child
Gate staff search by the child's name and tick which children are leaving now.
Verify who's collecting
A registered guardian's photo, a one-time code, or a parent on the account. Restriction checks run on every attempt.
Release on a clear result
Approved, verify manually, or do not release. Every attempt is logged, whatever the outcome.
At the gate
See a pickup get verified.
Here’s the one-off code path, start to finish. Guardian checks and the legal-hold override follow the same shape at the gate.
Parent issues a one-time code
Generated in the app for a specific pickup, valid for a set number of hours.
Pickup code
482 913
Expires in 6 hours
The code is given at the gate
The person picking up states the code — no app or login needed on their end.
Gate staff enters the code
Typed into the gate console at the point of pickup.
Enter pickup code
System confirms the match
Checked against the issued code — expired or already-used codes are rejected.
Verified
4:12 PM
The record is saved
Logged automatically, the same way every attempt is — this is the same record shown below.
Pickup confirmed
Guardian: Ada Bello · 4:12 PM · Gate 2Example values throughout are illustrative only.
The record
A record of every check.
Kiddypin does not just ask a question at the gate — it keeps a record of the answer.
Every pickup attempt is logged — approved, flagged, or blocked.
Verification happens at the gate, checked against ID or a code, not over the phone.
Staff accounts are issued by the school. There is no self-serve staff signup.
Pickup confirmed
Guardian: Ada Bello · 4:12 PM · Gate 2Example log entry — illustrative only.
Questions
What parents and schools ask first.
How verification works, who can collect, and what happens to your data.
At the gate, staff search for the child by name and tick which children are leaving. Then they choose how the person collecting is authorized: a registered guardian (staff match them to the photo on file), a one-time code the parent issued, or one of the child’s parents on the account.
Kiddypin answers with a clear result: approved, verify manually, or do not release. Every attempt is recorded with who processed it and when, whatever the outcome.
Three kinds of people, all set up by you as the parent:
- The parents on your family account.
- Guardians you register, with a name, relationship and photo. You can authorize a guardian for all your children or only specific ones.
- Anyone else, for one pickup, with a one-time code you generate in the app. You choose the name, which children it covers, and whether it lasts 3, 6 or 12 hours. It stops working once it’s used.
A parent can add a restricted person to their family, for example someone named in a custody order. On every pickup attempt, before anything else, Kiddypin checks the name of the person collecting against that list.
If it matches, gate staff see “Do not release”, and a valid code or a guardian match can’t override it. The attempt is logged so the school has a record of it.
A school registers, and Kiddypin reviews and activates it. The school’s admin then creates accounts for gate staff. There’s no self-serve staff signup, so only people the school adds can verify pickups.
Schools include Kiddypin in the fees they already collect, per family, per term. Once the school confirms a family’s payment, that family’s pickups can be verified at the gate. Gate staff work from a phone, and admins get a dashboard of the day’s pickups and anything flagged.
No. A guardian is matched to the photo you registered, and someone with a one-time code just gives their name and the code at the gate.
Kiddypin keeps only what pickup verification needs: your children’s names and class, the guardians you register (name, relationship, photo), your contact details, and the record of each pickup attempt.
Gate staff see only what they need to verify a pickup: children’s names and class, and guardians’ names, relationships and photos. Payment details and pickup codes are never shown on the gate screen. Codes are stored scrambled (hashed), so not even the school can read them back, and staff can only see families at their own school. The privacy policy covers this in full.