Privacy & Data
Security Practices
CyberWolfAI LLC · Version 0.9 (pre-launch draft) · Last updated 2026-07-28
In plain words
Good security is mostly good habits. This page describes the practices we follow when building and running Little Lobos Academy.
We describe what we do — not badges we have earned. We hold no formal security certifications (such as SOC 2 or ISO 27001), and we will not claim any until an independent review says so.
Collect less, protect more
Our first practice is simply not collecting data we do not need. We ask for a parent email, student first names, and learning activity — not birthdates, addresses, or full names of children.
When a feature can work without storing something, we build it that way.
Parents hold the keys
Every account is created and managed by a parent. Children never sign up, never manage settings, and never see billing or purchases.
This design means a child cannot accidentally share information or change protections — the adult is always in control.
Layered technical protections
Encrypted HTTPS connections protect data in transit. Row-level security in the database ensures each family can only reach its own records.
The platform runs on established cloud providers (Vercel and Supabase), so infrastructure security is handled by teams who do it full time.
Careful with uploads and audio
Documents parents upload — receipts, curriculum files — are stored under the same access rules as the rest of your family's data.
Cached audio narration exists so lessons load quickly; it is treated as platform content tied to your account, not shared elsewhere.
A private start
Little Lobos Academy is currently a private, single-family deployment. Before opening public family accounts, we plan to review and harden these practices for a larger audience.
Growing carefully is itself a security practice.
Honest limits
We are a small company, and we would rather be candid than impressive. We do not claim compliance with any security standard, and formal third-party review is pending.
If a practice on this page ever changes, we will update this document and its version number.