How we protect your school's data

A PTO site holds children's names, their classes and their families' home addresses. This page explains, in plain terms, what we do with that and what we've built to keep it safe.

Who owns what

Your PTO Owns its information: its families, events, sign-ups, orders, pages and news. We hold it only so your site works.
Each family Controls its own listing. A family decides what other families can see, and can change that whenever they like. A family's choice always wins over anything the PTO sets.
Red Night Owns the Hallknit software. We don't own your data, we don't sell it, we don't show ads, and we don't use it to train AI models.

If your PTO stops using Hallknit, we give your board a copy of its information and then delete it from Hallknit within 60 days. Payment records stay in your PTO's own Stripe account, which you keep.

What we never store

  • Social Security numbers
  • Student birthdays
  • Photos of students
  • Driver's licenses or other ID numbers
  • Background check reports. If your school requires checks, we store only whether a volunteer is cleared and until when.
  • Card numbers. Families pay on Stripe's page and we never see the card.

Keeping PTOs apart

Many PTOs use the same Hallknit service, so every record is labeled with the PTO it belongs to. The database checks that label, and the person's role in that PTO, every time anything is read or changed. This happens in the database itself, so a mistake in a screen can't show one school's families to another.

Before any change goes live, automated tests try every database rule as eight kinds of visitor: someone not signed in, a parent waiting for approval, an approved parent, a volunteer coordinator, the school office, a treasurer, a PTO admin, and a parent from a different school. If any of them can see or change something they shouldn't, the change doesn't ship.

Board members get only what their job needs. A treasurer sees orders and refunds. A volunteer coordinator sees the people who signed up for their events. The school office marks volunteers as cleared and sees nothing else.

The directory

  • A family is listed when it chooses to be, showing only the details it picks. A PTO can also list families from its own records, but each adult gets an email first with what will show and a "Don't list us" button, and a family's own choice always wins over the PTO's.
  • Only families the PTO has approved can search it. A new family waits until a board member checks them against the class list.
  • Every search goes through one database function that returns only the details each family chose to share. There's no way around it to the raw records.
  • The class list the school gives the PTO is used only to check new families. It is never shown to parents.

Signing in

  • Families sign in with a 6-digit code sent to their email. Nobody can make an account for an address they can't read.
  • A PTO can require its admins, treasurer and directory admin, the people who see every family or move money, to also enter a code from an authenticator app. Until they do, their board pages stay locked, even in the database.
  • Passwords are optional, need at least 10 characters, and can only be set after signing in with a code.
  • The sign-in cookie can't be read by scripts on the page and is only sent over HTTPS. Other sites can't embed Hallknit pages to trick someone into clicking.
  • Buttons in our emails never act on their own. They open a page where you press a button to confirm, so an email scanner or a forwarded message can't sign someone up or cancel a shift.

The record of who did what

Hallknit keeps a permanent record of the actions that matter. Each entry says who did it (their account and email), what they did, when, and whether they did it themselves or through an AI assistant they connected. The record includes:

  • Approving a family, or asking them a question first
  • Giving someone a board role, changing it, or removing it
  • Downloading or printing lists: the directory, classes, orders, events
  • Importing families, classes, events or volunteer clearances
  • Sending email to families
  • Refunds and changes to how the PTO gets paid
  • Publishing, changing or deleting events, pages and news
  • Turning on two-step sign-in, or resetting someone's

Board members can't edit or delete these entries. If someone's account is deleted, the record still shows who they were. Your board can ask us for your PTO's record at any time.

We don't record each time a family looks something up in the directory. We do record every download and print of it.

Bots and scraping

  • The sign-in page and the forms on this website use Cloudflare Turnstile, which checks that a person is there without making them solve puzzles.
  • Requests for sign-in codes are rate limited. Asking for a new code cancels the old one.
  • Nothing about families is public. Search engines and scrapers can't reach the directory, because it needs both a signed-in account and the PTO's approval.
  • Parents can't download the directory. They can search it one family at a time, and the printed version is marked for personal use.
  • Each household can send at most 10 invitations a day, so the site can't be used to spam people.
  • The public events page shows only what the board chose to make public. Who signed up for what stays behind sign-in.

Payments

Families pay on Stripe's checkout page, and the money goes to your PTO's own Stripe account. An order is marked paid only when Stripe sends a signed message confirming it, and each message is processed once. Payment keys live only on our servers.

Where it runs

  • The database and sign-in run on Supabase, in the United States (Ohio).
  • The website, files and email run on Cloudflare.
  • Everything travels over HTTPS, and the database is encrypted when stored.
  • Supabase backs up the database every day and keeps each backup for 7 days, encrypted and in the United States. If something goes wrong, we can restore any of those days.
  • Passwords for our services and payment keys are kept as encrypted secrets, never in our code.
  • Only the Red Night staff who run Hallknit can reach the live database, and only to fix a problem or answer a request from your PTO.

AI

Every AI feature is off until a PTO admin turns it on, and each one can be turned off again at any time. Turning one on or off is recorded with who did it and when.

Teacher-name suggestions

When it's on and a board member types a teacher's name, Hallknit can suggest which person on the staff list they meant, using Clef, an AI model Cloudflare runs on its own network. It receives only staff names and titles, the typed name, and the class's grade. Never a family, a child, or an email address.

  • Cloudflare lists Clef as zero data retention: the request and the answer are not kept once the answer is sent.
  • Cloudflare doesn't use what Clef processes to train AI models.
  • The only ways a copy could be kept are a logging gateway or our own logs. We use neither for these requests.
  • Nothing is linked until a board member confirms the suggestion.

Message checking

When it's on, the name and message someone leaves on a fundraiser or a child's page go to Clef to check they're fine for a school page. Never the giver's email, their real name, the amount, or anything about the child. Clef keeps nothing once it has answered, and these requests aren't logged.

AI assistants you connect

Families and board members can connect an AI assistant app to their Hallknit account. The assistant can see and do only what that person can on the site. What it sees, which may include other families' directory listings, is then handled under the assistant company's own terms, not ours.

  • Changes made through an assistant are recorded as made that way.
  • Risky actions, like emailing every family or changing board roles, need a preview first and a code from that preview. The code works for 15 minutes, for exactly those details.
  • A few smaller changes, like posting news that isn't urgent or publishing an event, happen without a preview.
  • When a PTO turns on two-step sign-in for its admins, assistants get no admin tools at all.
  • To disconnect an assistant, remove Hallknit from the assistant app.

If something goes wrong

If we find that someone saw information they shouldn't have, we'll tell your PTO's admins within 72 hours of confirming it, explain what happened, and help you tell the families affected.

Found a security problem? Please tell us. Don't look at or keep anyone's information while you check. We'll reply within two business days.