SAFR Scan Privacy Statement for On-Premises Deployments

Last modified on  October 14, 2025

Our Commitment to Your Privacy

At RealNetworks, we are committed to protecting privacy. The SAFR Scan access control device (“SAFR Scan”) is designed to give the local operator complete control over how data is collected, processed, and stored. This Privacy Statement explains how SAFR Scan handles information when it is deployed locally and describes the choices available to the local operator for managing that data.

  1. How SAFR Scan Works

In on premise deployments, SAFR Scan is deployed as a standalone device, where all processing takes place entirely within the SAFR Scan device. In this setup, the following types of data are collected and processed locally:

  • Default Data Collection: By default, SAFR Scan only captures and stores biometric signatures and facial images of individuals who are enrolled for access. Enrollment can be done using the web interface within SAFR Scan.
  • Temporary Data Processing: SAFR Scan briefly captures the facial image and generates a biometric signature of anyone attempting access. This information is used solely to verify whether the individual is enrolled for access and is automatically deleted immediately after the verification process is complete.
  • Live Event Logging: While the local operator is logged into the SAFR Scan web interface, the device will temporarily display events such as the face image and name of an access attempt to allow the administrator to confirm that the device is working properly. Once the operator logs out, these logs are automatically deleted.
  1. Optional SAFR Server and Desktop Integration

SAFR Scan can be connected to SAFR Server or SAFR Desktop application that can be installed on a local computer such as a laptop or a desktop machine to provide additional advanced features to the operator.  With SAFR Server or Desktop, local operator can choose to keep event data and application logs (the default retention is 30 days but can be adjusted to be deleted immediately).

  1. SAFR Server / Desktop Optional Configurations for Data Collection
Type of Information Examples Purpose Retention Limit (Default)
Biometric Data Encrypted facial-feature signature from a face image To recognize authorized individuals 30 days (adjustable)
Cropped Face Image Small image of the face captured during enrollment For visual confirmation on the device interface 30 days (adjustable)
Event Data Date, time, access granted/denied, device ID To log entry events and device activity 30 days (adjustable)
User-Provided Information Name, email, phone, access credential ID Only if the administrator enters it when adding a person NA

 

  1. Data Control and License Verification:

By default, all data collected through SAFR Scan remains entirely on the device or the computer where SAFR Server is installed and under the control of  local operator. RealNetworks does not receive or access any access control data, such as facial templates, images, or event logs. When SAFR Server or SAFR Desktop application is activated, it communicates with the SAFR Cloud Server hosted by RealNetworks only to verify that the software license is valid. No biometric, image, or event data is transmitted during this process.

  1. Security and Control

Local operator has full control over how long data is kept and who can access it. All data is encrypted, and can be deleted at any time.

  1. This document is provided to ensure transparency regarding data collection related to SAFR Scan and to enable the operator to provide required privacy disclosures to end users, employees and customers.
  1. Contact Us

For any questions about how SAFR Scan handles data, security privacy, please reach out to us at privacy@realnetworks.com.