Sign in

Privacy Policy

Effective May 18, 2026 · Version policy_v1

Didactic is a personal AI tutoring service that you, the parent, use on behalf of your children. This policy explains exactly what data we collect, where it goes, and how to remove it. Plain language; no dark patterns.

Who we are

Didactic is operated by an independent developer. Contact: vlukereddy@gmail.com.

What we collect

About you, the parent:

About each student you add:

We don't collect device identifiers, IP addresses (beyond what your browser sends with each request, which we don't store), location, contacts, photos, or anything from any other app.

How we use it

We do not use your or your child's data for advertising. We do not sell data. We have no analytics SDKs.

Third parties

We use two third-party services and no others:

Where data is stored

All data is stored on Cloudflare's infrastructure. Cloudflare encrypts data at rest and in transit. We use industry-standard hashing for passwords and authentication tokens — we never store either in cleartext.

How long we keep it

You can also delete your entire account at any time, which removes all data immediately.

Children under 13 (COPPA)

You are the account holder. When you create an account or add a student, you affirm that you are the parent or legal guardian and consent on the student's behalf to the collection and processing described in this policy. We record the timestamp and the version of this policy you accepted.

You can review or delete any student's data at any time. You can revoke consent for a specific student by deleting them from your account, or revoke consent for the entire account by deleting your account (Settings → Delete account). We do not knowingly collect data from anyone under 13 without parental consent.

Your choices

Cookies

We set one cookie: tutor_session, a signed session token used only to keep you signed in on the website. It is HttpOnly, Secure, and SameSite=Strict. We do not use any tracking, advertising, or analytics cookies.

Security

Passwords are stored as PBKDF2-SHA256 hashes with 100,000 iterations and a random per-user salt. OAuth and MCP tokens are stored only as SHA-256 hashes with a server-side pepper. We sign session cookies with HMAC and verify them with constant-time comparison. The platform runs over HTTPS only.

Changes to this policy

If we make material changes, we'll update the version at the top and notify you at next sign-in. Continued use after a change means you accept the updated policy.

Contact

Questions, complaints, or requests: vlukereddy@gmail.com.