Safety & privacy

Trust is part of the product.

Keeping accounts, student data, and payments safe was part of the plan from day one. It wasn't added later.

{}Course player● Protected
◧Parent dashboard● Protected
◈Payments● Protected
✓Runs in the browser, nothing to install
✓Payments handled by Stripe
✓Every support visit is logged
✓No student personal info in our logs
// product safeguards

Safety built into every part.

We protect every part of the site, from accounts and billing to the places you code.

⊟

Everyone sees only their part

Students, parents, and our team each have separate areas. Each person sees only what's meant for them.

⚿

Secure logins

Logins are checked on our servers. Password resets and sign-in codes are limited, so no one can keep guessing.

◈

Safe payments

Stripe handles every payment. We never store card numbers.

▤

Protected progress

Progress, projects, and badges are tied to each account. Only that account can see them.

{}

Safe places to code

Code runs in a closed-off space in the browser. Nothing gets installed on your computer.

⚙

Careful support access

When our team helps with an account, every visit is checked and logged.

// data protection

What we keep, and what we don't.

We only keep what we need to run accounts, teach courses, and handle billing. Nothing more.

01

Account info

Parent names and emails, the students on the account, and settings like the plan.

02

Learning records

Student profiles, progress, and certificates.

03

Projects and code

The code students write and run, so we can save progress and give feedback.

04

Billing status

The plan and whether it's paid. Stripe keeps the card details, never us.

// admin & support access

Our team's access is careful and logged.

Our team only opens an account to help with it. Every visit is checked, logged, and ended cleanly.

⚿

Locked-down team access

Our team's tools check every sign-in on the server. Old ways in are turned off.

◉

Every visit is logged

We record who opened an account, which one, and when.

↩

A clean exit

When a support visit ends, our team leaves the account and its temporary access is cleared.

// passwords and sign-in codes

Sign-in that stays safe.

✓Password reset links are random and expire
✓Reset links and sign-in codes are scrambled before we store them
✓Sign-in emails are limited, so no one can flood an inbox
✓Reset requests never reveal whether an account exists
// logs and analytics

What never ends up in a log.

✓No student personal info, sign-in links and codes, or full emails in our logs
✓Marketing analytics only run on public pages and checkout
✓Dashboards and the course player have no ad tracking
✓Sign-in pages have no tracking at all
// good habits

A few habits keep your account safe.

They take a minute, and they matter most.

01

Use a strong, unique password for the parent account.

02

Keep the parent login separate from student logins.

03

Check progress and activity in the dashboard.

04

Keep your browser up to date, especially on shared computers.

05

Contact support if something on the account looks wrong.

Report a security concern.

See something strange on an account, or think you found a security bug? Tell us. We look into it fast.

● Safety reports acknowledged in 2 business days● Support replies within 1 business day