Back

Privacy Policy

Last updated: 2026-05-03

QuickCards is a Chrome extension and a companion website that export Quizlet flashcards or vocab lists to formats like PDF, Anki, TXT, CSV, JSON, or directly into Knowt. This page explains what data QuickCards touches and what we do (and don't do) with it.

Short version. QuickCards runs in your browser. We have no user accounts. We don't store your flashcards, your IP, or anything that identifies you. We collect a handful of anonymous usage counts so we know which features are worth keeping. The full list is below.

Maintainer

QuickCards is built by Oliver Seifert in Switzerland. For privacy questions, write to quickcards@alias.oseifert.ch.

The browser extension

What stays on your machine

The extension stores your separator preferences (the characters between term and definition, and between cards) in chrome.storage.sync. If you're signed into Chrome, that bucket is synced to your Google account by Chrome itself, the same way bookmarks are. We don't see it and we don't run a server. A short-lived flag in chrome.storage.local tells the popup which screen to open. That's all.

Quizlet

When you open a Quizlet set page, the extension fetches the set's cards from quizlet.com directly from your browser. The request goes out the same way it would if you loaded the page yourself, using whatever Quizlet cookies your browser already holds. If you're signed into Quizlet, Quizlet sees that account; if you're not, Quizlet sees an anonymous visitor. Either way, we never see those cookies and we never proxy the request through a server of ours. The cards land in your browser and don't leave it unless you explicitly export them. See Quizlet's privacy policy .

Knowt import

The Knowt import is opt-in: it only runs when you click the Knowt button. When you do, the extension reads the session cookie that Knowt has already set on your browser (so we don't ask you for any credentials), takes the access token out of it, and sends your set straight to Knowt's own GraphQL API. The token and the cards go to Knowt and Knowt only. We don't proxy, log, or store either. If you're not signed into Knowt, the extension shows a sign-in prompt and stops there. See Knowt's privacy policy .

Other exports

PDF, Anki .apkg, TXT, CSV, and JSON exports are generated locally and saved straight to your downloads folder. They never touch a server we control.

Permissions

Each Chrome permission the extension requests, and what it's used for:

The website

The website does the same things as the extension, but for vocab lists you paste in. All parsing and exporting happens in your browser. Nothing you paste is sent anywhere. The site is statically prerendered, has no login, and sets no tracking cookies. It's hosted on Vercel, see Vercel's privacy policy for what their CDN does at the network layer.

Anonymous usage analytics

We run a self-hosted Plausible instance. Plausible does not use cookies, does not track users across sites, and does not store IP addresses or device fingerprints. The full list of events the extension and website send:

That is the full list. We do not log card contents, set IDs, URLs you visit, search terms, or anything that identifies you. The data is used to decide which features are worth keeping. We don't sell it, share it, or use it for ads. Any standard ad blocker that recognises Plausible will silently drop the requests; the extension and website work normally either way.

GitHub

The source code, releases, and bug tracker live on GitHub. Visiting the repository, filing an issue, or downloading a release zip from there results in a direct request from your browser to GitHub. GitHub may log your IP for their own security purposes. See GitHub's privacy statement . We don't proxy the request and we don't see your IP.

Your rights

Under Swiss data protection law (FADP) and the EU GDPR you have the right to access, correct, or delete personal data we hold about you. We don't hold any. If you have a question about data we might have collected anyway, write to quickcards@alias.oseifert.ch and we'll sort it out within 30 days.

Changes

If this policy changes in any meaningful way, the date at the top of this page will move and the change will be visible in the public Git history of this site.