Privacy Policy

The short version

• Opening, browsing and reviewing a deck involves no account, no upload and no tracking. Your file is parsed locally with WebAssembly.
• Review progress is stored in your browser's IndexedDB and never leaves your device.
• We do not run analytics, advertising or third-party tracking scripts anywhere on this site.
• A GitHub account is used only if you choose to submit a deck for sharing, and only to identify you and notify you of the review result.

What stays on your device

When you open an .apkg or .colpkg file, the archive is unzipped and its SQLite database is read entirely inside your browser tab using WebAssembly. No card content, media file or file name is transmitted to us or to anyone else.

Your review progress — which cards you have seen, their scheduling state and your ratings — is written to IndexedDB, a storage area belonging to this browser on this device. It is never uploaded, and it is removed when you clear your browser data for this site.

Because nothing is stored on a server, we cannot restore your progress for you, and we cannot see it either.

What we collect when you only browse

Nothing that identifies you. We do not use analytics, advertising, fingerprinting or third-party trackers.

Our hosting providers — Cloudflare, which fronts the site, and Vercel, which serves the static files — do receive the standard technical data any web request carries, such as IP address, user agent and requested URL, and may retain it in their own logs under their own policies. We do not augment those logs or combine them with anything else.

We set no cookies for visitors who only browse or review decks.

What we collect if you submit a deck

Sharing a deck is optional and separate from the reviewer. If you choose to submit one, you sign in with GitHub. We request read-only access to your basic profile — we never ask for, and never receive, write access to your repositories.

• Your GitHub username, avatar URL and profile URL.
• The deck information you type into the form: name, download link, summary, and any optional fields such as cover image URL, tags, author name and author link.
• The time of submission and the submission ticket number.

Your submission is opened as a public issue in our submissions repository on GitHub, and you are mentioned in it by username. That means the deck information you enter — including your GitHub username — is publicly visible. Please do not include personal information you would rather not publish.

The only cookie we set is a session cookie after you sign in. It is HttpOnly, Secure, SameSite=Lax, scoped to this site's path, and it stores nothing but your session. Signing out removes it.

We do not ask for, and do not want, your email address: review notifications are delivered by GitHub itself, to whatever address your GitHub account already uses.

Why we use GitHub for submissions

Running our own account system would mean storing passwords or third-party credentials — a liability for a small site like this. GitHub already solves identity and notification, and by asking for read-only profile access we keep the blast radius of any mistake as small as possible.

Your choices

• Do not submit a deck — browsing and reviewing never requires an account.
• Sign out at any time; the session cookie is deleted immediately.
• Ask us to close or delete your submission ticket, and to remove your published deck, by opening an issue or using the contact details below.
• Clear your browser data to erase all local review progress instantly.

Children's privacy

Anki Browser is a general-audience study tool and is not directed at children. We do not knowingly collect personal information from children. If you believe a child has submitted a deck, contact us and we will remove the submission.

Changes to this policy

If this policy changes materially we will update the date at the top of this page. Continued use of the site after a change means you accept the updated policy.