Skip to content

Draft, pending legal review

This text is a working draft. It has not been reviewed by a lawyer, is not legal advice and may change before BlazeScanner opens sign-ups. Items marked “Owner to confirm” are still being decided.

Privacy Policy

Last updated · Version 2026-11

BlazeScanner helps people reach you through a QR code without seeing your phone number. This policy explains what personal data we handle, why, who we share it with and the choices you have.

1. Who we are

BlazeScanner is operated by [Owner to confirm: legal entity name], [Owner to confirm: registered address] (“BlazeScanner”, “we”, “us”). For the personal data described here, we are the data fiduciary under India’s Digital Personal Data Protection Act, 2023 (“DPDP Act”): we decide why and how it is processed.

When an event organiser or a business uses BlazeScanner to manage their own guests or customers, we process that guest or customer data on their behalf and on their instructions. [Owner to confirm: confirm the fiduciary/processor split for organiser and business data with counsel]

2. The short version

  • Your phone number, address and emergency contacts are never shown to someone who scans your QR.
  • People who scan your QR reach you through BlazeScanner’s in-app messaging. They never see your number, and you never see theirs.
  • We do not track your location. Location is only ever shared when a person who found an item ticks a box to share where they are, once, with the owner.
  • We do not sell personal data and do not use advertising or analytics cookies.
  • You can see, correct, export and delete your data, and complain to our Grievance Officer.

3. Personal data we collect

When you create and use an account

  • Account: your mobile number (verified by a one-time SMS code), name, date of birth (to confirm you are 18 or over), your BlazeScannerID, an optional email address, an optional password (stored only as a one-way hash), language and time zone.
  • Emergency contacts: the name and mobile number of people you add. They are asked to confirm in the app before they receive any alert.
  • Vehicles and items: details you enter, such as make, model and colour, an optional registration number, item category, name, description and a note for finders.
  • Profiles (Blaze Identity): the fields you add, and which of them you choose to make public.
  • Events, queues, appointments and shop listings: what you or the organiser or business enter, such as guest names and contact details, RSVPs, check-ins, queue tokens, bookings and catalogue items.
  • Messages: alerts and conversations sent through BlazeScanner, including the reason chosen (for example “Blocking my car”).
  • Security and device data: signed-in sessions (browser and device description, sign-in times), one-time code requests and attempts, security events (such as failed sign-ins) and an audit log of sensitive actions. For these we store your full IP address, to protect your account and investigate misuse. Administrator screens show it masked (for example 203.0.113.x).
  • Payments: when paid features are available, order details, amount, status and invoices. Card, UPI and bank details are handled by Razorpay; we do not receive or store them.

When someone scans a QR (no account needed)

  • The QR that was scanned, when, the outcome, a coarse device family (such as Android or iOS) and the referring website’s name. We do not store the scanner’s IP address with the scan: only a keyed hash (HMAC) of their network range (the first three parts of an IPv4 address, or the /48 block of an IPv6 address).
  • The reason and message the person sends, if they send one.
  • To apply message limits and let an owner block one sender, a message is linked to two keyed hashes, never stored in readable form: one of the sender’s network range (as above) and one of a random identifier kept in their browser (bz_scanner_id). The identifier is random and not derived from the device or the person. The sender’s IP address is used for rate limits while the request is handled.
  • Location, only for Blaze Find and only if the finder ticks “Share where I found it”: one reading from the browser at the moment of sending, attached to that message and visible only to the item’s owner. It is never collected automatically and never updated afterwards.

4. What scanners see, and what stays private

Public pages show only what each page needs, from an explicit allow-list checked by automated tests.

  • Vehicle QR: a vehicle summary (such as make, model, colour and, if enabled, a partly hidden registration number), the alert buttons, and India’s emergency numbers 112 and 108.
  • Item tag (Blaze Find): the item category, the note you wrote for finders and whether it is marked lost or returned. Not the item’s name, description or owner.
  • Profile (Blaze Identity): exactly the fields you marked public, and nothing else. If you publish a phone number or email on a profile, anyone with the link or QR can see it.
  • Event invitation or pass: the details the organiser chose to show to that guest.

Never shown to scanners: your phone number, address, email, emergency contacts and BlazeScanner account details (unless you publish them on a profile yourself).

5. Why we use it

  • To create your account, verify your mobile number and keep you signed in.
  • To deliver alerts and messages between people who scan a QR and its owner, and to notify your confirmed emergency contacts when an emergency alert is sent.
  • To run the features you use: QR codes, profiles, events, queues, bookings and listings.
  • To process payments, issue invoices and meet tax and accounting duties.
  • To keep the service safe: rate limits, bot checks, blocking, abuse reports, fraud prevention and security logs.
  • To answer support requests and grievances.
  • To meet legal obligations and respond to lawful requests from authorities.

7. Who we share it with

We share personal data only with service providers who help run BlazeScanner, under contracts that limit their use of it:

  • MSG91 (India): sends one-time sign-in codes by SMS, and SMS alerts once they are switched on.
  • Razorpay (India): processes online payments.
  • Cloudflare Turnstile: a bot check on sign-in, sign-up and public forms. On a scan page it loads only after the person chooses to send an alert or message, and it can see that page’s address and device signals.
  • Hosting: our servers run on a virtual private server rented from Hostinger, located in [Owner to confirm: server location (country/city)].
  • Off-server backups: encrypted before they leave our server; provider and location [Owner to confirm: off-server backup location (TBD)].

Within BlazeScanner, other users see your data only as described above: the owner of a QR sees the messages sent to it; organisers and businesses see the guest or customer details for their own events and locations; staff they invite see only what they are assigned.

We disclose data to authorities only when the law requires it. We do not sell personal data.

8. Where your data is stored

Our main database is on our server in [Owner to confirm: server location (country/city)]. Off-server backups may be stored outside India; the location is [Owner to confirm: off-server backup location (TBD)] and this section will name it before backups start. Cloudflare runs a global network, so the bot check may be processed outside India. Any transfer outside India follows the DPDP Act and any country restrictions the Government of India notifies.

9. Cookies and browser storage

We use only what the service needs to work. No advertising, tracking or analytics cookies.

  • Sign-in cookie (__Host-bz_session): keeps you signed in. It cannot be read by page scripts, ends after 30 days without use and at most after 90 days.
  • Security cookie (__Host-bz_csrf): protects your account from forged requests.
  • Scanner identifier (bz_scanner_id in the browser’s local storage): created the first time someone sends a message from a scan or conversation page, and sent with each message so an owner can block that sender. It stays until the browser’s site data is cleared.
  • Cloudflare Turnstile may set its own cookies when the bot check runs.

10. How long we keep it

We keep personal data only as long as it is needed for the purpose it was collected for, or as the law requires. What happens today:

  • Account data: while your account is open.
  • Deleted accounts: held for 30 days so you can change your mind, then personal data is permanently erased. [Owner to confirm: confirm the 30-day grace period]
  • One-time code requests (which include the mobile number and IP address): deleted automatically after 90 days.
  • Security events (such as failed sign-ins, with IP address): deleted automatically after 90 days.
  • Signed-in sessions: until you sign out or the session expires, and then as long as your account exists.
  • Messages and conversations: kept while the QR, vehicle or item they belong to and your account exist. [Owner to confirm: intended limit, e.g. 12 months after a conversation ends]
  • Scan records: kept while the QR and your account exist. [Owner to confirm: intended limit, e.g. 13 months]
  • Security audit log of sensitive actions: 3 years.
  • Invoices and payment records: 8 years, as tax law requires, with minimal buyer details.
  • Server backups: 14 days on the server; off-server copies [Owner to confirm: off-server backup location (TBD)].

[Owner to confirm: confirm all retention periods with counsel]

Your BlazeScannerID is never given to anyone else, even after your account is deleted.

11. Your rights

Under the DPDP Act you have the right to:

  • Access: get a summary of the personal data we process about you and who we shared it with, and a copy of your data.
  • Correction and completion: fix or update your data. Most of it you can edit yourself in Account and My Stuff.
  • Erasure: delete your account and personal data, except what we must keep by law.
  • Grievance redressal: complain to our Grievance Officer and get a response.
  • Nomination: name someone to exercise these rights for you if you die or become unable to.

Data export and account deletion are coming to Account settings. Until then, and for any other right, write to [Owner to confirm: support email] (see Help: delete or export). Most corrections you can make yourself at any time. We may ask you to confirm your identity first. We respond within [Owner to confirm: response time].

12. Children

BlazeScanner accounts are for people aged 18 and over. We do not knowingly create accounts for children. An organiser or an adult guest may add a child to an event as a guest record with a name only (no phone, email, account or sign-in). If you believe a child has created an account, contact us and we will delete it.

13. How we protect it

We use encrypted connections (HTTPS), one-way hashing for passwords, sign-in cookies that page scripts cannot read, rate limits and bot checks, an authenticator for administrator access, and an audit log of sensitive actions. Access to personal data is limited to people who need it.

No system is perfectly secure. If a personal data breach happens, we will inform affected users and the Data Protection Board of India as the law requires.

14. Grievance Officer and contact

Grievance Officer: [Owner to confirm: Grievance Officer name]
Email: [Owner to confirm: Grievance Officer email]
Address: [Owner to confirm: registered address]

General questions: [Owner to confirm: support email].

If you are not satisfied with our response, you may complain to the Data Protection Board of India.

15. Changes to this policy

We will update the date at the top when this policy changes. If a change materially affects how we use your data, we will tell you in the app before it takes effect and, where the law requires, ask for your consent again.