⏳
Rate limits
Repeated messages, calls and emergency attempts are restricted per connection and tag.
Safety and privacy
A vehicle can be public. Its owner's personal number should not be.
TagVomo is designed around controlled communication: limited public data, contextual actions, temporary access, abuse limits and owner-controlled preferences.
🚗 Car QR ₹499🏍️ Bike QR ₹249👦 Child Tag ₹299🐾 Pet Tag ₹349🔑 Key Tag ₹249First year included · Yearly renewal by category
Privacy model
The scanner contacts a vehicle identity—not a personal phone number.
The public tag endpoint returns only the information needed to confirm the vehicle and choose an action. Stored mobile numbers are not returned on the public page.
Publicly availableLimited vehicle label, supported contact actions and emergency availability
Not publicly returnedOwner mobile, scanner mobile, home address and stored emergency phone
Owner-controlledDND, call availability, emergency profile and tag status
Time-limitedPrivate conversation access expires after the incident window
Abuse prevention
Multiple layers between a scan and unwanted contact.
🔕
Do Not Disturb
Owners can block call requests while continuing to receive useful text alerts.
🔗
Expiring access
The scanner’s reply token works for the current incident, not as a permanent owner contact.
#
Hashed telemetry
IP address and user-agent signals are hashed for abuse analysis instead of shown to owners.
🧹
Retention boundary
Temporary abuse telemetry is removed after the configured retention period.
✅
Consent gates
Activation, emergency profile and incident-location sharing require explicit consent.
Safety across categories
Privacy rules stay consistent whether the tag is on a car, collar, school bag or laptop.
The scanner gets only the action page. Stored phone numbers and sensitive owner details stay behind controlled relay workflows.
Emergency design
Urgent information without turning the sticker into a public medical card.
Emergency data is separated from normal contact and shown only when the owner enables the profile.
1
Owner chooses availability
The emergency profile is disabled by default and can be switched on or off.
2
Only selected context appears
Blood group and owner name appear only when the owner has chosen to share them.
3
Contact stays behind a relay
The stored emergency phone is not returned by the public API.
4
Emergency services remain primary
TagVomo is a notification aid, not a replacement for police, ambulance or roadside authorities.
Data map
Why each data point exists.
| Data | Purpose | Visible to scanner? | Control |
|---|---|---|---|
| Vehicle registration | Confirm the intended object or vehicle | Limited display | Owner/operator |
| Owner mobile | Receive alerts or relay calls | No | Private system data |
| Scanner mobile | Verify a requested masked call | No | Hashed/session use |
| Message content | Explain the incident | Shared with owner | Temporary thread |
| IP/user-agent hash | Rate limiting and abuse review | No | Retention-limited |
| Incident location | Towing or accident context | Owner only | Explicit scanner consent |
Production transparency
Security also means being clear about what is live.
Live corePrivacy-safe public API
Owner phone is excluded from public responses.
Live coreRate limits and expiry
Applied to contact and call-request routes.
ConfigurationMasked voice
Requires production voice provider credentials.
ConfigurationOTP/WhatsApp
Requires verified regional delivery providers.
Safety FAQ
Direct answers to privacy questions.
Does scanning reveal the owner’s phone number?
No. The public scan page and public tag API do not return the stored owner number.
Can every scanner request a phone call?
A scanner must provide a valid international number for verification, requests are rate-limited, and owner DND can block the action. Actual masked connection also requires a configured voice provider.
Do you store a raw device ID?
The current system stores a salted hash of network and user-agent signals for temporary abuse control, not a permanent hardware identifier.
Can emergency details be disabled?
Yes. The owner controls whether the emergency profile is enabled and which limited fields can appear.
Privacy is part of the utility
Get protected →