# Privacy & Security

Occuspace was architected with privacy in mind and we are committed to protecting individual identities. The design of Occuspace makes it impossible to track any individual and no Personally Identifiable Information is ever collected and stored in our platform.&#x20;

### Privacy & Security Safeguards

* Occuspace collects zero personally identifiable information (PII) and is fully GDPR and CCPA compliant
* Occuspace sensors have passed security review and penetration tests by a certified, independent third-party security auditing firm (report available upon request)
* Occuspace sensors never connect to any devices, and can only passively observe the BLE and WiFi activity in a space being measured
* Occuspace does use a unique identifier for each BLE and WiFi signal being measured.  This unique identifier is based on the broadcasted MAC address of each radio
* Modern smartphones, laptops, and other consumer devices randomly rotate the MAC address of the BLE and WiFi radios for consumer protection
* Occuspace further enhances privacy by irreversibly hashing the broadcast MAC addresses into the unique identifiers used in data analysis
* MAC addresses are irreversibly hashed immediately on the sensor itself with the original MAC address value never stored locally or in the cloud
* Hashing is performed with SHA256 and reduced (truncated) in size to make it impossible to reverse
* A daily rotating salt is applied to the hashing process to further obfuscate the unique identifiers
* The sensors only transmit hashed data to the Occuspace cloud
* After hashed data is successfully sent to Occuspace it is permanently deleted from the sensors&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.occuspace.io/technology/privacy-and-security.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
