> ## Documentation Index
> Fetch the complete documentation index at: https://www.algolia.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Radar data and privacy

> Learn what data Radar collects, how Algolia handles it, and how long Algolia stores it.

Radar collects pseudonymized behavioral event data from your ecommerce site for the [Value Engineering](/doc/value-engineering) service.

## Cost and terms

Value Engineering and the Radar data connector are free for qualifying customers.

Value Engineering is subject to Algolia's [Free Services](https://www.algolia.com/policies/terms#:~:text=services%20\\\(the%20%E2%80%9CServices%E2%80%9D\\\).-,2.%20Free%20Services.%C2%A0,-2.1%C2%A0Algolia%20may) and the [product specific](https://www.algolia.com/policies/product-specific-terms#:~:text=Agent%20Studio-,NeuralSearch,-Algolia%E2%80%99s%20NeuralSearch%20language) terms applicable to NeuralSearch.

## Performance and reliability

Radar run in your site's background without changing your website content or HTML elements.
The script loads asynchronously from a content delivery network (CDN) and is about 10 kB.

Radar collects selected pseudonymized user events and sends a small amount of data to Algolia.
The browser sends events in the background.
It might drop some events if the page closes, the network fails, or the browser blocks the request.

## Event data

Radar collects these events:

* `search`
* `view_item_list`for product listing pages
* `view_item` for product detail pages
* `add_to_cart`
* `purchase`

Radar can collect these events from two sources. During the initial analysis, Algolia checks that the required data is available from at least one source:

* **Data layer.** A structured data object on your site that contains event and page information.
* **HTML elements and URLs.** Radar can use page structure and URLs to identify search queries, search results, product views, cart events, and purchases.

## Personal information

Radar may receive personal information, such as IP addresses or information included in events.
Radar doesn't store this personal information.

Radar may use an Algolia first-party cookie for pseudonymized user identification.
This depends on which Algolia features appear in the demo.

## Data access

Only a limited group of Algolia engineers who operate Radar have access to your raw data.
Your Algolia account team only has access to aggregated data for ranking and relevance analysis.

## Security measures

Algolia provides the Value Engineering service under its [Security Measures](https://www.algolia.com/distributed-secure/security-compliance/measures).

Radar reads events from your website's data layer or HTML elements.
It filters the data to reduce what it sends to Algolia, then sends the remaining data to Algolia servers.

Algolia considered these safeguards during script and server development:

* Data minimization.
* Failure isolation to reduce impact on the user experience.
* No read endpoints for backend systems.
* OWASP Top 10.
* Snyk Code SAST scanner.
* Snyk Open Source, Snyk Container, and GitHub Dependabot dependency monitoring.

Algolia minifies and obfuscates the Radar script to reduce its size and limit browser-based tampering.
Algolia can provide the full version for code review.

## Data retention

Algolia stores Radar data for the length of the Value Engineering service.
Afterward, it deletes the data according to Algolia's standard retention policies.

If you choose to keep the Algolia application after the service ends, Algolia retains the data in that application.

Radar uses `sessionStorage` to store event data temporarily in the browser.
The browser clears this data when users close the tab or window.