Política de privacidad
En lenguaje sencillo, y con los mismos datos que el resto del sitio. Si esta política y nuestra página de privacidad alguna vez no coinciden, avísenos: una de las dos está mal y la corregiremos.
El texto legal que sigue está en inglés hasta que exista una traducción revisada.
Última actualización: 2026-11-14
En lenguaje sencillo
Esta página está escrita para leerse. Cada cláusula dice, con palabras sencillas, lo que el producto hace de verdad, y donde una cláusula fija un límite, una línea encima explica para qué sirve.
The short version, before the long one.
- Your center decides what happens to its data. We act on its instructions.
- We collect what the center’s day with children needs and nothing else: names, contact details, which parent goes with which child, how each child goes home, any custody order the center records, and what happened each day.
- We never sell or share data for advertising, and we run no third-party trackers.
- We never track or store your location. If your center uses the “I’m here” button and has marked its grounds, the app reads your phone’s location once, when you tap it, and we keep only whether you were at the center.
- You can get your data out, and you can ask us to delete it.
1. Who we are, and which role we play
Your center decides what happens to the information about its children and families. LexPro holds that information on the center’s behalf and acts on its documented instructions under its agreement — in the language most privacy law uses, the center is the controller and we are the processor.
An independent program your center does not run (an after-school or holiday program, say) decides what happens to its own records in the same way: it is the controller of them, and we are its processor. Nothing about a child passes from a center to an independent program until the center grants it and the child’s parent agrees, and then only the facts the center’s grant names. The one exception is a signal with no detail that a child is held at check-out under a custody order the center recorded, which the center’s grant alone allows.
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.
Where a center is subject to FERPA, the US law on student records, LexPro acts for it as a “school official” with a legitimate educational interest, under the center’s direct control. Whether or not FERPA applies to a center, we use the records about its children only for the center’s purposes, and we do not disclose them to anyone else except as the center directs or the law requires.
2. What we collect, by category
a. Your center’s data
- A child: first name, last name, an optional free-text age group, a room, the usual way home (car, bus and its route, walking, after-care or an activity), the center, and — only when the center loads its roster from its student information system — the child’s record id in that system, used to match the same child on the next sync. That is the entire child record. The record itself has no field for a photograph, a birthdate, a home address, a medical note, a grade report or an attendance history. The exceptions are the day’s pickup record: whether a child went home, and how, including being marked absent or being released early from the office; drop-off sign-ins and expected days, where the center uses them (below); and a reunification record (below).
- 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.
- A staff member: first name, last name, their center, whether they are an admin, the permissions granted to them, and — when the center gives access for a limited time — the date a permission or the whole account’s access ends.
- For a center with the Ratios & staff time add-on: which room a staff member or helper was marked in, from when to when and who marked it, and each room’s ratio of children to one adult; for a helper without a login, their first and last name, a role from a fixed list, whether they count toward a ratio and an optional last day. It names no child.
- For a center that uses staff clock-in: when each staff member or helper clocked in and out, who recorded it, any correction with its reason from a fixed list and a short note, and who approved or declined it; if the center checks the site, only whether each tap was on site (yes, no or not confirmed), never the location. No pay, rate or wage is held.
- For a center or 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.
- For a center in a school district, the district office’s people: first name, last name, email address, their district and role, and the list of what the district may do at its centers, which each center can see.
- 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.
- The link between them: which parent accounts are linked to which child, and the relationship if the center notes one, such as “Mother” or “Guardian”.
- Your center’s setup: its name, its time zone, its pickup time, how early check-in opens, the cutoff for parents’ changes, its rooms, the name of each pickup place with the random codes printed on its sign, the hangtag number issued to each family, whether the “I’m here” button is on, and, if the center sets one, a point and radius marking its own grounds — with a history of who changed any of it, a family link, a child’s room or a staff member’s role, permissions or sign-in, and when, which cannot be edited or deleted.
- Changes of plan, for one day or filed ahead — for a single date, a run of dates, or set to repeat on chosen weekdays (such as every Friday until June) with any days skipped: the way home, the name of another adult collecting if there is one, who asked and by what route, and a short note; if the center takes requests after its cutoff, each late request, whether the office approved or declined it, who decided, and a note from the office about a decline, which only staff see; for an early pickup, the time and a reason from a short fixed list (appointment, family, illness or other — never a description), and whether the child was called, collected, or nobody came.
- Adults a family names to collect some of their children (a grandparent or a sitter, say): their name, how they are related (from a fixed list), a phone number if the family gives one, which children, which days and until when, whether the center has approved them, and — if the family invites them — their email address and a login that shows them only that day’s pickup for those children. Carpools: which children ride together, on which days, and which parent accepted for each child. The center holds this data about people who are not its parents, and an adult’s details go only to the family who named them and to staff; the families in a carpool see its other children by first name and last initial.
- Drop-off sign-ins, where the center uses them: when each child was signed in, how (a sign scan, the typed sign code, the “I’m here” button, or staff from a room’s list, including a time staff entered later), who brought the child — a parent, a named adult, a member of staff, or a name staff typed in — and who recorded it, and any sign-in that was voided, with who voided it and a reason from a short fixed list.
- Where a center or an after-school 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 at an after-school site 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. The one-way PIN hashes from before the tablet asked for a phone number have been erased; an old kiosk code, which opens nothing, is kept until it is erased with the family’s other records.
- Expected days, where the center sets them for a part-time child: which weekdays the child comes, between which dates. A family reporting an absence gives the dates and, if they choose, a reason from a short fixed list (appointment, family, illness or other — never a description).
- Emergency contacts, where the center keeps them: people a family (or the office, from a paper form) lists to call when a parent can’t be reached — a name, how they are related (from a fixed list), one phone number, which children and in what order. No address, email or notes. Staff read them; nothing is ever sent to a contact, and a contact never collects a child.
- Enrollment forms, where a center uses them: the answers a family gives on the center’s form, the center’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). A date of birth or a physician only if the center asks for one, and then kept private: encrypted, shown only to staff given that permission, and every look recorded. The form never asks for a home address, a Social Security number or health details, and takes no uploads; the center may note that an immunization record was given to it, and when.
- 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, and an adult a family invited to collect, see 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.
- Custody orders the center records: the person named, or their account, the kind of order, 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. Where an order gives a parent set days, the pattern of those days — which weekdays, and whether it is every week or every other week — which is a family’s parenting-time arrangement and is treated as part of the order.
- The center’s calendar: the days the center is closed and the early closing days, with their times and a short note in the office’s own words (such as “Teacher training”), shown to staff and to the center’s parents in the app.
- The pickup record: which car checked in, when and how (a sign scan, the sign’s typed code, the “I’m here” button or a hangtag) — for the button, only whether that one tap was at the center, never where it was; which children were in it, who called, sent, held, released or held each child back, the reason a child could not come out, who cancelled what, and — when another adult collected — their name and a staff note of the ID they showed, never a whole ID number. When staff look a family up by name to check a car in, who looked and which families came back, but not the name typed. When a release was tapped on a staff device that had lost its connection, that it was done offline and entered later, and whether the office had to review it; until it is sent, the device itself keeps only ids and times, never a name.
- Display screens and call-outs: the name the center gives each paired screen (a curb or room display), when it paired and was last seen — a screen has no account; for a child whose family has opted out of directory information, a display name the screens show instead and whether to leave the child off the curb display; and each staff call-out (at most 80 characters, shown to staff and the screens the sender picks, never sent to a parent), kept with the pickup record.
- A reunification (an emergency release at another site, or a drill): the site and the reason an admin gave, each child’s status — not yet seen, present, missing or released, or, visible only to admins and with no detail or free text, hurt or with first responders — who marked it and when, and for each adult who asked for a child their name, the staff note of the photo ID they showed (never a whole ID number), who checked them in, which children they asked for and whether each was released or refused, and by whom.
- A roster import, whether your admin uploads it or we load it for you: the name of the file, the rows parsed out of it, and who uploaded it, kept as the record of what was imported and when — the rows and the file’s name for 30 days (clause 5). The file itself is not stored.
- Tuition, for a center that bills it in the app: each child’s tuition place (the rate group, the schedule, the days and the dates), the household’s paying parents and their shares, and the invoices, payments, credits, refunds, disputes and late-pickup fees as the center’s own Stripe account reports them, with the reason staff gave for waiving a late fee. The child’s name is copied into the center’s billing record; it is never sent to Stripe.
- An after-school program, whether a center runs it or it is independent: each child’s first and last name and, only if the program asks for it, a date of birth; the child’s guardians, how each is related, whether each may collect and gets notices, and who pays and their share; the answers a family gives on the program’s registration form, 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; each enrollment and place (the program, the term, week or days, the dates, and any waitlist place or move); the record of each program day — when a child was received, from class or at the door, 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); invoices and payments as for tuition, above; and, between a center and an independent program, which facts the center has granted the program and each parent’s consent to that, with when it was given or withdrawn.
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 notice does not name a child unless the center turns that on. By default it says “a child was released at 3:07 PM”, and the app shows who when it is opened.
- Messages between the center and families: the words of each message the center sends, who wrote it, which families it went to, on which channels, and whether each family has read it; a message set to go later (once or on chosen weekdays), with who set it, when it goes and who cancelled it; the center’s saved message templates; and each conversation a parent has with the center’s office — the words, which child it is about if they chose one, who replied and when. No attachments. A center’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 center, 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 center’s records never hold: license plates, whole card or bank numbers, advertising identifiers and third-party analytics. These are not settings we turned off. Nothing in Sunporch 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 center’s enrollment form, or the registration form of a program it runs, asks for one (above). Photos of children are built but switched off at every center for now, and when they are switched on, only with each family’s consent.
Health cards (allergies, dietary needs and a medical note), a medication log, daily reports and documents a family sends about a child are built too, and are switched off at every center for now. Before any of them is switched on, this policy will describe what it keeps.
Location is the one exception, and only where your center turns on the “I’m here” button and marks its grounds: when you tap the button, the app sends one reading of your phone’s location with that check-in. It is compared with the center’s grounds and dropped at once; only whether you were at the center (yes, no or unknown) is kept. The reading is never stored or logged, nothing is read in the background, and there is no column for where you were. Scanning the sign or typing its code sends no location at all.
3. Why we use it
- Center data: to run the center’s day with children. To sign each child in and out, put a car in the queue, show your staff which children that car is collecting, let them release each child at the door or check them out of a program, 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 center disables an account.
- Notification data: to tell a family about their own children’s day, on the channels they chose — a child signed in at drop-off, sent out or released, a car put in the line by hangtag or by staff, pickup paused and resumed, a pickup-day alert, a bus that has left, a child received or checked out by an after-school program, or not yet received by it, a change to a child’s way home, the evening-before reminder of a day the center is closed or closes early, a message or a reply from the center, an incident report, and the notice that a reunification has started — and to tell staff what their work needs: a center’s admins when a check-in needs the office or a room has stayed over its ratio, the office inbox when a family writes, and a teacher when a child in their room will be away or has a change for tomorrow (the evening digest). Nothing else.
- Website data: to answer you, and to keep the site standing up.
Center data is never used to market to anyone. We do not email parents about Sunporch. We email a parent because their center invited them to an account or a family invited them to collect its children, 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 or a reply from their center or a reunification notice, for the calendar reminder if they asked for it by email, to tell them an incident report about their child is ready to read, to ask for a field-trip permission slip, to invite them to fill in an enrollment form, to send a program’s bill or say a payment failed, and — unless they switch it off — to confirm that their child was released.
There is no clause here that quietly widens this with “legitimate interests”. If we ever want center data for something other than providing your center’s service, we will ask your center first and this page will say so.
4. Who sees it
Inside your center
Staff whose granted permission covers it, and — for the two screens in the next paragraph — every member of staff at the center. Permissions are granted one at a time, and a center can grant one for a limited time: see children, edit children, see parents, invite parents, manage staff, run pickup, clear custody holds, see custody orders, send messages to families, read and answer the parent inbox, work a reunification, work a program desk (only the programs they are assigned to), see private enrollment answers, manage the staff time record (everyone’s clock-in times; each member of staff always sees their own), see tuition places, invoices and payments, and run tuition billing, credits and refunds (which only an admin may grant), read incident reports, and record incident reports (someone who only records them reads only their own). Admins hold every one at their own center. Every other account starts with none.
Two things need no permission, because every member of staff at the center may need them: any room’s board — the children called for pickup, by first name and last initial, and that room’s class list with each child’s way home — and, during a reunification, any room’s roll call.
Two of them reach further than their names suggest. See custody orders lets a member of staff who is not an admin read the custody orders on file and a held child’s order — never for a child they are a party to, and only an admin can change an order. Read and answer the parent inbox lets them read the conversations parents have with the center’s office.
Your center’s district
If your center belongs to a school district that uses Sunporch, the district office’s people see what the district has been granted at its centers, and each center can see that list: counts and waits in the district’s reports (no names), the centers’ staff and their permissions, and — only if granted — the centers’ children or parents. A district can never run the pickup line, invite parents, change a child or read a custody order.
Inside LexPro
Our staff can manage a center — rename it, invite its first admin — without ever reading its children or parents. To read center data, we have to raise a time-boxed elevation with a written reason, or be added to the center as a member (the next paragraph). An elevation grants read access only, never write. It expires on its own or is ended early, the written reason is required, and the rows are never deleted.
Centers can ask us for the list of elevations raised against them.
A member of our support team may be added to a center’s account as a member — an admin, a teacher or a parent — only to help that center: to set something up with it, or to see what its people see while we work on a problem. They appear on the center’s member list like anyone else, their being added and what they do are recorded in the center’s history under their own name, and they are removed when the help is done. We never add someone to a center 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 center’s payments, 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 pickup notice names no child unless the center chose that; a message the center writes to families goes to the push, text and email providers as the center wrote it. Stripe receives the center’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 a center’s own payments send Stripe no child or family data (family payments for tuition are below). We do not use Stripe Tax. We will name any new provider on this page before it is used, and tell centers before we change one.
Family payments for tuition. When a center bills families in the app — its tuition, or a program it runs — the payments run on the center’s own Stripe account: the center is the merchant, and Stripe is its payment processor. To bill a family we send that account the paying parent’s name and email, the invoice lines (the rate group or 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 center’s, not ours. The center accepts Stripe’s own terms when it connects the account, 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 center’s payment processor, under the center’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 center bills that family in the app, and we take the platform fee the terms describe. A center 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 Sunporch 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; we switch them on when a district asks. 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. If your center loads its roster from Clever, ClassLink or its own student information system (OneRoster), we read its children, parents and classes with a credential the center gives us, and send it nothing but our requests.
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
Center data stays for as long as your center uses Sunporch, 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 parent or a staff member hides them everywhere in the product and, for a parent or a member of staff, ends their sessions. It does not erase the afternoons they were part of, because the pickup 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 center can do it. Erasing their name and details out of the record is done in place — the rows stay, so the center’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 center’s admins can read: when your center asks, and we approve and run it; and by a retention job that runs every night, on this schedule:
- A child removed from the center, a family removed from the center, and a custody order lifted or deleted: one year after the removal.
- An adult a family named to collect, once removed or revoked, and a carpool once closed: one year.
- An emergency contact, once removed: one year.
- An enrollment form: a private answer 30 days after the child leaves; a form the center never accepted, 90 days after it last changed; an accepted form with the child’s record.
- An account its owner deleted (a parent’s, or an adult’s a family invited): one year after the deletion, together with what each center held about that family.
- A member of staff removed from the center, and a district office’s person removed: 90 days.
- A helper without a login, once removed or past their last day: 90 days.
- Each entry of the staff clock-in record: three years, after which who it was, who recorded it, its note and its site check are erased.
- A staff certification: erased with the member of staff (90 days after they are removed) or with the center or program; the credential’s typed name and where the paper is kept or its number are cleared.
- The detail of each pickup day — who collected, the ID-check notes, the notes and names on changes, the time and reason of an early pickup, staff call-outs — and of each reunification: two years.
- 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: at a center, two years after the incident; at an after-school program, when the program’s record of the child is erased; and always with the child, whichever comes first. That a report existed, its kind and its times are kept.
- The names typed on field-trip permission slips: two years after the trip (at an after-school program that sets its own period for its day records, that period instead), and always with the child or, at a center, with the family. The answers, the head count and the trip itself are kept; a trip’s name, destination and details are erased with the center or the program.
- The words of the center’s messages and of each conversation with the office: two years after it was sent, or after its last message.
- The rows parsed out of a roster upload, and the file’s name: 30 days after it was imported or expired.
- Billing records — invoices, payments, credits, refunds and disputes, with their reasons and references: seven years.
- An after-school program’s day records — the names, notes and events of each program day: for the period the program sets, between one and seven years, and two years if it sets none.
- 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.
A legal hold your center places stops the erasure of what it covers until the center releases it.
Contact-form messages are anonymized two years after they were sent.
When a center closes its account, its data is erased when the center 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 center or a program to keep incident reports for longer than the schedule above. The schedule is the same everywhere, and we do not check anyone’s licensing rules for them. A center or program whose rules ask for longer places a legal hold on the children concerned, which keeps their reports, with everything else about them, 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, a parenting-time schedule, 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 center 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 detail, and are erased after two years. 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 center does with Sunporch needs one.
We receive information about a child from the center and from the child’s own family, never from the child, and we use it only to provide that center’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 Sunporch, and every record about a child is entered by the center’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 center holds about you and your children), and delete your account.
For anything else, and if you are a member of staff, go to your center. The center controls the data and we act on its instructions, so the center is the one that can answer for it — and we help them answer.
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.
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.
- The pickup log is append-only and the database rejects any attempt to change or delete a line of it.
If a security breach exposes a center’s data, we tell the affected centers 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.
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 center admins about it, and the “Last updated” line at the top of this page is changed with it.
If LexPro or Sunporch 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.