Legal

Privacy Policy

How we collect, use, and protect your personal data.

Last updated: November 17, 2026

This Privacy Policy describes how Qravio, a sole proprietorship of Shaukat Ali ("Qravio", "we", "our", or "us") collects, uses, shares, and protects information when you use our website at qravio.app and any related services, applications, or features (collectively, the "Service"). By accessing or using the Service, you agree to this policy.

This policy is published in compliance with the Digital Personal Data Protection Act, 2023 (DPDP Act) of India and applicable rules thereunder.

1. Information We Collect

Account Data

When you register for an account, we collect:

  • Full name and email address
  • Password (stored as a salted hash — never in plain text)
  • Profile picture (if provided via OAuth)
  • Organisation/workspace name

QR Code and Workspace Data

When you create and manage QR codes, we store:

  • QR code name, type, destination URLs, and content
  • Page design settings (colours, templates, branding)
  • Files you upload (PDFs, images, vCards) stored in our cloud storage
  • Folder structure and workspace member roles

Scan Analytics Data

Every time someone scans one of your QR codes, our edge network records the following data to power your analytics dashboard:

  • Hashed IP address — we hash the IP address with a daily-changing value before storing it in scan analytics. The original IP address is not stored in those analytics records.
  • Country, region, and city (derived from IP, then the IP is discarded)
  • Device type (mobile, tablet, desktop, bot)
  • Referrer information supplied by the browser, which can include a full URL with its path and query parameters
  • The destination URL served for a website QR, including an A/B test variant
  • Browser language and user-agent string
  • Timestamp of the scan
  • A session identifier to distinguish unique visitors from repeat scans

These records describe interactions with our QR codes. Referrer and destination URLs can contain personal information if it is present in the URL. We retain scan analytics as described in Section 4 and filter private URL details from operational monitoring data separately.

Payment Data

All payment processing is handled by our payment partners, depending on your region. Customers in India are billed in ₹ by Razorpay Software Private Limited, and international customers are billed in $ by Lemon Squeezy, LLC acting as our Merchant of Record. We do not collect, process, or store card numbers, bank account details, or UPI credentials on our servers. We receive a transaction ID, subscription status, and billing amount from the relevant provider to maintain your subscription record.

Usage and Technical Data

  • Pages visited within the Service and features used
  • Browser type, operating system, and viewport size
  • Operational logs, error reports, and sampled performance traces
  • Support communications you initiate with us

Operational Monitoring Data

We collect technical information to detect outages, investigate errors, and improve reliability. Depending on the event, this can include timestamps, request and correlation identifiers, route patterns, response status codes, timings, QR type and delivery outcome, application version, exception details, and stack traces. Events may include internal account, workspace, or QR identifiers so we can investigate an affected operation. These identifiers can be linked to our account records and are not necessarily anonymous.

We apply filtering and data-minimisation controls to application telemetry to limit personal information and exclude credentials, authentication headers, cookies, request and response bodies, and private URL details from diagnostic events and application logs. Hosting providers also process network and service information needed to deliver and protect the Service.

Device location (opt-in)

If a QR code owner turns on precise scan location, the person scanning sees a short request from that business before or over its page. Nothing is collected unless the scanner taps Share location and then allows it in their browser. Skipping, or denying the browser prompt, still opens the content.

  • What we store when a scanner shares: latitude, longitude and the device-reported accuracy, one fix per scan, with the device type, country and the time
  • The QR code owner is the Data Fiduciary for that location; Qravio is the Processor acting on the owner's instructions
  • The location is never used for advertising, never sent to a retargeting pixel, and is never included in webhooks or the public API

Form submissions and private feedback

Some QR codes open a form: a lead form, or the private-feedback form on a review page. What you type there goes to the business that owns the QR code, not to the public.

  • What we store: the answers you enter, the star rating if you give one, the consent wording you agreed to, the time, your browser type and a one-way hash of your IP address (used to limit spam, not to identify you)
  • The QR code owner is the Data Fiduciary for your submission and decides how it is used, including whether to reply; Qravio is the Processor storing it on the owner's instructions
  • The owner may receive your submission by email or forward it to their own systems
  • To access or delete a submission, contact the business directly, or reach us through the contact details in Section 11 and we will pass your request on

2. How We Use Your Information

  • Provide and operate the Service — create and serve your QR codes, host your files, and render scan landing pages at the Cloudflare edge
  • Analytics dashboard — aggregate and display scan statistics for your workspace
  • Scan location (opt-in) — show the QR code owner where a code was scanned, only for scanners who chose to share
  • Billing and subscriptions — manage plan upgrades, renewals, and invoices via Razorpay (India) or Lemon Squeezy (international)
  • Transactional communications — send account verification, password reset, workspace invitation, and payment receipt emails via Resend
  • Safety and abuse prevention — detect and block QR codes pointing to malicious or prohibited destinations
  • Product improvement — analyse aggregate, de-identified usage patterns to prioritise features
  • Reliability and incident response — monitor availability and job completion, investigate errors and failed requests, measure performance, and restore service during an incident
  • Legal compliance — maintain records required by applicable Indian law

3. Data Sharing and Disclosure

We do not sell, rent, or trade your personal data to third parties. We share data only in the following limited circumstances:

RecipientPurposeData shared
Supabase Inc.Authentication, PostgreSQL database, and file storageAll account and workspace data
Cloudflare Inc.Edge QR routing, KV storage, CDN, and operational monitoringQR metadata, hashed scan events, request identifiers, scan outcomes and timings
Razorpay Software Pvt. Ltd.Payment processing (India / ₹)Email, billing amount, subscription plan
Lemon Squeezy, LLCPayment processing & Merchant of Record (international / $)Email, billing amount, subscription plan
Resend Inc.Transactional email deliveryEmail address and email content
Vercel Inc.Frontend hosting and analyticsAnonymised page-view telemetry
RenderBackend hosting and service diagnosticsOperational logs, request identifiers, response status codes and timings
SentryError monitoring, sampled performance tracing, and debuggingFiltered error and trace data, stack traces, request identifiers, application versions, and internal account or workspace identifiers
Better StackCentralised operational logs, uptime monitoring, and public service statusFiltered application logs, request and internal identifiers, service timings, availability checks, and incident information
Healthchecks.ioScheduled-job completion and failure monitoringJob names, start and completion times, run durations, and failure signals

We may also disclose information if required by law, court order, or a government authority, or to protect the rights, property, or safety of Qravio, our users, or the public.

4. Data Storage and Retention

  • Account and workspace data — retained while your account is active and for 30 days after you request deletion, so you can recover the account if you change your mind. Your QR codes stop resolving immediately when you request deletion. Permanently deleted thereafter.
  • Form submissions and private feedback — kept until the QR code they were sent through is deleted, or the owner's account is erased.
  • Shared scan locations — kept for 12 months, and deleted earlier when the QR code is deleted or the account is erased.
  • Scan analytics — raw scan event rows are retained for 12 months. Aggregated counters (total scans, scans by date, etc.) are retained indefinitely.
  • Uploaded files — retained while your account is active; deleted within 30 days of account deletion or plan downgrade below the storage threshold.
  • Billing records — retained for 7 years as required by Indian accounting regulations. When you delete your account these records are kept, but your name, email, and payment-provider customer reference are removed from them so they can no longer be traced back to you.
  • Encrypted backups — our database provider keeps encrypted point-in-time backups on a rolling window for disaster recovery. Deleted data can persist in those backups until the window rolls past, after which it is gone. Backups are never used to restore an individual deleted account.
  • Operational telemetry — logs, error events, and performance traces are retained under the data-specific retention settings and plan of each monitoring provider for debugging, reliability monitoring, and incident response. Retention can differ between logs, errors, and traces. You can request details about the current retention periods through our privacy contact below.

Primary application data is stored in data centres operated by Supabase and Cloudflare. Hosting and monitoring providers separately process operational telemetry. See Section 8 for cross-border transfer details.

5. Your Rights under the DPDP Act, 2023

As a Data Principal under India's Digital Personal Data Protection Act, 2023, you have the following rights:

  • Right to Access — request a summary of the personal data we hold about you
  • Right to Correction — request correction of inaccurate or incomplete data
  • Right to Erasure — delete your personal data (subject to legal retention obligations). You can do this yourself at any time from Settings → Account → Delete Account; no request or support ticket is needed.
  • Right to Grievance Redressal — raise a complaint with our Grievance Officer
  • Right to Nominate — nominate another individual to exercise your rights in case of death or incapacity

To exercise any of these rights, email us at [email protected] with the subject line "DPDP Rights Request". We will respond within 30 days.

6. Cookies and Tracking

We use essential cookies (for authentication sessions managed by Supabase) and analytics cookies (Vercel Analytics, which uses anonymised page-view data). We do not use advertising or cross-site tracking cookies. A QR scan page that asks for location also sets small strictly necessary qr_geo_* cookies, none of which hold a location. For full details, see our Cookie Policy.

7. Children's Privacy

The Service is not directed at individuals under the age of 18. We do not knowingly collect personal data from minors. If you believe a minor has provided us with personal data, please contact us immediately and we will delete it promptly.

8. International Data Transfers

Our hosting, storage, and monitoring providers, including Supabase, Cloudflare, Vercel, Render, Sentry, and Better Stack, operate infrastructure outside India, including in the United States and European Union. Operational telemetry locations depend on the provider and configured data region. By using the Service, you consent to your data being transferred to and processed in these jurisdictions. We ensure our providers maintain appropriate technical and organisational safeguards.

9. Security

We implement the following security measures to protect your data:

  • All data in transit is encrypted using TLS 1.2 or higher
  • All data at rest is encrypted using AES-256
  • Passwords are stored as one-way Argon2 hashes (via Supabase Auth)
  • IP addresses are hashed before storage in QR scan analytics records
  • Role-based access control — team members only access data within their workspace
  • Service role keys (used for backend-to-database access) are stored as environment variables and never exposed to the client

No method of transmission over the internet is 100% secure. If you discover a security vulnerability, please report it responsibly to [email protected].

10. Changes to this Policy

We may update this Privacy Policy from time to time. We will notify you of material changes by email (to the address on your account) and by updating the "Last updated" date at the top of this page. Your continued use of the Service after the effective date constitutes acceptance of the revised policy.

11. Contact and Grievance Officer

For privacy-related questions, requests, or complaints, contact our Grievance Officer:

Name: Shaukat Ali
Email: [email protected]
Address: SRK Gardens, Kudlu Main Road, Singasandra, Bengaluru, Karnataka 560068, India

We aim to acknowledge your grievance within 48 hours and resolve it within 30 days. If you are not satisfied with our response, you may escalate to the Data Protection Board of India once it is constituted under the DPDP Act.