Eye tracking Data Transparency Policy

If Your Software stores or transfers Eye Tracking Data, then You must comply with this policy, and as such, Tobii requires the following to be implemented into Your Software:

Active User Acceptance: Your Software needs to use a consistent format to explicitly and clearly ask the user for their permission to store, or transfer, their Eye Tracking Data. This request for permission must happen before the user’s data is stored or transferred. It also needs to state the purpose of storing/transferring Eye Tracking Data and assurance that such data will not be used for any other purpose.
Visualization: Your Software must show the user when the storing or transferral of Eye Tracking Data occurs. You must provide a mechanism for visualization. This is required unless explicitly waived by Tobii.

Tobii recommends that the following is implemented into Your Software:

The What’s in it for me policy: inform users clearly about the value they will receive from Your Software. Clear guidance and knowledge of the benefits helps users to understand why they should provide with their Eye Tracking Data to You.

Please note that the implementation of this policy may vary for different product categories. For screen-based products, a window, such as the one below, is recommended for Active User Acceptance and the What’s in it for me policy.

Terminology

“Eye Tracking data” refers to these categories of data:

Biometric Eye Tracking Data: Data relating to the physical, physiological or behavioral characteristics of a person’s eyes or face;
Psychographic Eye Tracking Data: Any insights derived from biometric eye tracking data relating to a person’s physical, mental, and emotional state, or their interests

“Store or transfer” applies to any method of persistently saving eye tracking data beyond the length of the user session; or any method of sharing eye tracking data so that it can be observed by others in retrospect, or in real-time on a separate display or device.

Eye tracking Data Transparency Policy

Terminology

Our software development licensing model