Trust through clear choices, not big claims
A pet's record can include names, addresses, contacts and health information. We design PetNFO so that you can see who can reach it, why, and until when. This page separates what is designed from what is built, and lists what is still open.
What we are designing in
These are accepted design decisions for the first version. They become claims about the product only once they are built and checked.
You control sharing
Only people and practices you approve can see a pet's record. Each grant shows who, what and until when. Access that ends stops working, even in sessions that were already signed in.
Sources stay visible
Owner-reported and vet-authored records are always labelled. Corrections keep the original entry, plus who changed it, when and why.
Uploads are checked first
Files are scanned for malware and checked for safety before they can be viewed. A file that cannot be checked stays unavailable instead of being released anyway.
Changes are recorded
Access, record and administrator actions leave an attributable audit trail, without putting secrets or health notes in logs.
Staff work under tighter rules
Administrators, support and vets must use stronger sign-in, with a backup method. Ordinary support is not meant to browse clinical records, and any support session on your behalf is limited, time-boxed and audited.
Sign-in that suits you
Owners can use a passkey or an email and password, with optional extra protection. Sessions expire after inactivity, and sensitive actions ask you to confirm again.
What we do not claim
- We do not claim PetNFO is "100% secure" or that you can never lose a record.
- We do not claim ISO, SOC, Cyber Essentials Plus or any other certification. Aligning with a standard is not the same as being certified.
- We do not claim compliance with a privacy law until it has been reviewed and evidenced.
- Information a vet or family member has already received cannot be recalled after you end their access.
What has not been decided or done yet
- The legal entity responsible for privacy and access requests has not been established.
- Privacy notices, the access-request process and the hosting provider and region are not final.
- No independent security assessment has been carried out.
- No real pet or owner data is being handled. Everything shown is synthetic.
Specification first, tests first
PetNFO is built from written specifications, with tests written before the code. Every published change must pass the full automated test suites, including security regression tests, and keep 100% test coverage of the tested code.
Coverage is not proof of security, and we do not treat it as such. It is one of several checks, alongside dependency, secret and container scanning.
Your data and the future. Selling identifiable private records is not part of the plan. Any later use of information for research would need its own design, clear notice and a voluntary choice, and nothing like it is built or approved today.
Follow PetNFO as it takes shape
We are building in the open and describing only what exists. There is no sign-up form yet; read how to take part when we are ready for you.