QuickKit

Privacy

QuickKit is built to respect your data. This page describes the actual product accurately — no marketing, no unsupported claims.

No account, no backend, no database

QuickKit does not require sign-up, does not call a backend API, and is not connected to any database. The production build is a static export of HTML, CSS, and JavaScript. There is no server that processes your inputs.

What happens locally

  • Calculations run in your browser

    Every tool computes its result with client-side JavaScript. Numbers, dates, colors, passwords, QR payloads, and text you enter never leave your device.

  • Cryptographic randomness

    Passwords, PINs, coin flips, dice, and random choices use window.crypto.getRandomValues with rejection sampling for unbiased distributions.

  • Sensitive data is never persisted

    Generated passwords, PINs, QR payloads, raw Text Tool content, and Random Picker choice lists live only in memory. Closing the tab or reloading the page clears them. They are not written to localStorage or sent anywhere.

What is stored locally

QuickKit stores a small set of durable, harmless preferences in your browser's localStorage:

  • Theme preference — System / Light / Dark.
  • Favorites — the identities of tools you starred (e.g. "color", "unit-converter").
  • Recent Tools — a small bounded list of the identities of tools you have visited (most recent first). QuickKit stores tool identities only — never inputs, results, command strings, or any other content.
  • Haptics preference — on or off.

You can clear any of these at any time from Settings. A schema version is stored alongside the data so future updates can migrate it safely; if the data is ever corrupted, QuickKit falls back to defaults.

PWA and offline

When you install QuickKit as a Progressive Web App, a service worker caches the application shell and tool routes so the app continues to work offline. The service worker only caches application assets (HTML, CSS, JS, icons) on your device — it does not transmit your data anywhere. There is no push notification functionality.

What QuickKit does NOT do

  • No analytics or telemetry.
  • No tracking pixels, no third-party scripts, no advertising.
  • No cookies for tracking.
  • No operation History feature. There is no /history, no calculation log, no input/result history stored anywhere.
  • No backend, no API server, no serverless functions.
  • No database of any kind.

Contact

For privacy questions or security reports, please open an issue on the QuickKit GitHub repository.