Privacy policy

We collect only what is needed to authenticate you, render your scenes, bill correctly, and make Kodisc better. We do not sell your data. We do not train foundation models on your prompts or rendered videos.

Just a kid in his dorm at UMich.

Account data — email, display name, hashed password or OAuth identity, and the sessions tied to your logins. Managed by better-auth.

Prompts and projects — the text prompts you submit, the generated Manim code, the rendered videos, and any uploaded reference images or attachments. Stored on Supabase and Postgres for the life of the project.

Usage telemetry — page views, feature use, render durations, error traces. Aggregated and scoped to your account so we can debug and improve product quality.

Billing data — subscription status, credit balance, and the minimum payment metadata Stripe returns to us (card last four, brand, country). Full card numbers never touch our servers.

Device and network data — IP address, user agent, and cookies needed to keep you logged in and block abuse.

Running the product — authenticating you, rendering your scenes, delivering finished videos, billing what you owe, and letting you log back in tomorrow.

Product improvement — diagnosing failed renders, tuning latency, and spotting feature gaps. Always on aggregated or pseudonymised data unless we are debugging a specific ticket you opened.

Communication — transactional email (receipts, render failures, security alerts) and occasional product updates. You can opt out of the product updates; the transactional ones are part of running your account.

Trust and safety — detecting abusive prompts, rate-limiting attacks, and enforcing our terms. We review flagged content by hand when automation is not enough.

Generating Manim code is done by large language models hosted by OpenAI and Anthropic. When you submit a prompt, we forward the prompt (and any attached context) to the provider that best fits the task, receive code back, and render it on our infrastructure.

Both providers contractually do not train their public foundation models on traffic we send through their APIs. We add no additional opt-in to training on your side.

Projects, prompts, and rendered videos live for as long as your account is active. Deleting a project removes it from listings immediately and purges it from storage within thirty days.

Closing your account triggers a full delete of prompts, renders, and project data within thirty days. We keep minimum billing records (invoices, tax documents) for the period required by law — usually seven years.

Telemetry and error traces are kept for ninety days, then aggregated or discarded.

You can access, correct, export, or delete your personal data at any time. Settings handle most of it; anything we cannot expose through the UI, we handle manually within thirty days of a privacy@kodisc.com request.

If you are in the EU, UK, or California, you have the corresponding rights under GDPR and CCPA — including the right to object to certain processing and to lodge a complaint with your supervisory authority. We honour these rights for every user, regardless of location, because doing otherwise is tacky.

Essential cookies keep you signed in, protect against CSRF, and remember your theme choice. These are set the moment you load the app.

We do not set advertising or cross-site tracking cookies. Analytics are first-party and do not fingerprint you.

All traffic is served over HTTPS. Secrets, tokens, and passwords are stored hashed or encrypted at rest. Access to production data is limited to a small set of engineers and audited.

No system is perfect. If you spot a vulnerability, email dev@kodisc.com and we will respond within one business day.

We will update this policy as the product grows. Material changes are announced by email and in-product banner at least fourteen days before they take effect. The version and last-updated date at the top always reflect the live version.

Security reports — dev@kodisc.com.

Everything else — hello@kodisc.com.