Your information. Your vehicle identity. Your control.
This Privacy Policy explains how VaahanSafe handles information across your account, vehicle identity, QR activation, public safety view, and related services.
Effective:March 15, 2026
Version:1.0
Active Architecture
Information Boundary Architecture
Private Account → Owner Control → Public Safety View
01 / ACCOUNT DOMAINPrivate
Private Account
Your fundamental account records remain strictly isolated. They are never exposed to QR finders or public viewers.
Residential delivery address
Account email address
Authentication credentials & logs
Billing history & payment tokens
STATUS: ARCHITECTURALLY CONCEALED
02 / CONTROL BRIDGEOwner Control
Your Choices
You decide which supported safety information crosses into the public projection.
Choose supported emergency contacts
Toggle medical blood group visibility
Enable masked voice / SMS relay options
Update or pause projection anytime
POLICY: ZERO DEFAULT EXPOSURE
03 / RESOLVER PROJECTIONPublic View
Public Safety View
Only the designated safety details are projected when someone scans the vehicle's physical QR code.
Vehicle context (make, model, type)
Selected emergency contact relay
Blood group (if optional entry provided)
Critical safety or medical notes
SURFACE: qr.vaahansafe.com
Key Assurance: A QR scan reveals the configured safety view—never your private address, login details, or billing account.
Privacy Policy•13 Sections
01 / Introduction
Privacy at VaahanSafe
This Privacy Policy explains how VaahanSafe handles information across your account, vehicle identity, QR activation, public safety view, and related services.
Core Privacy Principle: Private Account vs. Selective Safety View
VaahanSafe is built around a deliberate architecture: your underlying account and sensitive personal records remain private, while you retain continuous control over the limited safety details made accessible when your vehicle's physical QR is scanned.
We believe vehicle safety should not require exposing your residential address, private travel history, or complete personal profile to every person who scans a sticker on your vehicle.
Scope of This Policy
This policy applies to individuals who access our public web portal (vaahansafe.com), activate physical stickers (activate.vaahansafe.com), scan registered QR codes (qr.vaahansafe.com), or manage their vehicles through the customer application (app.vaahansafe.com).
By accessing or using any VaahanSafe service, you acknowledge the handling of information described in this policy.
02 / Information We Collect
Information we handle
VaahanSafe handles distinct categories of information necessary to maintain account security, verify physical sticker ownership, and present your configured safety view.
Account Information
When you register an account with VaahanSafe, we collect information necessary to authenticate your identity and administer your services.
Verified mobile phone number (used for one-time passcodes and urgent relay notifications)
Account name or display moniker
Email address (optional or required based on notification preferences)
Authentication credentials and active session state tokens
Vehicle Information
To link a physical QR sticker to a vehicle, we handle basic vehicle contextual information supplied during onboarding or management.
Vehicle type and category (e.g., Two-Wheeler, Four-Wheeler, Commercial, Helmet)
Vehicle registration number or nickname
Make, model, and color for visual recognition by responders
Safety Profile & Emergency Contacts
You choose what supported safety information to attach to your vehicle's identity. These items are strictly controlled by your configuration.
Primary and secondary emergency contact names and phone numbers
Blood group (optional, provided solely for medical emergency assistance)
Important safety or medical notes (e.g., allergies, critical vehicle emergency notes)
Privacy projection settings designating which fields are active on the public safety view
QR Identity & Activation Data
Every physical sticker possesses unique technical metadata separating its public lookup locator from its ownership verification credentials.
Public QR Identifier (the random, non-sequential alphanumeric string physically printed and encoded in the QR code)
Sticker lifecycle state (e.g., manufactured, in-transit, activated, suspended, replaced)
Verification timestamp and activation proof submitted during initial retail or online setup
Order & Shipping Information
If you purchase a VaahanSafe physical kit or renewal plan directly from our web portal, we process details required to fulfill delivery.
Shipping address and pin code for physical sticker packet delivery
Transaction status and payment processor confirmation reference (payment card and banking credentials are handled directly by PCI-compliant payment partners; VaahanSafe does not store full card numbers or UPI PINs)
Order history and subscription entitlement status
Service Activity & Scanner Interaction
When a QR code is scanned by a third party (such as a helpful bystander, parking attendant, or emergency responder), our resolver logs minimal diagnostic information.
Timestamp of the scan event
Masked IP address and generalized browser user-agent for fraud prevention and abuse protection
Relay action triggered (e.g., call initiated, parking alert sent) to notify the owner of interaction
We process information solely for specific, legitimate purposes linked directly to operating the vehicle safety identity platform.
Authorized Processing Purposes
Information collected by VaahanSafe is used exclusively for the following purposes:
Generating and resolving the configured Public Safety View upon authorized QR scan
Routing masked voice or SMS notifications between vehicle discoverers and owners without exposing direct personal phone numbers unless explicitly designated
Verifying sticker authenticity and ownership during retail kit activation
Processing fulfillment, shipping, and replacement of physical reflective QR decals
Detecting fraudulent scans, bot scanning attacks, and unauthorized claim attempts
Communicating critical service announcements, security alerts, and subscription status updates
Complying with applicable laws, judicial orders, and regulatory directives in India
No Data Selling or Advertising Networks
VaahanSafe does not sell, rent, or lease your personal information, emergency contacts, or vehicle details to third-party data brokers or marketing aggregators.
Your safety profile is processed exclusively to deliver emergency connectivity and vehicle identity services.
04 / Public Safety View
The public safety view is not your account
When someone scans your vehicle QR sticker, they see only the specific safety details you have configured—never your private account, home address, or billing records.
The Architectural Privacy Boundary
A fundamental principle of VaahanSafe is the strict separation between your Private Account and your Public Safety View. Scanning your QR code loads a lightweight, read-only resolver interface (qr.vaahansafe.com).
The resolver does not require the finder to log in or create an account to view emergency instructions, ensuring immediate availability during an accident or parking obstruction.
Your residential address, billing records, payment methods, login credentials, and unlinked personal vehicles are architecturally isolated and never exposed through the QR resolver.
Granular Visibility Choices
Through the VaahanSafe customer application, you determine which emergency information fields are projected on the public view.
For example, you may choose to display an emergency contact phone number, route calls through our relay system, or show only essential medical notes like blood group.
Signature Architectural Invariant
REF / SAFETY-VIEW-SEPARATION
The public safety view is not your account.
When a VaahanSafe QR is scanned, the public experience is designed around the supported information you have chosen to make available for that vehicle. A scan connects a responder to your vehicle safety view—it does not provide access to your private profile, address, or billing history.
STEP 01Private
Private Account
• Residential address
• Account email & passwords
• Transaction details
STEP 02Control
Owner Control
• Toggle emergency relays
• Optional blood group
• Emergency medical notes
STEP 03Public
Selected Safety View
• Only selected details
• Masked contact relay
• Zero-login access for finder
Visibility choices may be updated through the applicable VaahanSafe account controls.
05 / QR Activation & Ownership
Public QR identity vs. Activation credentials
Scanning a public QR code allows viewing the safety profile, but does not grant the right to claim, modify, or transfer vehicle ownership.
Separation of Public Identifier and Claim Proof
In both retail stickers and online-purchased kits, the public QR code represents a public locator only. It does not contain or encode the secret credentials needed to activate or claim the sticker.
For retail packs, ownership verification requires physically scratching or revealing a separate, concealed activation token that is permanently linked to the sticker in our manufacturing database.
Once activated, that activation credential is invalidated and cannot be reused by another party to hijack your vehicle's identity.
Replacement Stickers & Transfer
In the event of vehicle sale, windshield replacement, or decal wear, replacement stickers follow a strict re-authentication and de-linking workflow to ensure old public locators are securely retired.
LEGAL REVIEW REQUIRED: Align replacement de-linking language with the final fulfilment and replacement SLA policy.
Ownership & Activation ArchitecturePUBLIC QR ≠ ACTIVATION PROOF
Public QR Identifier
Physically printed on the reflective decal. Serves only to route scanners to your configured safety view. It contains zero private account details and cannot be used to modify ownership.
≠
Concealed Activation Proof
Separated under a tamper-evident scratch layer or secure digital order token. Required exclusively during initial setup to claim vehicle identity. Once linked, it cannot be reused.
This architectural separation ensures that even if an unauthorized bystander photographs your vehicle sticker, they cannot alter your emergency contacts, hijack your subscription, or access your customer account.
06 / Information Sharing
When information may be shared
We share information with external entities strictly as necessary to execute requested transactions, deliver emergency relays, or comply with legal mandates.
Service Providers and Infrastructure Partners
We engage reputable technology and operational vendors who process information under contractual confidentiality and security commitments:
Telecommunications and SMS Providers: To deliver one-time verification passcodes, emergency alerts, and vehicle notification relays (e.g., MSG91 or equivalent certified telecom partners).
Payment Processing Partners: To process payment transactions in compliance with Reserve Bank of India (RBI) tokenization guidelines (e.g., Cashfree Payments).
Cloud & Content Delivery Infrastructure: To host edge resolver instances and distributed databases with high uptime and low latency across India (e.g., Cloudflare Inc.).
Courier & Logistics Partners: To deliver physical reflective QR sticker packages to your designated shipping destination.
Legal Obligations and Emergency Protection
We may disclose records if required to do so by applicable law, warrant, court order, or formal request from lawful authorities in India.
We may also disclose necessary details in good faith where we reasonably believe disclosure is critical to prevent imminent physical harm, preserve life in emergency response scenarios, or defend the integrity of our platform against malicious attacks.
07 / Data Retention
Information lifecycle and retention
We retain information only as long as necessary to provide active vehicle safety services, resolve disputes, and fulfill statutory tax and legal obligations.
Retention Principles
Account & Vehicle Records: Maintained for the duration of your active vehicle registration and customer relationship with VaahanSafe.
Emergency Contact Data: Stored while configured by you and immediately removed from the active public resolver upon account deletion or vehicle de-registration.
Transaction & Billing Records: Retained in accordance with Indian commercial, accounting, and tax compliance requirements.
Operational Diagnostic Logs: Retained on a rolling, time-bounded schedule to monitor service availability and combat automated malicious traffic.
LEGAL REVIEW REQUIRED: Confirm specific retention durations under statutory tax and digital data governance guidelines before finalizing.
08 / Security & Protection
Protecting your account and vehicle identity
VaahanSafe implements administrative, technical, and physical safeguards designed to protect personal and emergency data against unauthorized access, loss, or misuse.
Security Safeguards
All communication across our web portal, customer application, activation flows, and QR resolvers is encrypted in transit using industry-standard Transport Layer Security (TLS 1.3).
Customer accounts are protected by multi-factor authentication via cryptographically generated One-Time Passcodes (OTP) sent to verified mobile numbers.
Database access is restricted using strict role-based access controls (RBAC) and least-privilege security boundaries across internal operations.
Honest Limitation on Absolute Security
While we take rigorous measures to safeguard your vehicle identity and personal information, no online service or method of electronic storage can guarantee absolute security.
We urge you to protect your phone, never disclose your OTPs or concealed retail activation scratch codes, and notify us immediately if you suspect unauthorized access to your account.
09 / Your Choices & Rights
Your information should remain understandable and manageable
You hold direct control over your vehicle identity, emergency profile visibility, and personal account data.
Actionable Privacy Controls
Through the VaahanSafe Customer Portal (app.vaahansafe.com), you can exercise the following choices at any time:
Access & Review: Inspect all personal, vehicle, and emergency details associated with your account.
Toggle Visibility: Enable or disable specific fields from appearing on the public QR scan screen.
Suspend or Replace: Temporarily pause public resolver responses or unlink a retired sticker.
Account Deletion: Request complete closure of your account and purge of non-statutory personal records.
Statutory Rights in India
Users in India are entitled to seek clarification, access, correction, and grievance redressal regarding the processing of their digital personal data in accordance with applicable Indian privacy regulations.
LEGAL REVIEW REQUIRED: Incorporate exact statutory grievance officer contact details and DPDP Act provisions once implementation rules are notified.
Privacy Controls Index
Your information should remain understandable and manageable.
Use the following direct shortcuts to review or update your privacy preferences within the customer portal:
Our services interface with specialized infrastructure partners for payments, telecommunications, and mapping.
External Services Context
When you interact with third-party payment gateways, courier tracking links, or external status pages, those third parties operate under their respective privacy policies.
We encourage you to review the privacy documentation of any external service provider you interact with outside the direct vaahansafe.com domain perimeter.
11 / Children's Privacy
Protection of minors
VaahanSafe is designed for adult vehicle owners, drivers, and registered guardians.
Minimum Age and Parental Responsibility
Our services are intended for individuals who have reached the age of majority and are legally permitted to operate motor vehicles or hold property titles under Indian law.
We do not knowingly solicit or collect personal information from individuals under the legal age threshold. If you become aware that a child has provided us with personal information without parental consent, please contact us for immediate deletion.
LEGAL REVIEW REQUIRED: Confirm specific age threshold under DPDP Act provisions (18 years) and parental consent requirements for minor-operated vehicles.
12 / Changes to Policy
Revisions and update notices
We may update this Privacy Policy periodically to reflect enhancements in vehicle safety features, regulatory directives, or operational practices.
Revision Procedures
When changes are made, we will update the 'Effective Date' and 'Version' metadata at the top and bottom of this document.
For material modifications that meaningfully alter how we handle your personal information, we will provide prominent notice through the customer application or via SMS/email notification prior to the change becoming effective.
Your continued use of VaahanSafe following notification of updates constitutes acknowledgment of the revised Privacy Policy.
13 / Contact & Requests
Questions about your information?
If you have a question, request, or concern regarding your privacy or data handling, reach out to our dedicated privacy and grievance desk.
Official Communication Channels
We are committed to addressing privacy inquiries promptly and transparently. You may contact us through our official support and grievance channels:
Grievance Officer: Designated under Indian IT and Digital Data Protection guidelines (Contact via support portal)
Postal Communications: VaahanSafe Technologies, Customer Care & Privacy Desk, India
LEGAL REVIEW REQUIRED: Insert registered corporate address and named Grievance Officer details before production release.
13 / Contact & Grievances
Questions about your information?
If you have a privacy question, want to request data rectification, or wish to exercise any of your rights under Indian privacy governance, reach out to our dedicated privacy desk.
Effective: March 15, 2026•Version: 1.0•Republic of India
Notice for Legal & Compliance Review: This document represents the functional privacy architecture and data-handling invariants of the VaahanSafe platform. Specific statutory clauses under the Digital Personal Data Protection Act (DPDP) and corporate identifiers should be validated by counsel prior to final regulatory deposition.