Security & Privacy
How Property Tag is intended to protect property information, in plain English. Every item is marked with where it honestly stands today.
Coming soon. The Property Tag app hasn’t been built yet, and its security architecture is still to be completed. Nothing on this page describes a control that is already implemented, tested or certified. It sets out what we intend to build and what must be in place before launch.
How to read the status labels
- Planned
- We intend to build this, and the approach is broadly clear.
- Being designed
- We’re still working out how this should work.
- Required before launch
- We won’t open the app to the public without this in place and checked.
- To be decided
- A business or legal decision hasn’t been made yet.
The intended security model
Ten principles we intend the app to follow. None is claimed as built.
Role-based access
Owners, landlords, tenants, contractors and prospective buyers each see and do only what their role allows. The detailed rules are being finalised.
Account authentication
People who add or manage records sign in to an account. The sign-in method and recovery process have to be decided and tested before anyone is asked to add information.
Least access needed
Access is given for a purpose, such as one contractor for one job, and can be ended, instead of being open-ended by default.
Separation of public and private property information
What a tap shows to someone with no access is kept separate from the private record. Exactly what, if anything, appears publicly is still being decided.
Audit history
A record of who added or changed what, and when, so a property’s history can be trusted and questions can be answered.
Secure transmission and storage
Information is protected in transit and where it’s stored. The specific technical approach and the hosting provider haven’t been finalised, and we won’t describe them until they have been.
Backups and recovery
Records can be restored if something goes wrong. The approach has to be set up and tested before launch.
Monitoring
Watching for unusual activity and failures so problems are noticed early.
Incident response
A written plan for what happens if something goes wrong, including who decides, who is told and how.
Independent security review
An independent review of the finished app by a qualified person before it goes live. Not yet carried out, and none has been commissioned.
We aren’t claiming any certification, compliance status, uptime commitment or guarantee, and none has been obtained.
Intended privacy controls
What people could add, who could see it, and what happens to it over time. Where something isn’t decided, we say so.
What users may add
Records, invoices, photos, certificates and notes about a property. We’ll publish guidance on what not to upload, for example personal documents unrelated to the property.
Sharing choices
The owner or landlord decides who else gets access: a tenant, a contractor for a job, or a prospective buyer’s summary. The exact options are still being finalised.
Ownership and tenancy changes
The record is designed to stay with the property. Access for a leaving tenant ends, and the record passes to a new owner at sale. The detailed process is still being designed.
Data export
We intend owners to be able to take a copy of their record. Formats and process haven’t been decided.
Deletion
What can be deleted, by whom, and what must be kept (for example after a sale) hasn’t been decided.
Retention
How long information is kept, and what happens to records of properties no longer managed, hasn’t been decided.
Processor and service-provider transparency
A published list of the companies that handle information on our behalf, once they’re chosen. None has been selected yet.
Privacy notice and terms
A full privacy notice and terms will be published before the app launches. See below for how this website works today.
This website has no accounts and doesn’t currently collect personal information. Registration and contact forms are planned. Before they’re switched on, we’ll publish who is responsible for the information, where it’s stored, by which provider and for how long. We aren’t currently using cookies or analytics on this website.
What should never be in a public property view
Anyone can tap a tag at a property, including a visitor or a passer-by. So the starting position is that a tap with no access shows as little as possible. Our design principle is that these should never appear in a public view:
- Tenant names, contact details or tenancy information
- Documents, invoices or certificates
- Photos of the inside of the property
- Emergency or shut-off information that identifies the occupants
- Alarm, entry, lockbox or key-safe codes, or where keys are kept
- Owner or landlord personal details
- Maintenance history and open issues
Two things to keep in mind
Don’t store secrets in a record. Even with access controls, the safest place for an alarm code or a password is somewhere else. We’ll advise against putting them in a property record.
What a public tap shows is still being decided. It may be little more than a prompt to sign in or register. We’ll publish the final design before launch.
Public view contents
Decision outstanding.
Launch security checklist
What has to be true before the app is opened to real users. None of these is done yet.
- Final security architecture written down and reviewed
- Account sign-in and recovery built and tested
- Role and access rules implemented and tested, including for a tap with no access
- Audit history working
- Backups and restore tested
- Monitoring and an incident response plan in place
- Independent security review completed and findings addressed
- Hosting and service providers chosen and listed
- Privacy notice and terms written and published
- Retention, export and deletion rules decided
- A way to report a security concern (email address published above)
- The organisation responsible for personal information confirmed and named in the privacy notice
Privacy and terms
A full privacy notice and terms will be published before the app launches. For now, see how this website handles information.
Still have a question?
See the privacy, data and export FAQs.
Report a security concern
If you think you’ve found a security problem with this website, we want to hear about it. Please don’t access, change or share anyone else’s information.
This website has no accounts to log in to, and the Property Tag app hasn’t been built yet.
How to report something
Email [email protected] with what you found and where. Please don’t include anyone else’s personal information.
Follow Property Tag’s progress
The app isn’t built yet. We’ll publish more on security and privacy as it’s designed.