The window is not negotiable
A breach notification clock runs from discovery, and discovery is the part you can influence. Finding an exposure in week one is a managed disclosure with a plan attached. Finding it in month four is a regulatory conversation about why it took four months, held in public.
See the fragments as one exposure
Health data rarely appears whole. It surfaces in pieces, across sources that have nothing to do with each other, and the pieces only mean something assembled. KeyPriv resolves those pieces into a single identifiable exposure and tells you what it is made of.
Scattered mentions resolved into one identifiable exposure
Evidence retained for every finding, for disclosure and audit
Deployable on your own infrastructure where data cannot leave
A timestamped record of when an exposure was identified
Questions we get asked
- Can this run on our own infrastructure?
- Yes. On-premise is a supported deployment, and the collection side can be deployed separately from the platform it reports into — which is what makes a genuinely isolated deployment possible rather than merely permitted.
- Does KeyPriv store our patient data?
- Monitoring is driven by identifiers you register. The platform is looking for your data where it has been exposed; it is not a destination for your records. For deployments where nothing may leave your environment, the on-premise topology exists for exactly that reason.
- Is KeyPriv HIPAA certified?
- HIPAA has no certification — it has obligations, and any vendor claiming to be "HIPAA certified" is describing something that does not exist. What matters for your assessment is the deployment model, where data resides, and what is auditable. All three are worth going through in detail before you buy.
- How does this help the notification timeline?
- The clock runs from discovery. Shortening the interval between exposure and discovery is the only part of that timeline within your control, and it is the part this is built to compress.