Tez can see by default
- Node health: whether it is online and working, and its software state
- Nothing else, until you allow more
Trust and security
You decide when we can see your home.
Sentinel runs on your premises. By default Tez sees node health and nothing else. Video and recordings are yours.
How to read this page. Every control is labelled.
- Live todayWorking now
- Being rolled outIn progress
- Coming soonDesigned, not yet built
What Tez can and cannot see
The default is the narrowest view that still lets us look after your node.
Tez cannot see without your consent
- Live video and recordings
- The Guardian activity view
- Each of these needs your separate consent, every session. Coming soon
The controls that keep it that way
These are designed and being built. None of them is live yet, and we label each one so you can tell.
Coming soon
Support consent toggle
One switch that turns Tez support access on or off for your site. Off unless you turn it on.
Coming soon
Consent for each session
Video, recordings and the Guardian activity view need your separate yes every session. A yes for one session is not a yes for the next.
Coming soon
Time-boxed sessions with a reason
Every session has an end time and a written reason, shown to you before it starts.
Coming soon
Customer kill switch
End any session at once, and block further access until you allow it again.
Coming soon
Access log you can read
A page in your own app listing who accessed your node, when, why and whether they could view or act.
Coming soon
Monthly summary
A short monthly note of every support session on your site.
Coming soon
Emergency (break-glass) rule
If your node is down in a way that cannot wait and we cannot reach you, a named engineer may take emergency access to restore service. It is recorded in the access log, and we tell you afterwards.
Coming soon
Staff controls
Only named Tez support staff can start a session, each under their own login, and every action is tied to a person.
Support on demand
Tez does not hold standing access. Each session starts with you.
You ask
You report a problem or request a change.
You allow
You approve a time-boxed session and choose view-only or act. Coming soon
We fix
A Tez engineer works inside the limits you set.
Access closes
The session ends at the set time, or when you end it. Coming soon
What is live today
The foundations are in the product now, apart from one that is still rolling out.
- No standing open inbound ports. Remote access runs through an encrypted tunnel, so your router has nothing open to the internet. Live today
- Per-node credentials and key-only SSH on managed nodes, so one stolen password cannot open every site. Phase 1 is being rolled out. Being rolled out
- Local-first processing. Detection, recording and alerting run on the node at your premises. Live today
- Offline operation. The node keeps working when the internet is down. Live today
Local by default. Cloud is optional and extra.
Recordings, routines and network history stay on the node. Cloud access and cloud AI features are optional add-ons, charged separately and off until you ask.
If something goes wrong
If we find an incident that affects your node or your data, we tell you. How fast, and in what form, is part of the terms being finalised.
Legal terms are being finalised.
If you cancel
The system keeps running locally. Tez access to your site ends, and you lose updates, monitoring and support, not control of your home. Retention of records Tez holds is covered in the privacy notice.
Our roadmap
What we plan next on security
We hold no security certification today. These are plans, not claims.
- Independent security test of the platform and remote access path, with a summary of findings shared. Planned
- ISO 27001 is a goal for Tez Solutions. We have not started an audit and make no claim of compliance. Planned
Questions about security?
Ask us what a control does or where it stands. To report a security issue, write to [email protected].