Privacy Policy
Last updated: 8 November 2026
Scan To Move puts a QR code on your vehicle so a stranger can reach you when your car is blocking someone, your lights are on, or your window is open — without either of you learning the other's phone number.
This policy describes exactly what the app stores. It was written against the actual database schema, not from a template. Where we do not collect something, we say so.
Contact for any privacy question or request: anas.official2017@gmail.com
1. What we collect
If you create an account (vehicle owner)
| Data | Why | Required? |
|---|---|---|
| Email address | It is your login, and the only way to reset your password | Yes |
| Password | Stored only as a salted hash by our authentication provider; we never see it | Only for email sign-in |
| Display name | Shown to you in the app | No |
| Vehicle label, type, and registration plate | So you can tell your own tags apart | No — a label alone is enough |
| Tag records | The QR codes you create | Created by you |
| Emergency contact name, phone number, and relationship | To let you quickly call a person you chose from the Emergency screen | Optional |
| Notification preferences and an FCM push token | To deliver vehicle alerts to this device when you allow notifications | Optional |
If you sign in with Google, we receive your email address and, if you have set one, your name. We do not receive your Google password or your contacts.
We do not ask for the account holder's phone number. An earlier version had one in the profile screen; it was removed. If you use Emergency Contacts, you choose to store that contact person's name and phone number. The app does not read your address book and does not disclose emergency contacts to scanners.
If you scan someone's tag (you do not need an account)
| Data | Why |
|---|---|
| The message you write | To deliver it to the owner |
| An anonymous session id | So you can see the owner's reply on your own thread. It is a random identifier, not a name, email or device id |
| A salted hash of your IP address | To stop one person flooding a vehicle owner with messages |
We do not store your IP address. It is combined with a secret salt and hashed; the result cannot be turned back into an address. It exists only to count requests.
We do not collect your location. The current release does not request location permission and sends no location data.
Automatically
| Data | Why |
|---|---|
| Crash reports and error diagnostics (Firebase Crashlytics) | To find and fix crashes. Includes device model, OS version and a stack trace |
| Firebase installation/push token | To route an alert to this installation after you allow notifications. It is not used for advertising or cross-app tracking |
2. What the other person can see
This is the part that matters most, so it is stated plainly.
A person who scans your tag can see: the label you gave the vehicle (for example "Blue Hatchback") and its type. That is all.
They cannot see: your name, your email address, your phone number, your registration plate, your account, your other vehicles, or any of your other conversations. This is enforced by the database itself, not only by the app: the lookup a scanner performs returns three fields and no others, and every table is closed to them.
You cannot see: who scanned your tag. There is no name, number or email attached to them.
3. What we never do
- We do not sell your data.
- We do not share your data with advertisers, data brokers or insurers.
- We do not run advertising in the app.
- We do not build a profile of you for marketing.
- We do not track you across other apps or websites.
4. Who processes your data
| Provider | Role | Where |
|---|---|---|
| Supabase | Database, authentication, realtime messaging | Mumbai, India (ap-south-1) |
| Google Firebase (Crashlytics and Cloud Messaging) | Crash reporting and optional push delivery | Google data centres |
| Google Play | App distribution, and sign-in if you choose Google | Google data centres |
We do not use session-replay, heatmap or behavioural analytics tools.
5. How long we keep things
| Data | Retention |
|---|---|
| Your account and profile | Until you delete your account |
| Tags | Until you delete them, or you delete your account |
| Conversations and messages | Until you delete your account or the related tag |
| Emergency contacts | Until you delete the contact or your account |
| Push tokens | Until you sign out, revoke the installation token, or delete your account |
| Abuse reports and participant blocks | Until you delete your account; report status is retained only with the report |
| Rate-limit counters (hashed IP) | Rolling one-hour windows; not kept as history |
| Crash reports | Per Firebase Crashlytics' own retention (90 days) |
6. Deleting your account
You can delete your account from More → Settings → Delete account inside the app.
This is a real deletion, not a deactivation. It removes your profile, your vehicles, your tags, every scan and message attached to them, your notifications, and your login itself. Your QR codes stop resolving immediately. It cannot be undone.
If you cannot access the app, email anas.official2017@gmail.com from the address on the account and we will delete it.
7. Your rights
You can ask us to:
- See the data we hold about you
- Correct anything wrong
- Delete your account and data (or do it yourself, above)
- Export your data in a machine-readable form Email anas.official2017@gmail.com. We will respond within 30 days.
Depending on where you live, these rights may be granted to you by the Digital Personal Data Protection Act, 2023 (India), the GDPR (European Economic Area and UK), or the CCPA/CPRA (California). We apply them to everyone regardless of where you are.
Where the GDPR applies, our legal bases are: contract (running the account and delivering messages you or a scanner send), and legitimate interests (preventing abuse through rate limiting, and fixing crashes).
8. Children
Scan To Move is for people who own or drive a vehicle and is not directed at children under 13. We do not knowingly collect data from them. If you believe a child has created an account, email us and we will remove it.
8a. Our website
- Scan page. When you scan a tag, your browser is given an anonymous session (no name, email or number). It is kept in your browser's local storage so you can come back and read the owner's reply. Clearing your browser data removes it.
- Sticker orders. The order form on our home page does not send anything to us by itself. It prepares an email that you choose to send. We use what you put in it (name, email, delivery address and the vehicle label) only to make and deliver your sticker, and delete it once the order is complete, unless the law requires us to keep invoice records.
- Fonts. Our home page loads fonts from Google Fonts, which means your browser connects to Google and Google can see your IP address. See Google's privacy policy. The scan page and legal pages make no third-party requests.
- We set no cookies and run no analytics on the website.
9. Security
- Every table is closed by default; access is granted per-row to the owner only.
- The lookup used when someone scans a tag runs server-side and returns nothing that identifies you.
- QR tokens are 128-bit random values generated by the server, not by the app.
- Rate limits are enforced in the database, so they cannot be skipped by a modified client.
- IP addresses are salted and hashed before storage.
- Traffic is encrypted in transit (TLS); data is encrypted at rest by Supabase.
No system is perfectly secure. If you find a vulnerability, please email anas.official2017@gmail.com rather than disclosing it publicly, and we will work with you.
10. Changes
If we change what we collect, we will update this page and the "last updated" date, and — for a change that materially affects you — tell you in the app before it takes effect.