Security & privacy
ForMotiv analyzes how people interact with a digital insurance experience: pauses, edits, pastes and navigation. It does not capture or store sensitive entered application field values such as names and addresses.
Zero PII CapturedEntered application field values such as names and addresses are not captured or stored.
| Field | Typespeed | Pauses | Times filled |
|---|---|---|---|
| First name | 0 | 0 | |
| Last name | 0 | 0 | |
| Address | 0 | 0 |
A small sample. Typing speed, pauses and times filled are three of the hundreds of behavioral features ForMotiv captures in every session. The rest aren’t shown here.
Nothing you type is stored or sent. These numbers are worked out in your browser and disappear when you leave.
The data boundary
“Zero PII Captured” rests on a specific distinction: ForMotiv records how a person interacts with an application, not the sensitive values they type into it.
How someone moves through the experience.
Typing behavior
Field interaction
Copy and paste events
Navigation patterns
Mouse and interaction behavior
Context that helps interpret behavior and connect it to your records.
Device and browser attributes
Network attributes
Session metadata
Boundary
What a person types into application fields stays out of ForMotiv.
Names entered in the application
Street addresses entered
Other sensitive values typed or pasted into application fields
Device and network information and identifiers are processed, and are not excluded.
Conceptual data flow
A high-level view of what moves from the application experience to ForMotiv, and what stays behind. It is conceptual: it does not describe hosting, regions or transport.
Behavioral, device and network intelligence is analyzed for the use cases you prioritized.
SIU, digital, distribution and underwriting teams see the context relevant to their work, and act on signals in selected sessions.
How signals are configuredYour security review
The data boundary answers what ForMotiv captures. Your security and procurement teams will have broader questions. Tell us what your review needs to cover and we’ll route it to the right people.
Hosting and data residencyWhere your deployment’s data is processed and stored.
EncryptionHow data is protected in transit and at rest.
Access controlsWho can see what, inside your organization and ours.
Retention and deletionHow long data is kept and how it is removed.
Testing and assuranceThe independent reviews your program requires.
DocumentationQuestionnaires and contractual terms your process needs.
Questions
The questions privacy teams and security reviewers ask most often.
ForMotiv does not capture or store sensitive entered application field values such as names and addresses. It records how people interact with the application, such as pauses, edits, pastes and navigation, rather than what they type.
Behavioral information, device and network information, and identifiers your organization provides, such as quote or policy numbers.
No. ForMotiv observes that a paste event occurred in the field. The pasted content, as an entered application field value, is not captured or stored.
No. It shows that a field was edited, how often and when. See the Forensics page.
ForMotiv serves clients internationally, including Europe, North America and Australia.
No. The typing demo at the top of the page works out speed, pauses and fills in your browser and keeps nothing. Nothing you type is stored or sent anywhere.
Next step
We’ll walk your reviewers through the data boundary, what is processed for your journeys, and the requirements your program needs addressed.
Your privacy, security and procurement checklist.
What is observed, processed and excluded for your journeys.
Route the rest of your review to the right people.
