Source: https://docs.amadalis.ai/privacy/consent-and-visitor-data/

# Consent policy and visitor data

Checked against the product’s code on 7 November 2026.

Open **Privacy & Data** to review [consent](https://docs.amadalis.ai/reference/glossary/#consent), including when to ask permission before tracking people, and handle visitor records. Use an Admin account for personal visitor data. See [Privacy and consent](https://docs.amadalis.ai/trust/privacy-and-consent/) for the explanation of the consent model.

## Review the consent policy

Opt-in waits for acceptance of the relevant use of data. Opt-out starts with the allowed defaults until the visitor refuses. [Global Privacy Control](https://docs.amadalis.ai/reference/glossary/#global-privacy-control) is a browser signal asking the site to restrict data use.

1.  Open **Consent**.
2.  Read **Consent policy**. Check whether the policy follows visitor location or forces one setting everywhere, the country map, **Everywhere else** and the marketing default under opt-out.
3.  Read **What visitors experience** for the corresponding visitor choices.

**Accept all** grants what the banner names, and the banner names marketing only on a page that declares English and only on a site that shares. Global Privacy Control still refuses.

Under the platform default, unlisted or unknown locations use opt-in. A more specific regional rule takes precedence over its country rule. Global Privacy Control overrides both the defaults and a recorded acceptance.

The consent page is read-only. To change the policy:

1.  Open the copilot and describe the policy you want. For example, ask it to require opt-in everywhere if that is your chosen policy.
2.  Read **Change this site’s consent policy?** Check the locations, purposes and effect.
3.  Choose **Change the policy** to approve, or **Keep the current policy** to decline.
4.  Return to **Consent** and review the result. If the page could not refresh, use its refresh action before relying on the old display.

An approved policy changes the saved consent settings. An already open page or older stored copy can still show the earlier notice. Ask the copilot to undo the change to restore the earlier policy. Review the public site’s **Privacy choices** after changing the configuration.

[![Consent policy view with the automatic region mode, country map, marketing default and visitor-experience explanation.](https://docs.amadalis.ai/images/owners/menu-privacy-and-data.png)](https://docs.amadalis.ai/images/owners/menu-privacy-and-data.png)

The read-only consent policy view. Review its map and defaults before requesting a policy change. [Open full size](https://docs.amadalis.ai/images/owners/menu-privacy-and-data.png).

## Check recorded personalization reach by country

Use this to understand where personalization reached recorded visitors, rather than estimate everyone who visited.

1.  Ask the copilot: “How many visitors did personalization reach by country in the last 28 days?”
2.  Read the period and the newest counted record’s time.
3.  Compare each country’s count with its shown consent rule. The rules come from today’s policy.
4.  Read the grouped other countries as well as the named rows.

The question is read only and needs no approval. You can request 1 to 90 days; the default is 28. Countries with fewer than five reached visitors are grouped rather than named, with at most twenty countries named separately.

Visitors who refused, sent Global Privacy Control or had not answered where the site asks first are not recorded. The counts cannot show what share of all visitors personalization reached. See [Consent and reach requests](https://docs.amadalis.ai/reference/copilot/account-and-privacy/#consent-policy).

## Event retention

Visitor events are kept with no limit until you set a retention period. Once you set one, events older than it are deleted on the site’s regular scheduled run, but only after an [archive export](https://docs.amadalis.ai/reference/glossary/#archive-export) has covered them.

Open **Privacy & Data** > **Exports** > **Retention** to set or change how long each kind of event is kept. Review the approval before saving a period. Leaving a kind’s period empty keeps its events without a limit.

## Export site datasets

A site export is separate from one visitor’s export.

1.  Open **Privacy & Data**.
2.  Open **Exports**.
3.  Choose **Export a range**.
4.  Fill **From (inclusive)**.
5.  Fill **To (inclusive)**.
6.  Select the **[Datasets](https://docs.amadalis.ai/reference/glossary/#export)** you need.
7.  Continue to the approval step.
8.  Read **Export this site’s data for download?**, including the range and datasets.
9.  Choose **Approve & export** only when its scope is right.
10.  Read the result under **Run history**.
11.  Open **Downloads** for that run.
12.  Choose **Download everything (.zip)** to obtain its complete files.

The datasets cover events, decisions, goals, audience transitions, audiences, profiles, consent and daily rollups. Files are compressed NDJSON, a text format with one JSON record per line, plus a manifest listing the export’s files. Daily rollups are summaries grouped by day. A schedule requires the feature to be available for the account. Rerunning a range can replace its stored export files; read that consequence before approving. A file already downloaded cannot be recalled.

Exports and event retention are separate settings. See [Event retention](https://docs.amadalis.ai/privacy/consent-and-visitor-data/#event-retention) for when old captured events are deleted.

## Find the visitor record

1.  Open **Visitor Data**.
    
2.  Enter an email, user id, visitor id or person id.
    
3.  Choose **Search**.
    
4.  Open the matching browser record. One person can have more than one linked browser.
    
5.  Use **Journey**, **Identity**, **Interests and audiences** or **Decisions** to understand the record. **Data held** shows the stored data and consent choices.
    
    [![Visitor Data, Data held: no explicit consent records and arrival channel direct; name hidden.](https://docs.amadalis.ai/images/steps/S077-consent-visitor-record-data-held.png)](https://docs.amadalis.ai/images/steps/S077-consent-visitor-record-data-held.png "Open full-size image")
    
    What the site holds for one browser.
    

Check the browser identity before choosing an export or erasure. These operations have different reach.

## Export the record

1.  Open **Erase** on the browser record. The export controls are on this tab alongside the erasure controls.
2.  Choose **Export this visitor’s data**.
3.  Read the scope notice.
4.  Choose **Export this visitor’s data** again to draw the approval card.
5.  Read **Export this visitor’s data?** Check the time range, linked browsers and any data withheld for lack of consent.
6.  Choose **Approve & export**, or **Don’t export** to cancel.
7.  Read the receipt.
8.  Open **Privacy & Data**.
9.  Open **Exports**.
10.  Find the run under **Run history**.
11.  Open **Downloads**.
12.  Choose **Download everything (.zip)** for the complete run.

An export can reach beyond this browser to the linked browsers named in the card. A file already downloaded cannot be recalled.

## Erase one browser’s data

1.  Open **Erase**.
2.  Review the inventory of what will be removed.
3.  Choose **Erase this visitor permanently**.
4.  Read the scope and permanence notice.
5.  Choose the same control again to open the approval card.
6.  Read **Permanently erase this visitor’s data?** Check the exact browser record.
7.  Choose **Erase permanently** to proceed, or **Keep the data** to cancel.
8.  Read the receipt, including the result of resetting the visitor’s live state.

Erasure has no Undo. It removes the selected browser’s visitor data; it does not automatically erase the person’s other browsers. Search result checkboxes let you select several browser records for one approval card that names all of them.

Commerce orders remain, with their visitor link removed. This action does not delete the order’s customer details or the shopper’s account. Treat the export and erasure cards as statements of their exact scope.

## Your next step

Review [counting and identity](https://docs.amadalis.ai/privacy/counting-and-identity/) before interpreting a visitor’s records or combining them with another dataset.