Privacy Policy
Last updated: 2 October 2026
At QuvtyQR we value your privacy. This policy explains what data we collect when you use our service, why we collect it and how we protect it.
1. Data we collect
- Account info: Name, email, phone, password (stored encrypted).
- Business info: Business name, address, menu content, images, opening hours.
- Usage data: QR scans, session info (device, approximate location/IP), page interactions.
- Order/reservation data: Name, phone and order content left by your customers.
- Transaction security, billing and fraud-prevention data: IP address and the country determined from it, phone number, the card's issuing country and card fingerprint received from our payment provider (Stripe) — the card number is not stored — and payment dispute (chargeback) records.
- Device and browser security data: A random device identifier stored in a first-party cookie (qq_did; it contains no personal data by itself), a browser fingerprint (a one-way SHA-256 hash of browser and device characteristics, stored in the qq_fp cookie), approximate location derived from your IP address by Cloudflare (country, region, city and approximate coordinates), and your browser's user agent and language — recorded at sign-up, sign-in and payment. Web browsers cannot access hardware identifiers such as IMEI; we do not collect them.
- Consent records: When you accept the Terms of Use and the Privacy Policy (at sign-up, when purchasing and when turning on auto-renewal), we record the document version, time, IP address, country, device identifier and browser user agent as evidence; for payments, the record ID is attached to the payment at our payment provider (Stripe).
2. Why we use data
- To provide the service, manage your account and publish your menu.
- To build your analytics panel (scans, peak hours, popular products).
- To deliver order and reservation notifications.
- For security, abuse prevention and legal obligations.
- For regional pricing and location verification, billing and tax obligations, preventing fraud and chargebacks, and preventing accounts closed due to a chargeback from being reopened.
- For account and payment security, and to enforce the permanent ban after a chargeback: the device identifiers of a banned account are blocked; the IP address and browser fingerprint are used only as supporting signals and never block on their own.
We process transaction security, billing and fraud-prevention data on the legal grounds of the establishment and performance of a contract, compliance with legal obligations (billing and tax) and our legitimate interest in preventing fraud. Blocking records of accounts closed due to a chargeback are kept for as long as the blocking purpose continues and for the applicable statutory retention periods. Device and browser security data are processed on the basis of our legitimate interest in preventing fraud and the performance of the contract; consent records are kept to prove the conclusion of the contract. Security records are kept for 2 years.
3. Data sharing
We do not sell your data to third parties. We share it only with the infrastructure providers needed to deliver the service (Stripe for payments, location verification and fraud prevention; email delivery; hosting). These providers only access the data needed to provide their own service. Cloudflare, our network and security provider, processes IP addresses to protect the service and to determine approximate location.
4. Cookies
We use cookies for session management and core functionality. See our Cookie Policy page for details.
5. Data security
Passwords are one-way hashed, connections are encrypted with SSL/TLS, and access is restricted with authorization. Two-step verification (2FA) can be used to protect your account.
6. Your rights
You can request access to, correction of and deletion of your personal data. For your rights under data protection law, contact us.
7. Contact
For privacy questions: [email protected]