Skip to main content
Bell & Beyond by lexpro.app
  • School-run programsA school already on Carline adds after school programsYMCA and community programsSeveral sites, your own staff and partner schoolsParks and recPrograms at each site, with places by dayClubs and campsYour own terms, schedules and check-out
  • Programs

    Programs and schedulesRegistration and waitlists

    The afternoon

    The program deskCheck-out with custody checksThe kiosk

    Running it

    Invoices and paymentsRatios and staff time
  • How it worksStep by step, through a typical dayFor familiesWhat families see and do in the appWorks with CarlineThe handoff from a school’s classroom boardHelp centerAnswers and how-tos for every screenFAQShort answers to common questionsPrivacy and securityWhat we keep, who can see it, and how it’s protectedContactAsk a question or book a demo
  • Pricing
  • For K–12 schools
Español Log in Book a demo

Legal

Privacy policy

Plain language, and the same facts as the rest of the site. If this policy and our privacy page ever disagree, tell us — one of them is wrong and we will fix it.

Last updated: 2026-11-14

Plain language

This page is written to be read. Each clause says what the product actually does, in plain words, and where a clause sets a limit, a line above it says what it is for.

The short version, before the long one.

  • The program that holds your family’s records decides what happens to them — an independent program, or the school that runs its own. We act on its instructions.
  • We collect what a program’s day with children needs and nothing else: names, contact details, which adult goes with which child, each registration and place, who may collect, any custody order the program records, each check-in and check-out, and the bills.
  • Nothing about a child passes from their school to an independent program unless the school allows it and a parent agrees.
  • We never sell or share data for advertising, and we run no third-party trackers.
  • We never track or store your location. If a program has marked a site’s grounds and you tap “I’m here” in the app, it reads your phone’s location once, and we keep only whether you were at the site.
  • You can get your data out, and you can ask us to delete it.

1. Who we are, and which role we play

An independent program — a YMCA, a parks and recreation department, a club, a camp or a center that no school runs — decides what happens to its own records: its families and children, their registrations and form answers, their places, each program day, its own custody orders, its messages and its bills. LexPro holds them on the program’s behalf and acts on its documented instructions under its agreement — in the language most privacy law uses, the program is the controller and we are its processor.

A program a school runs for its own children is part of the school’s records. The school is the controller of it and we are the school’s processor, as we are for the rest of the school’s records.

An independent program and a child’s school are separate. Nothing about a child passes from the school to the program until the school grants it and the child’s parent agrees, and then only the facts the school’s grant names — such as whether the child is expected today, their first name and last initial, and their classroom. The one exception is a signal with no detail that a child is held at check-out under a custody order the school recorded, which the school’s grant alone allows. A program’s own custody orders never reach the school.

For this website — the contact form, and the server logs behind it — nobody is instructing us, so for that small amount of data LexPro is the one deciding.

LexPro is LexPro LLC, Lexington, Kentucky. A formal notice goes to that address by post, with a copy by email to the address at the end of this page.

Under FERPA, the US law on student records, LexPro acts for a school that runs its own program as a “school official” with a legitimate educational interest, under the school’s direct control. We use those records only for the school’s purposes, and we do not disclose them to anyone else except as the school directs or the law requires. An independent program’s records are its own, not the school’s: what a school tells one moves only under the school’s grant and the parent’s consent above.

2. What we collect, by category

a. Your program’s data

  • A child: first name and last name as the family gives them, and a date of birth only if the program asks for one; the child’s guardians, how each is related (from a fixed list), whether each may collect and gets notices, and who pays and their share. At a site in a school, and only once the school confirms it, which of the school’s students the child is, with who proposed and who confirmed that match.
  • A parent or guardian: first name, last name, email address and telephone number. There is deliberately no home address on a parent — a pickup needs to know which children someone may collect, not where they live.
  • Registrations: the answers a family gives on the program’s form — the emergency contacts and health section every form asks, and the questions the program adds — where a private answer (the health section always, and any question the program marks private) is kept encrypted, shown only to staff given that permission, and every look recorded; the program’s policies and each signature on them (the full name typed, when, and a fingerprint of the text signed — no drawn signature and no stored file); and a place held for a child in a re-enrollment window, with whether the family took it or declined it.
  • Places: each enrollment (the program, the term, week, session or days, the dates, and any waitlist place or move), the reason a place moved, and the payment plan and options chosen for it.
  • The record of each program day: when a child was received, from class or at the door, which group they were in or moved to, when they were checked out and to whom, with a staff note of any ID check, or why they were not expected (a reason from a short list); a guardian’s word for the day — not coming, collecting early and when, or another adult collecting, with that adult’s full name, checked against a photo ID at the desk; and a late-pickup fee: the minutes after close, whether it was approved or waived, who decided, and the reason staff gave for waiving it.
  • Adults a family names to collect: their name, how they are related (from a fixed list), a phone number if the family gives one, which children, and whether the program has approved them; and, where a school’s grant allows it, whether an adult the school approved may collect at the program too — the name appears only at check-out, when that adult is the one being checked.
  • Custody orders the program records: the person named, or their account, the kind of order (do not release, or check with the office first), its dates, whether a document is on file (the document itself is not stored), a staff note, and a history of every change to the order, which cannot be edited or deleted.
  • A member of staff: first name, last name, email address and telephone number, their role (admin, site lead or staff), the sites they work at, and the permissions granted to them.
  • For a program that tracks ratios: who was on duty at which site and group, from when to when and who marked it, and each group’s name, size and ratio of children to one adult. It is not a timesheet: no pay, rate or hours total is held, and it names no child.
  • For a program that records staff certifications: each credential from a fixed list (CPR, first aid, background check, fingerprinting, state childcare training, or another the admin names), its issue and expiry dates, and where the paper is kept or its number; never the document itself. It is a reminder only and never stops anyone working. For a program that schedules staff: who is planned at which site, group, day and time.
  • The language a parent or staff member chose in the app (English or Spanish), if they chose one, so the emails sent to them are in it. It is never counted, reported on or used for anything else.
  • Your program’s setup: its name and kind, its sites (a center’s business address and hours, or the school a site is at) and, if the program sets one, a point and radius marking a site’s grounds; its programs, terms, sessions and groups; the days it is closed, with a short note in its own words. A history of who changed who may collect — custody orders, the adults families name — and of our support team joining or leaving, which cannot be edited or deleted; and an access log of each time someone opened a family’s registration, revealed a private answer, downloaded a household’s record or took a year-end statement, which keeps ids only.
  • Where a program uses a kiosk tablet by the door: each tablet’s name and how many numbers it failed to find recently (over the last few minutes and the last day; never the digits typed — an adult types the last four digits of the phone number already on their account, and nothing else is stored for it); and each “Drop off” or “I’m here to collect” a family asked, who asked, when, what became of it and, for one asked in the app, whether the phone was at the site — never where it was.
  • Messages from the program: the subject and words of each announcement, who wrote it, which sites, programs or groups it went to, and whether each family’s push, text and email were delivered; and, if it was withdrawn, who withdrew it and why. No attachments.
  • Incident reports, when staff record one: what happened, from a fixed list (an injury, an illness, behavior or something else), when, where (from a fixed list, with a short place name if staff add one), which children were involved, where on the body and the first aid given (each from a fixed list), how and when a guardian was told, which staff were involved, who recorded it, and a short factual note (at most 500 characters, beside a warning not to enter health information) — never a diagnosis. Each child gets their own report; their guardians read it and sign that they read it (the name typed and when), and once one has, the report can’t be changed, only added to by a dated note. A guardian never sees another child’s name or the staff names; an adult a custody order keeps from the child sees nothing of it.
  • Field trips, when staff plan one: the trip’s name, date, times, destination and any details, as staff typed them; the staff going; which children are on its list, and any a member of staff took off it; each family’s answer to the permission slip, yes or no — signed in the app or on the web with the parent’s own full name, typed, and when, or recorded by staff from a signed paper slip with the date written on it — and a fingerprint of the trip’s text it answered; and the head count: when each child left on the trip and was counted back, and any missing or found mark, each with the member of staff who marked it, and each count as two numbers, expected and counted.
  • Billing, for a program that bills families in the app: its fee plans and discounts; each household’s invoices, payments, deposits, credits, refunds and disputes as the program’s own Stripe account reports them, with the reason staff gave for a credit or refund; for autopay, the kind of card or bank account and its last four digits; and a payer who is not a guardian (a subsidy agency, an employer or a scholarship): its name, the email its invoices go to, its share, and the agency’s own reference for the family’s authorization — never an income figure. For the program itself: its Stripe account’s id and status, and its employer identification number, if it gives one, kept encrypted and shown only by its last four digits — except on the year-end dependent-care statement a paying parent downloads, which prints the whole number, names the children the year’s payments were for, and is written to the program’s access log before it is given. A child’s name is never sent to Stripe.
  • Between a school and an independent program: which school accepted which program, which facts it granted and when it changed them, and each parent’s consent to that, with when it was given or withdrawn and the wording they agreed to.

b. Account and security data

  • A password, held only as a one-way Identity hash. We never hold the password itself, never log it and never email it.
  • Whether the email address has been confirmed, when the account last signed in, the failed-attempt counters behind the fifteen-minute lockout, and whether the account has been disabled.
  • The session: a cookie in the browser, or an opaque token in the phone’s keychain. Neither carries anything about the person beyond which account it belongs to.
  • Invitations: which account was invited, by whom, when the invitation expires, and a SHA-256 hash of the invitation token — never the token itself, so we cannot reproduce the link, even to help.
  • Password reset links: the same kind of hash, never the link itself, with when it was asked for and used. A link works once, for an hour.
  • If you link a Google, Microsoft, Apple, Clever or ClassLink sign-in to your account (Google, Microsoft and Apple sign-in are on; Clever and ClassLink are not switched on yet): that provider’s id for you, your organization’s domain or tenant if the provider gives one, and when it was linked and last used. Never the provider’s tokens, and nothing else from the provider’s account.

c. Notification data

  • For a phone with our app that allows notifications: the push token Firebase Cloud Messaging gave it, the platform, the app version and language, and when it was last seen. A phone not seen for thirty days is dropped, and signing out stops its notices at once.
  • For someone who wants texts: their mobile number, that it is confirmed (by a six-digit code that works for ten minutes, of which we keep only a salted hash), and when they agreed to texts and to which wording. Replying STOP withdraws it.
  • Which notices each person wants on which channel, and a record of each notice sent — who, which channel, when, and whether the provider accepted it. Never the text of the notice.
  • A program’s message is sent to the push, text and email providers as written.

d. Website data

  • What you type into the contact form: your name, your email address, your organization, your role and phone number if you give them, and your message.
  • Ordinary server logs — the request, the time, the address it came from — kept for security and for debugging.

What a program’s records never hold: photographs, license plates, whole card or bank numbers, advertising identifiers and third-party analytics. These are not settings we turned off. Nothing in Bell & Beyond asks for them. Where families pay in the app, Stripe holds the card or bank details and we keep only the last four digits (clause 4). A date of birth is held only where the program’s form asks for one (above).

Health cards (allergies, dietary needs and a medical note), a medication log and documents a family sends about a child are built too, and are switched off at every program for now. Before any of them is switched on, this policy will describe what it keeps.

Location is the one exception, and only where a program marks a site’s grounds: when you tap “I’m here” in the app to drop off or collect, the app sends one reading of your phone’s location with that request. It is compared with the site’s grounds and dropped at once; only whether you were at the site is kept. The reading is never stored or logged, nothing is read in the background, and there is no column for where you were. The kiosk sends no location at all.

3. Why we use it

  • Program data: to run the program’s day with children. To register each child and hold their place, receive them from class or at the door, show your staff who may collect each child, check them out at the desk, bill the family, and keep the record of it.
  • Account and security data: to sign the right people in, keep everyone else out, and end a session when a program disables an account.
  • Notification data: to tell a family about their own children’s day at the program, on the channels they chose — a child received or checked out, or not yet received, a message from the program, an incident report, a field-trip permission slip, a bill or a payment that failed — and to tell staff what their work needs. Nothing else.
  • Website data: to answer you, and to keep the site standing up.

Program data is never used to market to anyone. We do not email parents about Bell & Beyond. We email a parent because a program invited them or they made an account to register a child, because their invitation is waiting, to reset or confirm a change of their password, to confirm that they deleted their account, to deliver a message from the program, to tell them an incident report about their child is ready to read, to ask for a field-trip permission slip, to offer a place in a re-enrollment window, and to send a program’s bill or say a payment failed.

There is no clause here that quietly widens this with “legitimate interests”. If we ever want program data for something other than providing your program’s service, we will ask your program first and this page will say so.

4. Who sees it

Inside your program

At an independent program, staff see what their role and their granted permissions cover, at the sites they work at. An admin holds every permission at every site. A site lead works the desk, sees families and reads and records incident reports at their own sites, plus what they are granted. Anyone else holds only what they are granted, one permission at a time: enroll children and manage registrations and the waitlist, work the desk, see families, see private registration answers, manage custody orders, see invoices and payments, run billing, credits and refunds, manage staff, see reports, send messages to families, read incident reports, and record incident reports (someone who only records them reads only their own). Only an admin may grant managing staff, running billing, private answers or custody orders. Every other account starts with none.

At the desk, staff see each child expected today, who may collect them and whether a custody order holds them — never the detail of a school’s order, and never an unpaid balance, which never stops a check-in or a check-out.

At a program a school runs, the people are the school’s own staff, under the permissions the school grants them one at a time; the privacy policy of the school’s own product names every one, and working a program’s desk is granted for the programs a member of staff is assigned to.

A child’s school

A school a program works with sees which of its students the program has asked to match, the facts it has granted, how many parents have consented, and the program’s reads through that grant, by day. It never sees the program’s own custody orders.

What each role and permission covers →

Inside LexPro

Our staff can manage a program’s account — invite its first admin, say — without ever reading its families. To read an independent program’s records, a member of our support team has to be added to the program as a member (the next paragraph).

A member of our support team may be added to a program as a member — an admin, a site lead or staff — only to help that program: to set something up with it, or to see what its people see while we work on a problem. They appear on the program’s staff list like anyone else, their joining and leaving are recorded in the program’s history, what they open of a family’s registration is in the program’s access log like anyone’s, and they are removed when the help is done. We never add someone to a program for any other purpose.

Outside

The services we use to run it, our sub-processors: Google Cloud, which hosts the service, its database and its files (Cloud Run, Cloud SQL and Cloud Storage, in the United States) and, when push notifications are switched on, delivers them through Firebase Cloud Messaging (which hands an iPhone’s notices to Apple’s push service); Brevo, which delivers our email; Stripe, which takes a program’s subscription payments to us, under its standard data processing terms; and Twilio, which sends text messages when texts are switched on (they are off at launch). The email, push and text providers see an email address, a device token or a phone number, and the contents of each message; a message the program writes to families goes to them as the program wrote it. For a program’s subscription, Stripe receives the program’s name and the paying admin’s email, and takes card details on its own pages: we never see or store a card number, and that payment sends Stripe no child or family data. We do not use Stripe Tax. We will name any new provider on this page before it is used, and tell programs before we change one.

Family payments. When a program bills families in the app, the payments run on that program’s own Stripe account, connected to Bell & Beyond through Stripe Connect: the program is the merchant, and Stripe is its payment processor. To bill a family we send that account the paying parent’s name and email (or a payer’s name and the email its invoices go to), the invoice lines (the program, the schedule and the period — or, for a late-pickup fee, the date and how many minutes after close — never a child’s name) and the amounts. The parent enters card or bank details on Stripe’s own pages; we keep Stripe’s references, what Stripe reports about each invoice and payment, and for autopay only the card’s or bank account’s last four digits.

That Stripe account is the program’s, not ours. The program accepts Stripe’s own terms when it connects the account, gives Stripe the details Stripe asks of a business, pays Stripe’s processing fees, sees everything in its own Stripe dashboard, and answers for refunds and disputes on its payments. For those payments Stripe is the program’s payment processor, under the program’s agreement with Stripe; it is not our sub-processor for them. We send the account only what billing a family needs (above), because the program bills that family in the app, and we take the platform fee the terms describe. A program can disconnect its account from us in Stripe at any time.

Each provider above handles the data under its own standard data processing terms, which are part of the terms we accept to use it: Google’s for Google Cloud and for Firebase, and Brevo’s, Stripe’s and Twilio’s for theirs. We have not negotiated different terms with any of them.

Nobody is texted without agreeing to it. A person who turns on texts confirms their number and agrees to this wording: “I agree to receive automated pickup texts from Bell & Beyond at this number. Message frequency varies with pickups. Message and data rates may apply. Reply STOP to cancel or HELP for help. Consent is not a condition of using the service.” We keep when they agreed and to which version of the wording. Replying STOP, the text provider telling us the number has opted out, or switching texts off ends it, and a new number has to be confirmed and agreed to again.

You can sign in with Google, Microsoft or Apple. Clever and ClassLink sign-in are not switched on yet. If you sign in with Google, Microsoft, Apple, Clever or ClassLink, that provider handles the sign-in and tells us who you are: its id for you, your email and, for some, your organization’s domain or tenant. We ask for nothing else and keep none of its tokens.

We do not sell data, share it for advertising, or use it to train models. There is no third-party analytics script on this site and no advertising identifier in the app. The site and the web app load their code and fonts from our own servers, with one exception: to show a character none of our fonts include (an emoji, say), the web app fetches a font from Google Fonts, which sees that request and your IP address.

5. How long we keep it, and what deletion means

Program data stays for as long as your program uses Bell & Beyond, except where the schedule below erases it sooner, and on exit we act on your instruction: an export first, then deletion if that is what you want.

Nothing is ever hard-deleted by the app. Removing a child, a family or a member of staff hides them everywhere in the product and, for a member of staff, ends their access. It does not erase the days they were part of, because the program’s record is a record. Every foreign key in the database is set to restrict, so the database itself refuses to erase a row that anything still refers to.

Hiding a person from the app is immediate and your program can do it. Erasing their name and details out of the record is done in place — the rows stay, so the program’s counts still add up, but the names and notes in them are gone — in two ways, and each run is written to a register your program’s admins can read: when your program’s admin asks, and we approve and run it; and by a retention job that runs every night, on this schedule:

  • A child who has left — no place, and none ended or asked for in the last year — or who was removed more than a year ago: their name, date of birth and everything held about them.
  • A household removed more than a year ago, or whose children have all been erased and that has had no place for a year: everything held about it, except its billing records (below), and never while one of its invoices is still to settle.
  • A program’s registration answers: a private answer once the child has no place left at the program; every other answer a year after the child’s last place there ended. The reasons a place moved, and names typed on the program’s policies outside a registration: a year after the household’s last place ended.
  • A saved card or bank account for autopay: a year after the household’s last place ended, and at once when the payer’s account is deleted.
  • A program’s day records — the names, notes and events of each program day, the adult a guardian named for a day, and the names typed on field-trip permission slips: for the period the program sets, between one and seven years, and two years if it sets none.
  • A custody order lifted or deleted, and an adult a family named to collect once removed: one year.
  • A note on a day the program is closed: once the day is past the day-record period above. A site removed more than a year ago: its name and address. A group retired more than a year ago: its name.
  • A member of staff removed from the program: 90 days.
  • A staff certification: erased with the member of staff (90 days after they are removed) or with the program; the credential’s typed name and where the paper is kept or its number are cleared.
  • The detail of an incident report — the place name, where on the body, the first aid, the staff named, the note, its added notes and the guardians’ typed names: with the program’s record of the child. That a report existed, its kind and its times are kept.
  • The words of the program’s messages: two years after they were sent.
  • An account its owner deleted (a parent’s): one year after the deletion.
  • Billing records — invoices, payments, credits, refunds and disputes, with their reasons and references: seven years.
  • A program that has closed its account: everything held about it, a year after it closed; its employer identification number at once.

A legal hold your program places stops the erasure of what it covers until the program releases it.

A program a school runs follows the same schedule, and its records are also erased with the school’s, on the school’s instruction.

Contact-form messages are anonymized two years after they were sent.

When a program closes its account, its data is erased when the program instructs us to, and otherwise on the schedule above.

Server logs are kept for 30 days, Google Cloud Logging’s default. The database’s automated backups are kept for 30 days; the extra backup we take before each update of the service is deleted by a later update once it is a week old.

Incident reports and licensing rules. A state’s child-care licensing rules may require a program to keep incident reports or attendance for longer than the schedule above. The schedule is the same everywhere, and we do not check anyone’s licensing rules for them. A program whose rules ask for longer sets its day-record period to match, or places a legal hold on the children concerned, which keeps their records until it releases the hold; or it downloads its records before then, and the download includes every incident report.

Custody orders, ID checks and other adults. A custody order is kept whole for as long as it is in force. One year after it is lifted or deleted, the name in it, the staff note, the reason it was lifted, and the before and after of each change in its history are erased; that the order existed, for which child, and when it was entered and lifted are kept, so the record still shows what the program acted on. When a child is collected, the name staff recorded of who took them and the note of any ID check are part of that day’s record, and are erased with it. An adult a family named to collect is erased one year after the family removes them. Each of these is also erased with the child’s record, and a legal hold keeps it until the hold is released.

6. Children

No child ever holds an account. Children have no login, no password and no way to sign in, because nothing a program does with Bell & Beyond needs one.

We receive information about a child from the program and from the child’s own family — and, only as clause 1 describes, from the child’s school — never from the child, and we use it only to provide that program’s service. No advertising, no profiling, and no automated decision is ever made about a child.

COPPA, the US children’s online privacy law, is about information collected online from a child under 13. We collect nothing from a child: no child uses Bell & Beyond, and every record about a child is entered by the program’s staff or by the child’s own family.

7. Your rights, and how to use them

If you are a parent, two things you can do yourself, from your own account: download your records (a file of what the programs and schools you use hold about you and your children), and delete your account. If you pay a program in the app, you can also download a year-end statement of what you paid it.

For anything else, and if you are a member of staff, go to the program. It controls the data and we act on its instructions, so it is the one that can answer for it — and we help it answer. A program’s admin can download a household’s whole record to do so.

If you filled in the form on this website, write to us directly at the address below and we will deal with it ourselves.

We are not going to print a response time we have never had to meet. Until we can stand behind a number, the commitment is this: as quickly as we can, and always with a reply.

hello@lexpro.app

8. Security

  • Passwords are stored only as an Identity hash; at least ten characters and four different ones; five failures locks the account for fifteen minutes.
  • Every failed sign-in returns the same answer and costs the same work, so the response cannot be used to find out which email addresses have accounts.
  • The web session is an HttpOnly, SameSite=Strict cookie, secure outside development, re-checked against the account every few minutes. The app holds opaque tokens in the device keychain, and Android backup is off so they cannot be restored onto another device.
  • Sign-in and invitation endpoints are rate limited, and every state-changing request needs a header that a cross-site page cannot add.
  • Private registration answers are encrypted, and every look at one is written to the program’s access log before it is shown.
  • The access log and the history of who may collect are append-only, and the database rejects any attempt to change or delete a line of them.

If a security breach exposes a program’s data, we tell the affected programs without undue delay, and as state law requires.

We describe mechanisms, not adjectives. There is no “bank-level” or “military-grade” anywhere on this site, because those phrases mean nothing.

The full account of how it works →

9. Where it lives, how this changes, and how to reach us

The data is hosted in the United States, on Google Cloud in its us-central1 region (Iowa): the service on Cloud Run, the database on Cloud SQL and files on Cloud Storage. The sub-processors in clause 4 handle what they need to deliver email, payments, push notifications and texts.

When this policy changes in a way that matters, we email program admins about it, and the “Last updated” line at the top of this page is changed with it.

If LexPro or Bell & Beyond is ever sold or merged, the buyer must honor the commitments in this policy, or the data is deleted.

Until we have an inbox dedicated to privacy, everything comes to the address below and gets read.

hello@lexpro.app

Bell & Beyond by lexpro.app

After school and camp management software.

Get Bell & Beyond on Google Play

Product

  • How it works
  • For programs
  • Payments
  • Pricing
  • FAQ
  • Help center

Who we serve

  • Programs
  • Families
  • K–12 schools →
  • Preschools →

Company

  • About
  • Privacy and security
  • Contact
  • Accessibility
  • Security
Bell & Beyond

© 2026 LexPro. Privacy policy · Terms · Delete account

Photos: Caleb Oquendo, Lara van der Walt, Thang Nguyen, Josh Meeder (Pexels); Jon Torres, Jochen van Wylick (Unsplash).

Interface design based on Untitled UI React (MIT license)

Ask a question

Are you a parent or guardian?

Please contact your child’s school. Your school manages your account and your child’s pickup, and we can’t see your child’s details.

Tell us what you’d like to know. Your question comes to our team by email, and we reply to the address you give.

Please don’t include a child’s name or details.

Home
Who we serve School-run programs YMCA and community programs Parks and rec Clubs and camps
Features

Programs

Programs and schedules Registration and waitlists

The afternoon

The program desk Check-out with custody checks The kiosk

Running it

Invoices and payments Ratios and staff time
Resources How it works For families Works with Carline Help center FAQ Privacy and security Contact
Pricing For K–12 schools
English Español
Book a demo Start free trial
Bell & Beyond by lexpro.app

Log in

or

Forgot password?