Security
Security and trust
Per-utility isolation, your data stays yours, and a platform audited and red-teamed internally — the posture in plain language, without internals. Detail is given in the demo, by a person.
01
Built so one utility cannot see another’s data
Every utility’s data is kept in its own compartment, with its own keys, on every plan. That is not a setting somebody remembered to check; it is how the platform is built, and it is tested by deliberately trying to break it.
Utilities that want more separation than that can have it: an add-on gives a utility its own database. A cell of its own that no other utility shares is planned, and cannot be ordered yet. What the add-on buys is separation of noise and blast radius. It is never what stops one utility reading another’s data, because the plan every customer is on is already built to prevent it.
02
Your data stays yours
- Ownership
- The measurements, the records and the reports are the utility’s. IntelH2O operates the platform; it does not own, sell or pool what is in it.
- Sharing
- Nothing leaves your compartment except in the ways you set up: a share you create — with a regulator, a consultant, a partner — of only the measurements you name, for the period you set, revocable at any time; the alarm messages you choose to send; and, if you use the AI assistant, only the facts an answer needs, never used to train anything.
- Staff access
- IntelH2O staff cannot read a utility’s content in the ordinary course of business. Support access is opened for a stated reason and a limited time, and the utility sees it in its own activity log.
- Leaving
- When a utility leaves, it receives its data in full before anything is removed.
- Retention
- How long each kind of record is kept is visible to the utility’s administrator and can be shortened; the compliance record itself — the audit trail and filed reports — is kept for at least seven years, and longer where your regulator requires it.
03
Signing in, and who can do what
Your staff can sign in with your organization’s own identity; roles decide what each person may do and which sites they see, and a change takes effect at once. Every change and every request is logged, so an incident can be traced back to who did what.
04
Audited and red-teamed, in the open
IntelH2O does not hold a third-party security certification and does not claim one. What it holds to is a practice: a running copy of the platform goes through internal, AI-assisted security audits and red-team passes; findings are fixed and re-tested until nothing serious is open. The record of each round is kept.
The plain-language version above is deliberately all this page says. The mechanisms — how the compartments are built, how sign-in works, how the audits are run — are explained in the demonstration, by a person, and in the documentation a utility receives during its assessment. Your IT lead is welcome to bring questions.
See it on your own terms.
Ask the questions in person.
Request a demo: intelh2o.com/contact