This Privacy Policy explains how the current NarraSense Quest Player and NarraSense Server process limited technical and operational information for our location-based, shared-device installations.
NarraSense is designed primarily for location-based, shared-device environments such as museums, exhibitions, education, demonstrations, and other managed immersive installations.
The NarraSense Quest Player does not require the person wearing the headset to create an account or provide personal information. NarraSense does not currently collect Meta profile information, user account data, biometric data, eye-tracking data, hand-tracking data, precise GPS location, advertising identifiers, or information intended to identify the individual person using a headset.
The system does process limited technical and operational information needed to connect Quest headsets to a local NarraSense Server, synchronize playback, diagnose faults, and support operation of the installation.
The Quest Player may process and record the following technical and operational information locally on the headset:
The Player does not log Wi-Fi passwords.
To support automatic network reconnection, the NarraSense Player may store the local Wi-Fi network name and password in local application storage on the headset. The NarraSense Server stores the venue Wi-Fi network name and credentials locally on the server machine so that headsets can be configured and reconnected to the installation network.
These credentials are used only for operation of the local NarraSense installation. The current release does not send these credentials to NarraSense cloud services or to any external internet service.
The Quest Player and NarraSense Server communicate over the local venue network.
The Server may receive and process:
The Server sends operational commands and configuration information to Quest Players over the same local network, including playback commands, clip information, projection settings, timing information, volume settings, and local network configuration needed for reconnection.
The Quest Player creates diagnostic log files on the headset. These logs may contain the technical and operational information described above.
Player logs may be uploaded to the local NarraSense Server either automatically when recovering a previously unsent log after reconnection, or when requested by an operator through the Server. These uploads occur over the local network only.
The NarraSense Server stores uploaded headset logs as local files on the server machine.
The Server also maintains its own operational logs and structured event logs. These may include headset connection and disconnection events, device identifiers, operator-assigned headset names, clip playback events, connected-device counts, commands, and errors.
Quest Player log files are retained on the headset for up to 7 days after a successful upload, subject to the configured retention setting, and are then deleted automatically.
NarraSense Server logs, structured event logs, and uploaded headset logs are stored in dated log folders and are automatically deleted after 30 days under the current server implementation.
Configuration data such as headset names, language/group assignments, clip metadata, network configuration, media metadata, and local network credentials may remain on the relevant device or server until they are changed, manually cleared, or the application/configuration is removed.
In the current release, the NarraSense Quest Player does not contain a NarraSense cloud telemetry endpoint and does not automatically transmit Player logs, operational statistics, or device information to NarraSense over the public internet.
Based on the current reviewed NarraSense Server application code, the Server also does not transmit operational data to external analytics, telemetry, crash-reporting, advertising, or NarraSense cloud services.
The current system is designed to operate locally between the NarraSense Server and Quest Players on the same local network.
The current NarraSense Player does not use Unity Analytics, Firebase Analytics, advertising SDKs, third-party behavioral analytics, or third-party crash-reporting services identified in the reviewed application code.
NarraSense does not currently use Meta account/profile information to identify headset users and does not use the Player to collect information about the identity of the person wearing a headset.
AVPro Video is used for media playback. It is not used by NarraSense as an analytics or user-tracking service.
The Quest Player requests permissions required for local-network operation, media playback, and headset lifecycle management.
Android may classify some of these permissions broadly. In particular, location-related permission is required by Android for Wi-Fi connection functionality used by the Player. NarraSense does not use this permission to obtain, store, or transmit GPS coordinates or physical-location information about headset users.
Storage/media permissions are used to access media and application files required for NarraSense playback and diagnostics.
NarraSense is designed for managed installations in which different people may use the same headset over time. The current release does not create user profiles, audience accounts, attendee histories, or persistent records of who watched a particular experience.
Operational records relate to devices, media playback, system status, and installation activity rather than to the identity of individual headset users.
Future NarraSense versions may introduce features such as licensing management, customer CRM integration, fleet statistics, cloud telemetry, operational analytics, or optional user-provided information.
These features are not active in the current release. If NarraSense introduces new data collection or external transmission, this Privacy Policy will be updated before or when those features are deployed, as appropriate.
NarraSense is designed to operate on a managed local installation network. Technical configuration and diagnostic information is kept on the Quest devices and NarraSense Server used by the installation, except where a future version explicitly introduces an external NarraSense service and updates this policy accordingly.
Customers operating NarraSense are responsible for maintaining appropriate physical and network access controls for their local server, router, and headset environment.
Where NarraSense itself processes personal data described in this policy, the main legal basis is legitimate interests under Article 6(1)(f) of the GDPR. Those interests are operating, securing, maintaining, diagnosing and supporting the NarraSense system, preventing misuse, and maintaining reliable service. We limit this processing to technical and operational information reasonably necessary for those purposes and do not use it for advertising or audience profiling.
If you contact NarraSense directly for support, privacy requests, or other enquiries, we process the contact details and information you provide so that we can respond and manage the request. Depending on the context, this is based on our legitimate interests, performance of a contract or steps requested before entering into a contract, or compliance with a legal obligation.
Most operational information in the current release remains on customer- or venue-controlled Quest devices and the local NarraSense Server and is not automatically received by NarraSense. A customer or venue operator may therefore be the controller for personal data processed within its own installation. Where NarraSense receives or accesses installation data solely to provide support on a customer's instructions, the applicable controller/processor roles depend on the relevant arrangement and applicable law.
Headset users are not required to provide their name, Meta account information, contact details, or other identity information in order to use the current NarraSense Player.
Technical and operational information described in this policy comes from the Quest device and NarraSense software during normal operation, from configuration entered by an authorized venue/operator, and from diagnostic logs generated by the Player or Server. If you contact NarraSense directly, information also comes from what you choose to provide in that communication.
Within a local installation, technical and operational information may be accessible to authorized staff of the customer or venue operating the NarraSense system. NarraSense personnel may receive or access information when it is provided for support, troubleshooting, maintenance, or a privacy request. NarraSense does not sell personal data and does not share the current Player/Server operational data for advertising or behavioral profiling.
The current Player and Server do not automatically send the operational information described in this policy to external analytics, advertising, crash-reporting, or NarraSense cloud services. Meta may separately process platform or device information under its own terms and privacy policies; the current NarraSense Player does not use Meta account or profile information to identify headset users.
Where the GDPR applies and NarraSense is the controller of personal data about you, you may have the right to request:
To exercise these rights, email info@narrasense.nl and describe your request. We may ask for limited additional information where necessary to identify the relevant records and verify the request. Because the current NarraSense Player does not create user accounts or identify the person wearing a headset, in some cases it may not be reasonably possible to link a local technical record to a particular individual. If so, we will explain that limitation.
We will respond within the time limits required by applicable law. GDPR requests are generally handled without charge, subject to the exceptions allowed by law.
You also have the right to lodge a complaint with a data protection supervisory authority. In the Netherlands, the supervisory authority is the Autoriteit Persoonsgegevens (AP), available at autoriteitpersoonsgegevens.nl.
The current NarraSense Player and Server do not use personal data for automated decision-making that produces legal or similarly significant effects, and do not create behavioral or advertising profiles of headset users.
All users may request deletion of data that NarraSense has collected or stored about them at any time, regardless of where they live, and without charge. To make a deletion request, email info@narrasense.nl with the subject "Data deletion request" and provide enough information for us to identify the relevant NarraSense installation or device records.
The current NarraSense release does not automatically transmit local Quest Player logs or NarraSense Server operational data to NarraSense cloud services. As a result, NarraSense may not possess the local operational data associated with a particular installation. Where requested data is held only on a customer- or venue-controlled NarraSense Server or headset, we will explain this and, where appropriate, assist with or direct the request to the operator of that installation.
Where NarraSense does hold data that falls within the request, we will delete it unless retention is required by applicable law. If a legal obligation prevents deletion of specific information, we will explain that limitation.
For privacy questions or requests relating to NarraSense, contact:
NarraSense
Email: info@narrasense.nl
Website: https://narrasense.nl/
Business address: Jan Pietersz. Coenstraat 7, 2595 WP Den Haag, Netherlands