1. The Windshield Vulnerability: Physical Exposure in Public Spaces
Vehicle owners frequently display visiting cards or phone numbers on their dashboards to resolve parking obstructions or facilitate roadside emergencies. However, physical cards create an uncontained vector of persistent exposure. A car parked outside a gym, school, or residence broadcasts who owns the vehicle, where they work, their mobile number, and often their residential address.
In metropolitan areas, predatory data brokers and automated harvesting rings systematically photograph dashboards in shopping mall parking lots. These harvested phone numbers are cross-referenced with leaked databases to build comprehensive behavioral dossiers on vehicle owners, resulting in targeted spam, extortion attempts, and stalking.
2. The Three-Tier Architectural Boundary Model
To eliminate this risk, VaahanSafe enforces a three-tier isolated security architecture:
Tier 1: Private Account Core (Encrypted Relational Truth)
Resides exclusively on server-side Cloudflare D1 databases. Contains legal owner name, verified billing records, KYC documentation, and account credentials. This tier is accessible only via HttpOnly authenticated sessions and is never exposed to public network gateways.
- End-to-end encrypted at rest using AES-256
- Never queried by public scanner endpoints
- Strict role-based access control (RBAC)
Tier 2: Owner Security Controls (Dynamic Privacy Toggles)
Provides vehicle owners with real-time control over their public profile. Owners can selectively enable or disable emergency voice relays, parking assistance prompts, or verified medical context with a single tap in the customer app.
Tier 3: Public Safety View (Zero-Exposure Projection)
The dynamic projection returned when a passerby scans the physical decal. Displays only anonymized action triggers: 'Call Emergency Contact', 'Notify Driver to Move Vehicle', or 'View Emergency Medical Flags'. Zero raw phone numbers or personal names exist in the rendered HTML or API payloads.
3. Compliance with the DPDP Act 2023: Purpose Limitation and Data Minimization
India's Digital Personal Data Protection (DPDP) Act 2023 establishes stringent legal obligations for Data Fiduciaries. Section 4 mandates that personal data must only be processed for specific, lawful purposes for which the Data Principal has provided clear consent. Section 7 enforces Data Minimization: entities must not process more personal data than is strictly necessary to achieve the designated purpose.
Displaying a raw phone number to solve a temporary parking block violates data minimization, as it permanently surrenders privacy to achieve a transient notification. VaahanSafe enforces purpose-limited communication: once the call or notification completes, no lingering PII remains in the responder's possession.
Under Section 33 of the DPDP Act, failure to implement reasonable security safeguards carries financial penalties up to ₹250 crore. Utilizing masked zero-exposure relays ensures commercial fleet operators maintain complete statutory compliance.
4. Masked Telephony Architecture: How Virtual DIDs Work
When a bystander initiates an emergency call from a scanned vehicle profile, the system executes a secure telephony handshake:
Instead of revealing the owner's phone number, the browser connects to an edge-routed Cloudflare Worker that provisions an ephemeral virtual Direct Inward Dialing (DID) bridge via telecom gateways (MSG91 / Twilio). The gateway dials both parties simultaneously and bridges the audio stream. Both the caller and the recipient see only the platform's trusted caller ID.