Choose what’s shared.
Keep control of the rest.
HopeTag separates the ability to identify a tag from the permission to access or change a person’s information.
Three visibility settings
| Setting | Who can see it |
|---|---|
| Public | Anonymous scanners when the tag is active and in Public mode, authorized caregivers, and authorized institution users. |
| Verified institution | Authorized caregivers and approved clinicians or officers in a verified institution. |
| Caregivers only | Authorized caregivers. A verified institution user needs a separately audited medical-emergency access operation. |
New fields, medical information, photos and dates of birth start as Caregivers only. A tag’s Public setting never overrides a field’s more restrictive visibility.
A private tag stays private.
A Private tag returns a neutral message on an anonymous scan. Invalid, suspended, lost, replaced and deactivated tags do not reveal profile information either. There is no anonymous public-code search.
Possession is not ownership.
Knowing a QR address, public code, a person’s name or even holding the bracelet never grants editing permission. Only a signed-in caregiver with an active Owner or Manager relationship can change the profile. A Viewer can read but cannot edit.
Your activation secret has one job.
The separate secret connects a newly manufactured tag to an authorized caregiver’s profile. It expires, is protected by attempt limits, and becomes unusable after activation. Only its cryptographic hash is stored.
Changes and protected access leave a record.
Profile change records contain the authenticated user, time, action and changed field names. They do not contain sensitive before-and-after values. Institution searches and protected views also create records, including the purpose and any emergency-access reason.
Deactivating a profile or tag retains its history. It is not a request to erase historical data. The website operator can explain the retention arrangements for your deployment.
Protecting information in storage
Profile text, dates of birth, photos, contact details and medical details use application encryption. Account passwords are hashed. Authentication uses a protected session cookie; the client does not save authentication tokens or profile information to browser storage.
Questions about your information?
Contact the website operator through the available support options. Do not include medical details, passwords or private activation secrets in an ordinary support message.
View support options →