What data does Tangiblee collect around users and what is done with it?
We take data privacy very seriously and take great care to ensure that your user’s information is safe. Tangiblee does not sell user data, nor collect data from individual users for use other than improving our product experience.
Please see the table below to see how Tangiblee's products handle user data.
For both Tangiblee Standard and Tangiblee Virtual Try-On (AR):
- Any anonymized data (user behavior within our solution) is aggregated and can be accessible via our Microsoft Power BI portal or Google Analytics.
- We can adhere to User Tracking Consent Settings
- We access and read the cookie settings established by the Privacy and Tracking Consent settings administered by the website.
- Based on this we adjust the performance and features of the Tangiblee software using the consent settings established at the user level.
- If you choose not to enable cookies, Tangiblee can turn off cookies as well.
Tangiblee uses two server options when it comes to Virtual Try-On (AR) photos storage. Depending on the retailer residency we can choose between the US server or the EU server. The photos are stored on the servers for two weeks. The pictures that come from Virtual Try-On experience (AR) are stored at the server RAM, while the pictures that were shared would be stored on the driver.
Tangiblee’s application is not dependent on the client’s cookies in any way and we run the application independently of them. Therefore, even if the user declines cookies, we will still run the application and the widget will be fully functional.
If the client’s cookies are configured so that if the user declines them, the whole activity shouldn’t be tracked, then this data won’t be pushed into the client's Google Analytics account. In that case, we won’t be able to extract this data from the client’s GA. What we suggest in that case, is the exact source from which to collect the cookie consent. We either can get it from the SDK triggering event tracking with our js script or the cookie source can be shared by the client, from which the preferences will be collected. For example, if the value is set at 0 we're not tracking events, if the value is set at 1 we do collect them.
