Security
For a household’s most private details
Where the cars are kept. Who holds a key. How to get through the gate. Hartfield is designed on the assumption that none of it must ever reach the wrong person.
Protection by design
These describe how Hartfield is designed. We are in private preview; independent testing and published controls come before we open more widely.
Sealed per household
Each household’s records are isolated in the database itself, not just in the interface. One household’s data is never used to answer another’s question.
Secrets stay in your vault
Alarm codes, gate passwords and Wi-Fi keys are never stored or shown. Hartfield holds a link to your password manager and controls who gets it.
Access by person, home and area
A house manager can see the vehicles at one home and nothing at the others. A vendor’s access is designed to end when the job does.
Answers follow your permissions
Ask reads only what the person asking is allowed to see. It cannot be talked into revealing more.
Not used to train models
Your records are yours. We design every AI feature so that your household’s content is not used to train anyone’s model.
A record of who saw what
Hartfield is designed to log every view of a sensitive area and every change, in a record the owner can read.
What Hartfield will never do
Some of this is policy. Most of it is architecture: the system is built so that it can’t.
Access you can read at a glance
Choose a person and you see everything they can reach, in one place. Try it: pick someone and change what they can see.
The first row is different on purpose: codes are never held here. Turning it on gives that person the link to the item in your password manager — which still makes its own decision.
Questions we’re asked
We’d rather walk a security lead through the design than ask anyone to take it on trust.

