Public pages only
We see the page the same way a signed-out visitor would.
Security & data handling
We protect the page. We keep the footprint small.
KeyPages checks public, signed-out pages in a real browser and keeps only the evidence needed to explain what happened.
What does KeyPages access?
KeyPages checks public, signed-out pages only. We do not use application admin credentials, and we do not access logged-in areas or private-page flows.
No access to private areas
No admin account, private session, or stored application credentials.
What does KeyPages do on the page?
KeyPages renders the page in a real browser, checks visible content and page behavior, and records what it sees.
It does not submit forms, create accounts, place orders, or submit payments.
What evidence is kept?
We keep the minimum evidence needed to explain what happened. Raw HTML is removed after 48 hours.
Results and timing
Check outcomes, timing, and the signals needed to understand what happened.
Rendered content
The readable content and page behavior observed in the browser.
Screenshots when available
A visual record of the rendered page when screenshot evidence is captured.
Screenshot evidence is stored privately and accessed through revocable, read-only links.
What happens when I delete a protected page?
Page-owned scan history is removed and unreferenced screenshots are scheduled for cleanup. Other derived evidence and history follow your account retention policy.
Built for public pages today
Automatic discovery may inspect a starting site to suggest pages. Ongoing protection stays scoped to the pages you choose.
Not for logged-in flows yet
KeyPages does not currently test authenticated or private customer journeys.