Security

Security at Dana: who can see your pet’s record

A pet record is a small thing with a lot of people around it: a partner, a sitter, a parent, an ex. Most of the security that matters here is not cryptography. It is who can open what, and whether you can see when that changed.

Dana the mascot dog sitting calmly in a warm room with one paw resting on the closed lid of a cream record box

Access is a role, not a password you pass around

Everyone you invite gets their own account and their own role. An owner runs the pet, a caregiver logs care, a limited caregiver sees only the parts you pick. Nobody shares a login, so nobody has to change one when a sitter moves on.

That separation is enforced on the server, per row, not by hiding buttons in the app. A request for a pet you have no role on does not come back empty; it does not come back at all.

Access that ends without you remembering

Sitter access can carry an end date and close itself. This exists because the usual failure is not a break-in, it is a permission nobody revoked: the dog walker from two summers ago is still on the account, and nobody has thought about it since.

Invites and ownership transfers expire on their own for the same reason. A link that lives forever is a link that eventually reaches someone you did not mean.

You can read the access history

Invites, accepted invites, removals, role changes and ownership transfers land in one account activity feed with who and when. A shared account is only trustworthy if you can answer "who was let in, and when" without asking anyone.

What is encrypted, plainly

Traffic between the app and Dana runs over HTTPS. The managed database and file storage encrypt at rest. On your phone, credentials sit in the operating system’s own secure storage rather than in a file the app invented.

That is the honest extent of it. Dana does not claim end-to-end encryption, because it would not be true: the server processes your records to send reminders, resolve shared timelines and answer AI checks.

Some things never leave your phone

The walk summary estimates how far you moved, not just the dog. That number is worked out on your device from the walk you just finished and stays there — never uploaded to Dana, never sent to analytics. It is your health data, and the cheapest way to protect it was to never collect it.

Getting your data out, or getting rid of it

Export everything, or delete the account, from inside the app on every tier including the free one. Deletion is a real deletion on a stated schedule rather than a flag that hides the rows, and there is a web page for it too, because someone who has already uninstalled the app still needs the door.

What Dana does not claim

Dana has no SOC 2 report, no ISO certification, no third-party penetration test and no bug-bounty programme. A small team saying otherwise would be the least trustworthy thing on this page. What it does have is a narrow attack surface, authorization enforced per row rather than per screen, rate limiting and a managed firewall in front of the API, and a security contact that a person reads.

Found something?

Tell us and we will answer. Machine-readable contact details are published at /.well-known/security.txt per RFC 9116. Please give us a reasonable window to fix an issue before publishing it.

support@danapetcare.com

The privacy policy carries the detail this page summarises, including how long each kind of data is kept and which providers process it. Deleting an account is documented at Delete your account.