Legal

Privacy Policy

Last updated: June 2025 · QRDoc by Ashwinkumar D Basari

🔒
Your privacy is the architecture, not an afterthought. QRDoc is designed from the ground up so that no URL, document link, or personal data you enter ever leaves your browser tab. There is no server, no database, and no analytics.

🌐 How Data Flows (or Doesn't)

Every operation in QRDoc — URL parsing, validation, direct-link conversion, and QR code rendering — runs entirely within your browser using the JavaScript engine on your device.

Your browser
→
QR generated locally
✕
Any server
The Content Security Policy enforced by QRDoc explicitly sets connect-src 'self', which technically prevents the page from making network requests to any external server — even if the code tried to.

📋 What Data QRDoc Handles

The table below summarises every type of data touched by QRDoc and how it is handled:

Data Type How It's Used Sent to Server?
Document share URL Parsed and validated in-browser; used to generate the QR code Never
Selected cloud platform Used locally to choose the correct URL conversion logic Never
Generated QR image Rendered to an HTML canvas element; downloaded directly to your device Never
Rate-limit counters Stored in browser memory (JavaScript Map) only for the current session Never
Security event logs Written to browser console only (DevTools); not transmitted anywhere Never

🍪 Cookies & Tracking

QRDoc sets no cookies of any kind — neither first-party nor third-party.

  • No analytics scripts (Google Analytics, Plausible, Mixpanel, etc.) are loaded.
  • No advertising or remarketing pixels are present.
  • No session identifiers are created or stored.
  • No local storage or IndexedDB entries are written.
  • All in-memory state is cleared when the browser tab is closed.

📦 Third-Party Libraries

QRDoc loads one third-party JavaScript library: QRCode.js, served from the Cloudflare CDN (cdnjs.cloudflare.com). This library runs locally in your browser and does not send data to any Cloudflare or third-party server.

The library is loaded with a Subresource Integrity (SRI) hash, which means your browser verifies the file has not been tampered with before executing it. If the hash does not match, the library will not load.

Beyond this single CDN library load, QRDoc makes zero outbound network requests. The CSP connect-src 'self' directive enforces this technically.

🗑️ Data Retention & Deletion

Because QRDoc stores no data on any server, there is nothing to retain or delete on our end. All state — including the URL you pasted and the QR code generated — exists only in your browser's memory for the duration of your session.

  • Closing the browser tab immediately removes all QRDoc data from memory.
  • The "Reset All Data" button within the tool explicitly clears all in-memory state mid-session.
  • Sensitive fields (URLs, links) are also cleared on the browser's beforeunload event.

📬 Contact

If you have questions about how QRDoc handles data, or if you believe you have identified a privacy concern, you can reach the developer at:

Ashwinkumar D Basari · via LinkedIn or the contact details on the About page.

← Return to QRDoc