What is public, and what stays private.
PraniID exists to make some animal information public — a photograph, a name, a way to make contact — while keeping the rest inside your organisation. This page says exactly where that line sits.
1. The two kinds of data
Every PraniID record has two sides. Account data — your organisation's registry, medical notes, audit log and staff accounts — is visible only to signed-in members of your organisation, plus platform administrators for support and safety. Public profile fields are the small subset a care team deliberately publishes so a finder can help: name, species, breed, photograph, summary badges, and whichever contact options the team enables.
Nothing becomes public by accident. A field appears on a public profile only when the record's visibility settings allow it, and those settings can be changed at any time.
2. What an animal's public profile shows
| Field | Public? |
|---|---|
| Name, species, breed, age, sex, photograph | Yes — this is the point of the profile. |
| Vaccination and sterilisation badges | Yes, at summary level, such as "vaccinated". Full histories with batch numbers stay in the console. |
| Caretaker phone number | Shown whenever the animal is marked lost, so a finder can call — this cannot be switched off. Otherwise it depends on whether the record publishes it, and it is always shown for stray and community animals. |
| Guardian name | Shown as "Registered Guardian" or "Community Caretaker" to strangers unless the team publishes the name. |
| Address or landmark | Not published by an organisation. Address hiding is an individual-account control and individual accounts are closed. What an organisation publishes instead is the city or area. |
| Medical, dietary and emergency notes | Only when the team enables public sharing for them. Otherwise the page says the notes are private. |
| Internal notes, audit log, staff accounts | Never public. |
| Other people's sighting reports | Never public. A sighting goes to the guardian and the holding organisation only. |
One thing is worth knowing before you publish anything. A shelter cannot hide its own address from a finder, and that is deliberate: an address withheld from the person holding an animal does not protect the shelter, it only makes the animal harder to return. To be unreachable, switch the animal's public passport off — then nobody scanning the tag can open the profile at all.
3. Sighting GPS locations
When a finder submits a sighting from a public profile, their phone sends its GPS location with the report. That location goes to the animal's guardian and organisation only. It is never published on the public page, never written to the sitemap, and never visible to another visitor — the sighting table is readable only by members of the organisation holding the animal.
Sighting reports appear inside the console, where the care team can review and update them. The finder is told on the form itself that their location is shared with the care team and nobody else.
How long sighting coordinates are kept, and when they are deleted, is not yet defined in this policy. That gap is flagged for legal review against the Digital Personal Data Protection Act 2023 and is tracked in the repository handover notes rather than hidden here.
4. Organisation applications
Applying for access asks for organisation details: name, type (shelter, NGO, gaushala), city, contact person, and supporting information about the organisation. Applications are reviewed by platform administrators — people checking that the applicant is a genuine care organisation. Application details are never published and never shared with other organisations.
5. Local storage and analytics
Your browser stores the installed app itself and the icons it needs to launch, which is why an installed PraniID opens without a connection. Animal records are not held on the device: they are fetched from the server each time you open one. Clearing site data removes the stored app copy and logs you out.
The public pages use Cloudflare Web Analytics, which measures visits without cross-site tracking cookies. There are no advertising trackers and no data is sold. Account sessions use strictly necessary authentication cookies.
6. Your rights under India's DPDP Act, 2023
The Digital Personal Data Protection Act, 2023 gives you rights over your personal data: to know what is held, to correct it, to erase it, and to nominate someone to act for you if you cannot. To exercise any of these, ask the organisation that holds your record — they can correct it, export it, or remove it from the console directly.
Organisations can export their registry as CSV at any time. Deletion removes public profiles, so a linked QR tag stops resolving to personal data.
A named grievance officer is not yet published. That is required by the Act and is an outstanding item, flagged in the repository handover notes rather than filled with a placeholder address.
7. Security of stored data
Records live in a secured database with role-based access: staff see only their own organisation's animals, volunteers can be limited to a narrow set of actions, and every change is written to an audit log. Public pages are served through an allow-list that exposes only the fields described in section 2, so a bug in the interface cannot leak a phone number — the number never leaves the database for a caller who is not allowed to see it.
8. Changes to this policy
If this policy changes materially, organisations are notified in the console and this page is updated. The version that matters is the one on this page today.