Privacy Policy

The short version

• No accounts. Nothing to register, so there's no profile to leak.
• No tracking. No analytics, no cookies, no fingerprinting, no ad pixels.
• Your data stays on your device. QR generation happens entirely in your browser — your links, messages, Wi-Fi passwords, contacts and UPI IDs are never transmitted to us or anyone else.
• One exception: files you choose to upload are stored temporarily in the cloud and auto-deleted within about 24 hours (details below).

1. What we never collect

Because QRForge has no signup and no server-side generation, we do not collect:

• Names, email addresses, or phone numbers
• Account credentials — there are no accounts
• The content you encode into QR codes (URLs, Wi-Fi passwords, contact details, payment IDs, messages, GPS coordinates)
• Browsing behavior on this site — we run no analytics of any kind
• Payment information — we never process payments; UPI codes encode your own bank's UPI ID and money moves directly between banks

2. What is stored on your device

Exactly one thing: your theme preference (light or dark mode), saved in your browser's localStorage. It never leaves your device and you can clear it any time through your browser settings.

3. File uploads — the one exception

A QR code can only hold a few kilobytes, so the File → QR tool and WhatsApp's attach a file option work by uploading your file to temporary cloud storage (AWS S3) and embedding the public download link in the QR. Know exactly what that means:

• The link is public. Anyone who scans the QR or obtains the link can download the file until it expires.
• Files auto-delete after about 24 hours via a storage lifecycle rule. Deletion timing is approximate.
• Upload only files you're comfortable sharing publicly for that window — never IDs, passwords, or sensitive documents.
• During the upload, our server-side function sees the request needed to authorize it (standard for any upload on the web). It does not read, scan, or store the file's contents.
• Need one gone sooner? Contact us and we'll delete it from storage immediately.

4. Third-party services

QRForge is a static site with no backend of its own. These parties are involved in serving it:

• Netlify (hosting) — serves the pages. Like every web host, Netlify keeps standard server logs (including IP addresses) for security and abuse prevention, governed by Netlify's privacy policy.
• Public CDNs (jsDelivr, UNPKG, cdnjs) — serve the open-source code libraries that draw the QR codes and barcodes. Requests to them expose your IP to those services, as with any website that loads scripts from a CDN.
• AWS S3 (file uploads only) — temporary storage for uploaded files, as described in section 3. Governed by AWS's privacy notice.

None of these parties receive the content you type into the generators — that is encoded in your browser and never sent to them.

5. Cookies and similar technologies

We use no cookies — not tracking, not session, not advertising. The only browser storage we use is the localStorage theme preference described in section 2. No third-party trackers, pixels, or beacons are loaded.

6. Device permissions

The Location QR tool can optionally use your browser's geolocation permission to fill in your current coordinates. This runs entirely in your browser — the coordinates fill the input fields on the page and nothing is transmitted unless you then generate a QR containing them (which you control).

7. Children's privacy

QRForge is a general-purpose utility with no age-restricted content and collects no personal information from anyone, including children. No data is collected from children because no data is collected from anyone.

8. Your rights

Under regulations like GDPR and CCPA you have rights over your personal data. Because we don't collect any:

• Right to access / deletion — there is nothing for us to access or delete; nothing identifies you.
• Theme preference — clear it yourself: browser settings → clear site data.
• Uploaded files — they auto-delete within ~24 hours; contact us below for faster removal.
• Server logs — handled by Netlify per their policy; contact them for log-related requests.

9. Data security

The strongest security is not needing it: with no database, no accounts, and no stored personal data, there is nothing for a breach to expose. Uploaded files exist only in the short public window described above — treat anything uploaded as public during that time.

10. Changes to this policy

We may update this policy as the site evolves. The "Last updated" date at the top always reflects the current version. If we ever add a feature that changes the privacy picture, we'll update this page before or at the same time — not after.

11. Contact

Two inboxes — pick the one that matches your message:

Related pages: Terms & Conditions · About Us · FAQ