What we know about
your information — and
what we don’t.
Facial data, medical information and emergency contacts are as sensitive as personal data gets. This page states what is documented in VerifyU’s own sources, and marks every statement that still needs confirmation from our team.
How to read this page
Each section says what is known, where that knowledge comes from, and what has not been confirmed. Anything carrying an amber Owner verification badge is a statement our engineering team has not yet verified — it is listed as an open question, not presented as fact.
VerifyU supports identification and communication. It does not replace emergency services, and it cannot guarantee that a person will be found, identified or reached.
- The VerifyU privacy policy at verifyu.in
- Feature descriptions published on verifyu.in
- The App Store privacy declaration for VerifyU
- The Google Play data safety section for com.verifyu.app
Your information, section by section
Your face & biometrics
Facial data is one of the categories the privacy policy says VerifyU collects, along with your name, email address, phone number and usage, log and device data. It is collected for identity verification — that is the purpose the policy states.
The privacy policy also states that your data is not shared with third-party service providers. VerifyU does not publish facial data, and verifyu.in states that your data is never publicly visible.
- What
- A face image captured at registration and the facial data derived from it, as described in the privacy policy.
- Why
- So a registered person can be identified in an emergency by a VerifyU user with scanning access.
- Who sees it
- Not the public. A successful match shows emergency-relevant profile information to the scanning user — see “What a successful match may reveal”.
- Your control
- You choose to register. You can request access, correction or deletion through the app settings or by contacting support, as the privacy policy describes.
Per the privacy policy at verifyu.in; “never publicly visible” as described on verifyu.in.
- Whether VerifyU stores the face image, a mathematical face template, or both Owner verification
- Whether face matching happens on the device or on VerifyU servers Owner verification
- Whether any external face-recognition software or model provider is involved in processing Owner verification
- How long facial data is kept after an account is deleted Owner verification
Face verification
Face verification is a step you complete yourself during registration. The app asks for camera access and guides you through on-screen prompts, after your mobile number, photo, personal details, emergency contacts and medical information have been added.
It is what links your face to the profile you created. Registration cannot be completed for someone without their participation in this step.
- What
- A guided camera capture during registration, using the prompts shown in the app.
- Why
- To confirm that the face on the profile belongs to the person registering it.
- Who sees it
- VerifyU, for identity verification as stated in the privacy policy.
- Your control
- You complete the step yourself, and you can stop at any point before submitting.
Per the in-app registration flow shown in the official VerifyU registration guide.
- Whether a liveness or anti-spoofing check is performed during verification Owner verification
- Whether the verification capture is stored separately from your profile photo, or discarded after the check Owner verification
- Whether re-verification is required after you change your profile photo Owner verification
- Whether failed verification attempts are recorded, and for how long Owner verification
Facial matching
Matching is the emergency path: a VerifyU user with scanning access opens the scanner, and the capture is checked against registered VerifyU profiles. It works only where the person has already registered, the image is suitable and there is connectivity.
A match is a possibility, not a promise. VerifyU supports identification and communication — it does not replace emergency services and cannot guarantee that a person will be identified.
- What
- A check of a captured face against registered profiles, initiated by a user with scanning access.
- Why
- To connect a person who cannot communicate to their identity, emergency information and next of kin.
- Who sees it
- The scanning user sees the result. The registered person is alerted in the app when their profile is accessed, as described on verifyu.in.
- Your control
- Only registered profiles can be matched, and medical details on the profile that opens require an OTP verified from one of your own emergency contacts.
Feature behaviour as described on verifyu.in and in the app store listings.
- What happens to a scanned image when there is no match — whether it is stored, and for how long Owner verification
- What accuracy or confidence threshold is used to declare a match, and how near-matches are handled Owner verification
- Whether a match attempt against an unregistered face creates any record Owner verification
- Whether repeated or bulk scanning by one account is rate-limited or blocked Owner verification
Who can scan
Scanning is not open to the public and it is not a feature of the website. It is available inside the app to a VerifyU user with scanning access, and access depends on the plan.
That is the extent of what is publicly documented today. The rules that decide who is granted scanning access — and how that is checked — are not published, so we are not going to describe them as though they were.
- What
- The ability to open the scanner in the VerifyU app and attempt a match.
- Why
- So that a helper, responder or family member can identify someone who cannot speak for themselves.
- Who sees it
- The scanning user sees only what a successful match is permitted to show.
- Your control
- Profile access is logged and you are alerted in the app when your profile is accessed, as described on verifyu.in.
Per the current app store listings and the feature description on verifyu.in.
- The exact criteria for granting scanning access, and whether identity checks are performed on scanning users Owner verification
- Whether organisations such as hospitals, police or event teams receive scanning access, and under what agreement Owner verification
- Whether scanning access can be suspended or revoked, and who decides Owner verification
- Whether a scanning user’s own identity is shown to the person whose profile was accessed Owner verification
What a successful match may reveal
A successful scan opens a screen headed Verified Profile, marked “Scanned securely via VerifyU”. The header carries your photo, your name, your gender and your blood group, and behind it sit three tabs: Personal, Emergency and Medical.
Personal shows the details you entered, such as date of birth and age. Emergency lists the two contacts you chose — name, relation and phone number, each with a call button, under the label “Encrypted & Private”. Medical does not open on its own: the app asks the person scanning to verify an OTP sent to one of your emergency contacts first. verifyu.in also states that your data is never publicly visible.
- What
- A verified-profile header — photo, name, gender, blood group — plus Personal and Emergency tabs. Medical details are gated behind an OTP verified from one of your emergency contacts.
- Why
- To help a stranger act correctly and contact the right people quickly, without handing over your whole medical history to do it.
- Who sees it
- The VerifyU user with scanning access who made the match.
- Your control
- What you put in your profile, and who you list as emergency contacts — because they are the people whose OTP unlocks the medical tab.
Screen behaviour observed in the current app (demo account); “never publicly visible” as described on verifyu.in.
- Whether the field list differs by the scanning user’s plan, role or organisation Owner verification
Medical information
Your profile can hold your blood group, relevant medical history and notes. You enter it during registration and can change it later. Premium is described in the app as full medical data access.
Two different things happen to it. Your blood group is shown up front on the verified-profile header, because it is the detail that changes what a helper does in the first few minutes. Everything under Medical Details is protected: when someone scans you, the app tells them “Medical information is protected” and asks them to verify an OTP sent to one of the emergency contacts you listed. The people you trust are the gate.
- What
- Blood group, medical history and notes that you choose to add.
- Why
- So a helper or clinician has useful information when you cannot give it yourself.
- Who sees it
- Blood group: the scanning user, on the profile header. Medical details: only after an OTP from one of your emergency contacts is verified.
- Your control
- You decide what to add, what to leave out, and who your emergency contacts are — they hold the key to the medical tab.
Blood-group display and the OTP gate observed in the current app (demo account); plan descriptions per the app and the store listings.
- The default visibility of medical information on a newly created profile Owner verification
- Whether individual medical fields can be hidden separately, or only the section as a whole Owner verification
- Whether medical information is stored separately from the rest of the profile, with tighter access controls Owner verification
Emergency contacts
Registration asks for two emergency contacts — their names, relation to you and phone numbers. They are the people a helper is meant to reach when you cannot make the call yourself, and they are also the people whose OTP unlocks your medical details.
In the app they sit under Emergency Contacts, marked “Encrypted & Private”, each with their relation, their number and a call button beside it. Please tell the people you list that you have listed them, and check the numbers once a year. A contact who has changed their number is the most common way this quietly stops working.
- What
- Two contacts: name, relation and phone number.
- Why
- So the people who know you can be reached quickly in an emergency — and so someone who knows you can authorise access to your medical details.
- Who sees it
- A scanning user, who sees the number in full with a call button, within the permitted VerifyU workflow; and the SOS alert flow when you trigger it.
- Your control
- You choose the contacts and can change them in the app at any time.
Per the registration flow and the Emergency Contacts screen in the current app (demo account).
- Whether a person is notified or asked to consent when they are added as your emergency contact Owner verification
- Whether an emergency contact can view any part of your profile Owner verification
- Whether more than two contacts can be added on any plan Owner verification
Location
The App Store privacy declaration for VerifyU lists Location — both precise and coarse — and Contact info as data linked to your identity. verifyu.in also states that scan logs include time, IP and location.
Location matters in two very different situations: an SOS you trigger, where sharing where you are is the point, and a scan of your profile, where the log records where the access happened.
- What
- Precise and coarse location, as declared on the App Store listing, and location recorded in scan logs per verifyu.in.
- Why
- To support emergency alerts and to record where a profile access took place.
- Who sees it
- VerifyU; and your emergency contacts through the SOS and share-location actions you trigger.
- Your control
- Location permission is granted, limited or withdrawn in your phone’s settings.
Per the App Store privacy declaration for VerifyU and scan-log details as described on verifyu.in.
- When location is actually collected — continuously, only in the app, or only during an SOS or a scan Owner verification
- Whose location a scan log records: the scanning user’s device, the person being scanned, or both Owner verification
- How long location data is retained, and whether it is separated from the rest of the profile Owner verification
- Whether your location is ever shown to a scanning user Owner verification
Scan / access logging
verifyu.in states that scan logs include the time, IP address and location of the access. Logging is what makes access to your profile reviewable rather than invisible.
Usage, log and device data are also listed in the privacy policy among the categories VerifyU collects, for account management, support and improving the service.
- What
- A record of profile access, including time, IP address and location, as described on verifyu.in.
- Why
- Accountability: so an access to your profile can be examined afterwards.
- Who sees it
- VerifyU. You are alerted in the app when your profile is accessed.
- Your control
- You can ask VerifyU what has been recorded about your profile through privacy support.
Scan-log contents as described on verifyu.in; log and device data per the privacy policy.
- Whether the full access history is visible to you inside the app, and how far back it goes Owner verification
- How long scan and access logs are retained Owner verification
- Whether the log shows you who scanned your profile, or only that an access occurred Owner verification
- Whether you can dispute or report an access you believe was improper, and what happens then Owner verification
User notifications
verifyu.in states that you receive an in-app alert when your profile is accessed. The app also has push notifications and SOS alert preferences in its settings.
An alert is how you find out that the system did something on your behalf. We are not going to describe it as instant or guaranteed, because delivery depends on connectivity, permissions and your device.
- What
- An in-app alert when your profile is accessed, plus notification and SOS alert settings.
- Why
- So access to your identity is not silent.
- Who sees it
- You, on your registered device.
- Your control
- Notification preferences in the app and permissions on your phone.
In-app access alert as described on verifyu.in; notification settings per the current app.
- Whether the access alert is also delivered as a push notification, an SMS or an email Owner verification
- Whether the access alert can be switched off, and whether emergency access can suppress it Owner verification
- How quickly the alert is sent after an access, and what happens if your device is offline Owner verification
- Whether your emergency contacts are notified when your profile is accessed Owner verification
Children & guardian profiles
The privacy policy states that the service is intended for people aged 13 and over, and that children under 13 are covered through a parent’s or guardian’s account. Registration lets a parent add children’s details to their own profile.
A child who cannot explain who to call is exactly the person this is for — and also the person whose information most needs an adult in charge of it.
- What
- Children’s details added by a parent or guardian to their own VerifyU profile.
- Why
- So a separated or distressed child can be connected back to their family.
- Who sees it
- A scanning user, within the permitted VerifyU workflow.
- Your control
- The parent or guardian manages the dependant’s details and can change or remove them.
Ages 13+ and parental accounts per the privacy policy at verifyu.in; dependant details per the registration flow.
- Whether a child’s face is registered and matchable, or only their details are stored Owner verification
- What a scanning user sees when a child’s profile is matched Owner verification
- What happens to a dependant profile when the child turns 13 or 18 Owner verification
- How age is checked at sign-up, and what happens if an under-13 registers independently Owner verification
Data storage
verifyu.in states that VerifyU’s servers are in India, on AWS. The privacy policy states that your data is not shared with third-party service providers.
Hosting location is a fair question to ask of any identity product, and it is the one infrastructure detail currently stated publicly. The rest of the picture is not published, so it is listed below as unconfirmed rather than described.
- What
- Profile, facial, medical, contact, location and log data held by VerifyU.
- Why
- To run the service described in the privacy policy: your account, support, improvement and identity verification.
- Who sees it
- VerifyU. The privacy policy states data is not shared with third-party service providers.
- Your control
- Access, correction and deletion requests through the app settings or privacy support.
Servers in India on AWS as described on verifyu.in; sharing statement per the privacy policy.
- The AWS region used, and whether any data is stored or backed up outside India Owner verification
- Whether data is encrypted at rest, and with what key management Owner verification
- Which sub-processors, if any, are used for hosting, analytics, messaging or crash reporting Owner verification
- Whether any processing takes place outside India, for example by support staff or contractors Owner verification
Retention
The privacy policy states that data is kept for as long as necessary for the purposes described, or as required by law, and is then deleted or anonymised.
That is the legal shape of the answer, not the operational one. No fixed retention period is published for any category of data, and we are not going to invent one here.
- What
- Every category: account details, facial data, medical information, contacts, location and logs.
- Why
- To provide the service and to meet legal obligations, per the privacy policy.
- Who sees it
- VerifyU, for as long as the data is held.
- Your control
- You can request deletion — see “Deletion” below.
Retention language per the privacy policy at verifyu.in.
- The exact retention period for facial data Owner verification
- The exact retention period for scan and access logs, and for location data Owner verification
- What is retained after an account is deleted, and for how long Owner verification
- What “anonymised” means in practice for face data, and whether anonymised records are kept indefinitely Owner verification
Correction
The privacy policy states that you can access and correct your information through the app settings, or by contacting VerifyU.
Correction is not a formality on a safety product. An old phone number for a next of kin, or a blood group typed in a hurry, is the failure nobody notices until the day it matters.
- What
- Your name, contact details, emergency contacts, medical information and dependants.
- Why
- Because out-of-date emergency information is worse than none: it sends a helper in the wrong direction.
- Who sees it
- You, in the app. Corrections apply to what a future match can show.
- Your control
- Edit in the app settings, or write to privacy support if a field cannot be changed there.
Access and correction rights per the privacy policy at verifyu.in.
- Which fields can be edited in the app and which require a support request Owner verification
- Whether changing your profile photo requires face verification again Owner verification
- How long a correction request takes to be actioned Owner verification
- Whether a history of previous values is kept after a correction Owner verification
Deletion
The Google Play data safety section states that users can request that their data be deleted. The privacy policy states that deletion can be requested through the app settings or by contacting VerifyU.
If you want to leave, you should be able to leave. Start at the account deletion page, which sets out the request route.
- What
- Your account and the data held with it, including facial data.
- Why
- Because registering was your choice, and so is stopping.
- Who sees it
- Your privacy support request is handled by VerifyU.
- Your control
- Request account deletion, or write to info@beaufortit.com.
Deletion request route per the Google Play data safety section and the privacy policy at verifyu.in.
- Whether a one-tap account deletion exists inside the app, or whether deletion is request-based only Owner verification
- How long deletion takes once requested, and whether you receive confirmation when it is done Owner verification
- Whether facial data is deleted immediately, or on the same schedule as the rest of the account Owner verification
- What is retained after deletion for legal or log-keeping reasons Owner verification
Security
The Google Play data safety section states that data is encrypted in transit. That is the only security property currently stated in a public source, and it is the only one we will state here.
VerifyU does not claim to be unhackable, 100% secure or end-to-end encrypted, and no security certification is claimed — we hold none that we can point to. Anyone telling you otherwise about this product is not speaking for us.
One label in the app needs saying out loud: the Medical Details card is marked “HIPAA Compliant”. HIPAA is a United States health-privacy law and is not the framework that governs an Indian service, so that label is with our legal team for review rather than offered here as a compliance claim. Legal review
- What
- The protection applied to your data in transit and at rest.
- Why
- Because facial and medical data deserve serious handling.
- Who sees it
- VerifyU staff access is not described in a public source; see below.
- Your control
- Keep your device locked, your app updated and your emergency information current.
Encryption in transit per the Google Play data safety section for com.verifyu.app.
- Whether data is encrypted at rest, and how encryption keys are managed Owner verification
- Which VerifyU staff can access profile, facial or medical data, and under what controls and logging Owner verification
- Whether independent security testing or a penetration test has been carried out Owner verification
- Whether a breach notification process exists, and how users would be informed Owner verification
- Whether any security or privacy certification is held (none is claimed today) Owner verification
Legal / government requests
The privacy policy states that data may be retained where required by law. Beyond that, VerifyU does not currently publish a process for handling requests from police, courts or government bodies, and no transparency report is published.
We are saying that plainly rather than describing a process that we cannot show you.
- What
- Requests from law enforcement, courts or government authorities for user data.
- Why
- Legal obligations that apply to any company operating in India.
- Who sees it
- Not published today.
- Your control
- You can ask privacy support what has been disclosed about you.
Legal retention language per the privacy policy at verifyu.in.
- Whether a formal process exists for receiving and reviewing government or police requests, and who reviews them Owner verification
- Whether VerifyU requires a warrant, court order or other legal instrument before disclosing data Owner verification
- Whether users are notified when their data is requested or disclosed, where the law permits Owner verification
- Whether a transparency report will be published, and how often Owner verification
Privacy support
Ask us. Questions about your information, an access you did not expect, a correction, or a deletion request all go to the same place, and a person answers them.
- What
- Privacy questions, access and correction requests, deletion requests and complaints.
- Why
- Because a rights page that does not end in a working contact is decoration.
- Who sees it
- The VerifyU team at Beaufort IT Solutions Pvt. Ltd..
- Your control
- Email info@beaufortit.com or message +91 82990 44462 on WhatsApp.
Contact details per the current site; rights per the privacy policy at verifyu.in.
- Whether a grievance officer or data protection officer is formally designated, and their name and contact Owner verification
- The response time VerifyU commits to for privacy and deletion requests Owner verification
- The escalation route if you are not satisfied with the response Owner verification
This page describes what is published today. Where a section is marked as unconfirmed, the honest answer is that we do not yet have it in writing from the people who build the system — and we would rather show the gap than fill it with reassuring language.
Questions about your information?
A person reads these. Ask about an access you did not expect, a correction, or deletion.