Privacy & compliance

MinakiLearn is a free, single-page learning site. This page is written for parents, teachers, and district IT — the whole story on one screen.

At a glance

Accounts: None. There is no sign-up, no login, no email required.
Data collected: None sent to a server by default. All progress lives in localStorage on the device.
What leaves the device: Nothing, unless an adult opens the feedback page and types a message. Kids' widgets send no free text.
Third-party scripts: None. No analytics, no ads, no CDN, no trackers, no social embeds.
Cookies: None set by MinakiLearn.
Ads: None. Ever.
Cost: Free.
Accessibility target: WCAG 2.1 AA.
Standards: Skills tagged with Common Core (CCSS) codes — the full list is below.

What data exists, and where it lives

Per-kid progress (on the device)

When a child answers a problem, the browser stores the outcome in localStorage. That includes: the skill practiced, whether the answer was correct, the difficulty rung, a timestamp for the honest attendance calendar, and a running coin count. Data is scoped to a locally-created profile name (which the parent types in — no email, no last name required).

Nothing about this data is sent anywhere. Clearing the browser's storage deletes everything.

Optional adult feedback (leaves the device)

Two pages let an adult send a message to the developer:

The kid feedback flag on each game — tap-only, no free text. Sends a small structured payload: which game, mood, and up to six reason chips (like "too easy" or "broken"). No name, no email, no message body.
The tester feedback page at tester.html — an adult-only free-text form. The banner warns testers not to include kids' names or personal details. Free text is capped server-side at 1,000 characters per field.

Both routes go to a single endpoint that appends to a private log. No IP address, user agent, cookies, or session identifiers are attached to the payload. The endpoint has no read API — only write.

Homeschool records (on the device)

Parents can generate a printable portfolio (PDF) from the parent dashboard. The data source is the same on-device progress log. Nothing is uploaded to generate the PDF; the print dialog is the browser's own.

Compliance posture

COPPA (US, children under 13). Because no personal information is collected — no name, email, geolocation, contacts, or persistent identifier tied to a person — the site does not trigger COPPA's collection-and-consent regime. The kid feedback widget is designed to be non-textual (tap-only) so a child cannot submit personal information through it.

FERPA (US, education records). MinakiLearn does not host education records. If a school uses MinakiLearn, the child's progress record lives on the child's device only; there is nothing for the site to disclose because it holds nothing.

GDPR (EU). No personal data is processed by MinakiLearn as a controller. On-device storage is under the user's control; there is no transfer or third-party sharing to notify or consent for.

Ad tech. None. No SDKs, no tracking pixels, no third-party JS.

What districts usually ask for. Data flow diagram: browser ↔ static files. That's it. If your student data privacy policy asks about DPAs, subprocessors, or breach notification, the honest answer is that MinakiLearn has no student data to breach.

The site targets WCAG 2.1 AA. Concrete measures:

Contrast ratios validated at deploy time — every UI color pair is checked ≥ 4.5:1.
Every interactive element has a name (aria-label or visible text). Every image has alt text.
Keyboard-navigable — every game responds to arrow keys or WASD; every button has a visible focus ring.
44 × 44 minimum tap-target sizes on kid-facing controls; on-screen game controls are larger.
Respects prefers-reduced-motion — screen shake, particle bursts, and non-essential animation are skipped when the OS setting is on.
No auto-playing audio. No flashing content.

Reports and fixes are welcome via the tester feedback form.

Standards covered

Every skill in the app carries one or more CCSS codes. The list below is generated from the same file that governs the games at runtime — it can't drift.

List reflects the current build. Codes are the anchors used by curriculum sites — search "2.OA.B.2" or "RF.2.3" against your state's frameworks to map to state standards.

Questions

Send a message via the tester feedback form. It's the same channel adults use to report bugs; the developer reads it. There is no support email published on this page by design — email inboxes get scraped and there is no support team to route around.