Privacy Policy
Last updated · August 23, 2026
Tchaku is local-first by design — your decks live on your machine, not ours. This policy is short because there genuinely isn't much for us to collect, and it spells out exactly what reaches us when you use the cloud-backed parts: live sessions, sharing, AI and billing.
Our approach to privacy
Tchaku is built local-first, and our privacy posture follows from that: we collect as little as we can, and most of what Tchaku does never touches our servers at all. This policy explains what is — and isn’t — collected when you use the Tchaku app and this website.
What stays on your device
Your decks (.tch files on desktop, including legacy .animprodecks; your browser’s own storage on the web), editor settings and theme preference are stored locally on your device. None of it is transmitted to us except through the explicit actions described below — publishing a share link, running a live session, uploading a recording, or making an AI request. If you delete the app or those files, that local data is gone. We hold no copy of your decks apart from what you have explicitly published: a share link keeps its snapshot until you ask us to remove it, and shared recordings that nobody has watched are deleted automatically after 90 days.
Your account
The desktop editor works without an account. Signing in — required on the web app, and on desktop for AI, sharing and saved session history — creates an account holding your email, sign-in credentials, display name, plan and AI credit balance. Audience members joining a live session never need an account.
Data during live sessions
When you run a live-audience slide, a session is created on our real-time infrastructure (currently Supabase). During an active session we process:
- a short session code;
- the question or prompt shown on the slide;
- the responses your audience submits from their browsers, along with the nickname each participant picks when joining.
Audience members join anonymously — no account, no sign-in; a nickname is all we ask for. Ending a session closes it, and sessions expire so they can no longer be joined. If you present while signed in, a results snapshot — including participant nicknames and answers — is saved to your account, and you can review, export or delete it at any time from your session history. Raw session records may be retained on our infrastructure after a session ends; you can request deletion at any time. Please don’t use live sessions to collect sensitive personal information.
AI generation
Tchaku’s AI features are credit-metered and run through our servers — you never supply or manage an API key. When you make an AI request, the content you submit (your prompt, and any deck content, images or recording audio the feature uses) is sent to a third-party model provider using Tchaku’s own keys: currently Anthropic for slide generation, OpenAI for images, narration and transcription, and Meshy for 3D models. Each provider processes it under its own privacy policy.
To meter credits, prevent abuse and monitor quality and cost, our servers keep a log of each AI request and its result. These logs are access-restricted, are not used to train models, and you can request deletion of your AI logs at any time. AI features require signing in.
This website
This marketing website stores one thing in your browser: your light/dark theme preference, in localStorage. That is a functional preference, not a tracking identifier. The web app at app.tchaku.com additionally keeps your sign-in session and your decks in the browser’s own storage — that is where your decks live, which is the point. None of our pages set cookies or load third-party trackers, which is why you don’t see a cookie banner. If we add privacy-respecting, aggregate analytics in the future we will update this policy first. We do not sell personal information.
Crash reports
The Tchaku apps send crash reports — the error and technical details of what went wrong — to Sentry so we can fix bugs. Crash reporting is on by default; you can turn it off at any time in the app’s settings.
Payments
Payments are processed by Stripe. Stripe collects and processes your payment information under its own privacy policy. We receive only what we need to provide your plan — such as a confirmation that payment succeeded and a billing email — and never your full card number.
Service providers we rely on
We keep our list of processors short, and each one handles data only under its own privacy policy:
- Supabase — database, accounts, real-time infrastructure for live sessions, and storage for content you publish.
- Anthropic / OpenAI / Meshy— AI model providers, called from our servers with Tchaku’s own keys when you use AI features.
- Stripe — payment processing.
- Cloudflare — hosts this website and the web app, and stores shared recordings and app downloads.
- Sentry — crash reports, if you leave crash reporting on.
We share only what each provider needs to do its job.
Your rights
Because Tchaku stores your decks and settings on your own device, you are in direct control of that data — you can view it, copy it or delete it at any time. For the data we do hold — your account, billing records, saved session results, published share links and AI request logs — you can delete saved session results directly in the app, and you may request access to or deletion of anything else by emailing us. We will respond within a reasonable time and as required by applicable law.
Children's privacy
Tchaku is intended for a general, professional audience and is not directed to children under 13 (or the minimum age in your jurisdiction). We do not knowingly collect personal information from children.
Changes to this policy
We may update this policy as Tchaku evolves. Material changes will be reflected in the “last updated” date above and, where appropriate, surfaced in-app or on this website.
Contact
Questions about privacy, or a data request? Email us at hello@tchaku.com.