Privacy policy — review draft

Information the service stores

QR records include a name, optional description, destination URL, public identifier, status, timestamps, and optional owner account. Guest credentials are stored as SHA-256 hashes. Account records contain a name, email, library-managed password hash, and server-side sessions. Abuse reports and moderation audit records are stored to support safety review.

Requests and infrastructure

Cloudflare processes requests to provide hosting and security. The application uses keyed IP-derived hourly counters for abuse prevention without storing raw IP addresses in those counters. Auth IP tracking is disabled. The application does not write a scan-history row or use analytics scripts. Infrastructure access and diagnostic data may still be processed by Cloudflare; the operator must document account-level logging and contractual settings.

Cookies and local preferences

Authentication uses essential session cookies. A theme preference is stored in your browser local storage. Guest management credentials remain in the saved URL fragment and application memory; they are not placed in browser storage. The application sends no-referrer headers, but you must keep private links out of third-party tools and shared screenshots.

Deletion and retention

Deleting a QR clears its destination, credential, owner, name, and description while reserving its public identifier as a tombstone. Account deletion disables owned QR records and removes auth records through the authentication library. Expired sessions, verifications, and rate-limit counters are cleaned daily. Abuse reports and audit records require an owner-defined retention schedule and deletion procedure. Cloudflare backups may retain older information within their configured recovery window.

Your requests and contact

Use Account settings to delete an account, or use the privacy email below for a request. Describe the request without including passwords or private management links. The operator still needs to finalize identity verification, data access and export procedures, retention decisions, applicable legal bases, and response handling. No legal compliance certification is made by this draft.

Advertising and future changes

Advertising is disabled. No optional ad or analytics technology is loaded. Before any ad integration is enabled, the owner must review disclosures, regional requirements, consent, withdrawal, vendor processing, and retention. This policy must be revised to reflect the actual configuration.

What advertising would change

If Google advertising is introduced, Google and other advertising providers may receive page URLs, IP addresses and device information, and may place or read cookies or similar identifiers for ad delivery, measurement, fraud prevention and, where permitted, personalization. That is a description of potential future processing, not technology currently enabled here. Provider identities, purposes, choices and applicable consent handling must be disclosed and tested before activation. Google’s explanation of its partner-site data use is linked below.

References

• Cloudflare privacy policy (hosting and security)
• How Google uses information from partner sites (if advertising is introduced)