qrff
Privacy Policy
This policy explains the information qrff handles to provide its features. qrff is owned and maintained by Brandon Ubben.
Information the service handles
Depending on how you use qrff, the service stores or receives:
- Account information: your email address, an account name, account timestamps, and authentication records such as sessions and password-reset attempts. Passwords and recovery PINs are stored as hashes rather than in their original form.
- QR-code information: the name you give a QR code, its generated public slug, its target URL, active or archived status, and creation and update times.
- Scan information: the time of a scan, the QR code scanned, a hash of the requesting IP address, and portions of the requesting user agent and referrer. The app stores the IP value as a hash, not as the original IP address, for basic scan tracking and security.
- Security information: session information and password-reset attempt records, which can include an email address, a hash of the requesting IP address, whether an attempt succeeded, and its time.
How information is used
This information is used to authenticate you, provide account settings and password recovery, create and manage your QR codes, redirect scans, show basic scan counts, generate exports, protect the service, and respond to support requests.
Cookies and external requests
qrff uses authentication session cookies so signed-in features work. The app loads the Material Symbols icon stylesheet hosted by Google Fonts. Loading that stylesheet makes a request to Google, which may include normal technical request information such as your IP address. Google's own policies apply to that request.
Sharing and service providers
qrff may use third-party infrastructure to operate and secure the service. This policy does not identify particular providers or claim that a particular provider receives particular information. qrff does not control the privacy practices of a destination website.
Storage and requests
The app does not currently provide a self-service account-deletion control or a fixed public retention schedule. Records may remain while they are needed to operate the service, provide its features, or maintain security. For questions about information associated with your use of qrff, email brandon@ubben.co.
Security
qrff uses measures such as password hashing, hashed IP values for tracking and reset protection, and authenticated sessions. No method of storing or transmitting information can be guaranteed completely secure.
Changes to this policy
This policy may be updated when the service or its data practices change. The current version will be available on this page. Questions about this policy can be sent to brandon@ubben.co.