Privacy Platform › Exposure Library › Session & Input Monitoring
Exposure family

Session & Input Monitoring

Tools that capture what a visitor types, clicks and does on screen: session replay, keystroke capture, form-field interception and clipboard access.

Why it matters to an underwriter

The engine of the current wiretap wave.

Session replay reconstructs what a visitor does as it happens, and courts have treated that as contemporaneous interception. Keystroke capture is the most direct form of input interception and the clearest wiretap fact pattern.

Chat widgets count too. Many record the full conversation, including text typed before a visitor hits send, and route it through a third party. Unmasked fields can expose sensitive data.

Default severity:CriticalHigh
CYRISK FINDING · SESSION & INPUT MONITORINGCritical to Bind

Third-party transmission of input data

PHASEBefore consent
TECHNOLOGYInput-capture tool (vendor withheld)
LEGAL THEORYCIPA · ECPA · Stored Communications Act · aiding and abetting
DAMAGES MODELOften modeled as $5,000 per violation under key provisions, plus injunctive relief
RESOLVED BYRemove the tool, or encrypt, restrict by contract and disclose

Example finding. Vendor names are withheld.

Risks in this family

What CyRisk tracks.

Severity and placement are CyRisk defaults. Your team can elevate, downgrade or drop any risk to context-only, per account.

RISKDEFAULT SEVERITYDEFAULT PLACEMENT
Third-party transmission of input dataCriticalCritical to Bind
User input monitoring and session analyticsHighMay Affect Coverage
Real-time keystroke captureHighMay Affect Coverage
Form field capture prior to submissionHighMay Affect Coverage
Clipboard monitoringHighMay Affect Coverage
Input monitoring prior to consentHighMay Affect Coverage
What triggers it

A session-replay, keystroke-capture or chat tool is observed recording or transmitting visitor input to a third-party server.

What resolves it

Remove third-party keystroke capture, mask every form field, and gate session replay behind consent. If a tool is retained for a documented purpose, encrypt what it sends, restrict the vendor by contract and disclose it.

Verified by rescan. The fix shows on the next scan.

How underwriters respond

Ready-to-use language.

Ask the broker

“Which session-replay or chat vendor is used, are form fields masked, and under what agreement?”

Subjectivity

“Mask all form fields and gate session replay behind consent, or remove keystroke capture, verified by CyRisk rescan.”

Terms

Sublimit or higher retention. Weigh most heavily on login, health and financial pages.

More on how underwriters use CyRisk →

Questions underwriters ask
Is all session replay a problem?

Not equally. Exposure depends on whether fields are masked, whether it runs before consent and which pages it covers.

Do chat widgets count?

Yes. Many record the full conversation, including what a visitor types before sending, and pass it through a third party.

Why is keystroke capture so serious?

It’s the most direct form of input interception, which makes it the clearest wiretap fact pattern.

Find the session tools in your pipeline.

Send five past submissions you’ve already bound, conditioned or declined. We score them blind, then put our disposition next to the call you made.

Severity and placement shown are CyRisk defaults and can be tuned per account. A detected exposure indicates a fact pattern common to privacy litigation, not a confirmed violation. Litigation theories explain why a finding is tracked; they are not legal advice.