How we protect a school's records.

Every record in Cubby carries its school, and every query is scoped to it. A person signed in at one school cannot list, search, or read another school's students, devices, or incidents. District users see a rollup across their own district's schools and nothing beyond it. This is the oldest rule in the codebase and the one we test hardest.

• Staff sign in with a work email and password or with Google. Those are the only two doors. Passwords are handled by our authentication platform and are never stored in Cubby’s own tables.
• Students never sign in. There is no student login to secure because there is no student login.
• Three roles gate every screen: superintendent, school admin, and teacher. A teacher sees their own homeroom’s assignments, not the school’s finances.

Checkout happens on Stripe's hosted payment page and the customer portal. Card numbers go directly to Stripe. They never pass through Cubby's servers and are never stored in Cubby's database. What we keep is what a receipt needs: the plan, the status, and Stripe's reference IDs.

• All traffic runs over HTTPS. There is no unencrypted path to Cubby.
• Cubby runs on managed cloud infrastructure through Base44, which operates the underlying hosting, storage, and physical security.
• The activity log is append-only. It is never edited and never deleted, including when a school is removed. What happened is always on the record.
• Removing a school archives its records rather than destroying them, so a mistaken deletion cannot vaporize a device program. Permanent deletion happens on written request, as the privacy policy describes.

The assistant can read records and can never write them. It sees only the school of the signed-in person asking, it is built not to keep memories about individual students, and school records are not used to train models. It answers questions; it does not touch data.

We are a young company and we will not decorate this page. We do not yet hold a SOC 2 report or an ISO 27001 certification. If your district's procurement process needs security documentation, questionnaires answered, or a data processing agreement signed, email administrator@cubbyhq.app and we will work through it with you directly.

If you find a vulnerability, tell us at administrator@cubbyhq.app and give us a reasonable window to fix it before talking about it publicly. We answer fast, we will not take legal action against good-faith research, and if a problem ever puts a school's records at risk, we notify that school without undue delay and say plainly what happened.

What we hold and why is on the privacy page.