Legacy Trigger Code (<18x) - Replay Privacy Options

ForeSee Replay was designed to give the client control over blocking any sensitive data, including but not limited to Personally Identifiable Information (PII). Because ForeSee is not in the business of collecting and managing PII, ForeSee prefers that this information be blocked from capture on ForeSee’s servers. ForeSee assumes clients agree that PII should be kept apart from customer satisfaction analytics. However, on a case-by-case basis at the direction of a client, ForeSee can accommodate requests for alternative management of PII data.

The following are various approaches that ForeSee provides clients to control the way personal information is handled by Replay – including the preferred option of not capturing the personal information at all. In all cases, the client is responsible for rigorously identifying any sensitive information that maybe present on their web site to assure that it’s handled properly in accordance with the client’s processes and procedures. ForeSee requires all clients to declare which of the following options will be implemented with their SessionReplay code package via ForeSee’s Secure Information Form (SIF). Clients must sign and date the SIF prior to code development.

Data Field Entry

As a default, Replay does not capture any data field entry. These fields appear as blocked with the following symbol: “*”. The actual characters typed in the data field do not appear inReplay.

If “Joe” is typed into the “First Name” field, it appears inReplay as “***”.

ForeSee has the ability to change this default and allow certain fields deemed NOT Personally Identifiable Information (PII) to be processed. For example, some clients choose to enable the capture of input into the following data fields:

  • Search Box
  • City and Zip Code (but still blocking First Name, Last Name, Address, and Phone)

In-line Personalization

In-line personalization is data of a personal nature that is displayed on a webpage as static text or within a drop down.

Example 1
After a user logs into a site, they may receive the following message: “Hello Joe, your balance is $123.45.”

Example 2
In the process of placing a purchase order (order confirmation page): “Shipping Address: Joe Smith, 123 Main Street, Ann Arbor, MI 48103”.

Example 3
User’s previous credit card information selectable from a drop down. User may have the following in the drop down:

“Amex, ….1234, exp 10/2011”
“Mastercard, …9876, exp 11/2012”

Data Blocking

Replay has the ability to mask information PRIOR to it being sent to ForeSee by inserting comment tags that encompass the PII fields. These tags are created and inserted by the SessionReplay product and require no alterations to the page HTML.

<!--fsrHiddenBlockStart--> Name:<fname>, Zip Code:<zip code><!-- fsrHiddenBlockEnd --> 

ForeSee’s Implementation Team will review the SIF with the subscriber prior to making any changes in the default setting, which blocks the recording of all data collection fields, and approving code to block all in-line personalization.

Other articles in this section:

  1. Implementing ForeSee for Web
  2. Implementation Steps
  3. Testing & Troubleshooting
  4. Survey Options
  5. Code File Library
  6. Performance Optimization
  7. Trigger Specifications
  8. ForeSee Replay Specifications
  9. Replay Privacy Options (current article)
  10. 508 & WCAG Compliancy