Security & privacy

How we protect aschool’s data.

Only what Carline does today. Where something isn’t settled yet, this page says so.


Security & privacy

Built in

  1. Encrypted in transit

    Outside development, the Carline API answers a plain-HTTP request only with a redirect to HTTPS, and its sign-in cookie is marked secure, so the cookie only travels over an encrypted connection.

  2. Secrets stored as hashes

    Passwords are stored only as salted hashes. Invitation links, password-reset links, and the pairing codes and device tokens of school display screens are stored only as hashes too, so a copy of the database doesn’t hand anyone a working link.

  3. A record that can’t be rewritten

    Every step of the pickup line, from a check-in to a child handed over, is written to an append-only record. The database itself refuses to change or delete those rows, and the same goes for the configuration history and the log of who opened a child’s record. The one exception is an approved erasure, which removes names in place.

  4. Least privilege

    Staff get only the permissions their school gives them, checked against the database on every request, so taking one away works at once. A disabled account stops working on its next request, even on a phone that is already signed in. Our own platform accounts manage schools; they can read a school’s children or families only through a time-limited access with a recorded reason, and never to change anything.

  5. Sign-in protection

    Five wrong passwords lock an account for 15 minutes, sign-in attempts are rate-limited, and an unknown email takes as long to answer as a wrong password, so the answer doesn’t reveal who has an account.

  6. Retention and erasure

    A nightly retention job erases what is no longer needed: deleted records after a year, a member of staff 90 days after leaving, and pickup detail after two years. A school can ask us to erase a child, a family or the whole school; we approve and run it, and a certificate is issued. A legal hold stops both.

Security & privacy

Where things stand

  1. Where the data is stored

    In the United States, on Google Cloud in us-central1 (Iowa).

  2. Encryption at rest

    The database, its backups and stored files are encrypted at rest by Google Cloud.

  3. SOC 2

    Not yet. We have no SOC 2 report or other security certification today.

  4. Student Privacy Pledge and the NDPA

    Not signed. We have not signed the Student Privacy Pledge or the National Data Privacy Agreement.

Report a security problem

If you think you have found a vulnerability, email us the details. Please don’t test against a school’s real data.

Email hello@lexpro.app

Contact us