Legal
Data Retention Policy
Last updated: June 2026 · QRDoc by Ashwinkumar D Basari
🗄️
We retain almost nothing — by design. QRDoc's architecture minimises data retention to near zero.
🎯 Purpose
This policy describes how QRDoc handles operational data. Because QRDoc processes data locally in the user's browser, the vast majority of data is never transmitted to any server and therefore cannot be "retained" by QRDoc.
🌐 Browser-Side Processing
- Your document URLs are never transmitted to a QRDoc server.
- Generated QR codes are rendered to an HTML canvas element in your browser.
- All in-browser state is held in JavaScript memory only.
Browser memory is ephemeral. It is automatically cleared when the tab is closed or the page is refreshed.
⏱️ Retention Periods
| Data Type | Where Stored | Retention Period |
|---|
| Document URL (input) | Browser memory | Tab session only — cleared on close |
| Generated QR image | Browser memory / local device | Until tab close or download |
| Rate-limit counters | Browser memory (JS Map) | Tab session only |
| Security event logs | Browser console (DevTools) | Tab session only — not persisted |
| Analytics data | Google Analytics (planned) | Per Google Analytics retention settings (typically 14 months) |
| AdSense cookies | Browser cookie store (planned) | Per Google AdSense / IAB consent framework |
🧹 How to Clear Your Data
- Close the browser tab — this clears all in-memory state immediately.
- Use the Reset button within the tool to clear the current session.
- Clear browser cookies and site data via your browser settings to remove any future analytics cookies.
📊 Analytics Data (Planned)
- Only anonymised, aggregated usage data will be collected.
- No personally identifiable information (PII) is collected.
- IP addresses are anonymised before processing.
- Analytics will be introduced with an appropriate cookie consent mechanism.
🔄 Policy Changes
This policy may be updated periodically. The "Last Updated" date at the top of this page indicates when it was last revised.