Your school's records are your school's records.

Cubby is a device and property management platform for K-8 schools, run by Cubby HQ and available at cubbyhq.app. This policy explains what we hold, why we hold it, and what happens to it. Questions go to info@cubbyhq.app, and a person answers them.

Cubby holds three kinds of records, all entered by your school's staff.

• Staff accounts. Name, work email, and role for the people your school signs up. That is what a login needs, and that is all it takes.
• Student and family records. The roster your school enters or imports: student name, grade, homeroom, and where your school chooses to add them, a student email, a guardian's name and contact details, and a student ID from your information system. Plus the working records built on top: which device a student holds, its condition, incidents, and billing notices.
• Inventory and money. Devices, serial numbers, purchase details, stock, and your subscription. Payments run through Stripe. Card numbers go to Stripe and never touch Cubby's servers or its database.

There are no student accounts and no student login. Cubby collects nothing from children directly: every student record is entered by an adult on your school's staff, about a device program the school already runs. This is how we approach the Children's Online Privacy Protection Act, and it is also just how the product is built.

We use your school's records to run Cubby for your school, and for nothing else. The emails we send are the ones the product exists to send: overdue notices, billing notices, incident alerts, digests your staff turn on, receipts, and account messages. We do not sell records, rent them, or share them with advertisers or data brokers. There is no advertising anywhere in Cubby.

Cubby includes an assistant that answers questions from your school's own records, like how many devices are still out. It reads only the school of the person asking, it can read but never change records, and it is built not to keep memories about individual students. Your school's records are not used to train AI models, ours or anyone else's.

Student records belong to your school and stay under your school's direction. We act only on your school's instructions, use education records solely to provide Cubby to your school, and never disclose them except as this policy says. When your school asks us to correct, export, or remove records, we do it.

A small set of services run Cubby, and each one sees only what its job requires.

• Base44 hosts the application and its database.
• Stripe processes subscription payments and holds the card details we never see.
• Google handles sign-in only for staff who choose to sign in with Google.

That is the whole list. If it ever grows, this page changes first.

We keep your school's records for as long as your school uses Cubby. If your subscription ends, the account goes read-only: your records stay visible and exportable, and nothing is deleted out from under you. Any screen with a table can export it as a spreadsheet at any time.

When your school removes itself from Cubby, records are archived out of active use and the audit trail records that it happened. For permanent deletion of archived records, email info@cubbyhq.app from an administrator account and we will complete it and confirm in writing.

Every record is scoped to your school, traffic is encrypted in transit, and staff see only what their role allows. The full picture, including how to report a vulnerability, lives on the security page.

If this policy changes in a way that matters, we email the administrators of every school before the change takes effect. The date at the top always tells you when it last moved. For anything at all: info@cubbyhq.app.