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

# Visitor records, identity and decisions

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

You need an [Admin](https://docs.amadalis.ai/reference/glossary/#admin) account to look visitors up, export a record or erase one.

1.  Open **Privacy & Data**.
2.  Open **Visitor Data**.
3.  Search with at least two characters of an email, user id or [visitor id](https://docs.amadalis.ai/reference/glossary/#visitor-id).
4.  Select the record you intend to inspect.

## Read the record’s tabs

| Tab | What to inspect |
| --- | --- |
| **Overview** | The selected record’s summary. |
| **Journey** | Recorded visits and actions in their order. |
| **Identity** | Browsers joined to the [person](https://docs.amadalis.ai/reference/glossary/#identity) and their links. |
| **Interests and audiences** | Available scores, memberships and reasons. |
| **Decisions** | Recorded selections and their available explanation. |
| **Data held** | The record types held about the visitor. |
| **Erase** | The visitor export action, and the scope and consequence of permanent erasure. |

Missing data is different from a zero score or no action. A page can be shown before its decision is recorded, so the **Decisions** tab can miss a recent page view. A decision rerun uses the saved facts about that visit with today’s settings. It may not reproduce the original decision exactly.

## Review identity links

Select the browser you intend to inspect. Removing it from a person changes the identity link; it is not erasure of its underlying records. A person can have other joined browsers with separate retained data.

## Export or erase

**To export:** open **Erase** and follow [Export the record](https://docs.amadalis.ai/privacy/consent-and-visitor-data/#export-the-record) for the two request clicks, approval and download steps. Use **Export this visitor’s data** and review its approval.

**To erase permanently:** open **Erase** and follow [Erase one browser’s data](https://docs.amadalis.ai/privacy/consent-and-visitor-data/#erase-one-browsers-data). The card names the one browser it erases. This cannot be undone. Choose **Erase this visitor permanently** only when that is the browser you intend to erase, then approve the card.

Batch selection also names visitor browser records; it does not automatically widen each selection to every browser joined to a person.

## Handle an erasure request across browsers

There is no single action in this screen that erases everything held about a person. An export can cover linked browsers; erasure covers the browser records named on its card.

1.  In **Identity**, review the person’s linked browsers.
2.  Open each browser record you need to erase.
3.  Follow [Erase one browser’s data](https://docs.amadalis.ai/privacy/consent-and-visitor-data/#erase-one-browsers-data), or select the relevant browser records for a batch erasure.
4.  Check that the approval card names the intended records before approving permanent erasure. There is no Undo.

An identity link does not find every browser a person has ever used. Unlinked browsers need finding separately.

Erasing a visitor alone leaves the shopper account in place. An Admin outside a support visit can erase that account separately. Open **Privacy & Data** > **Visitor Data** > **Erase shopper account**, enter the shopper’s email, choose **Review**, and read the permanent action before **Erase the account**. A live subscription must be cancelled first. Orders keep their full checkout details, including names, email, telephone, address, notes and arrival details, without the account link. Package purchases remain without that link; back in stock requests keep their email and Stripe keeps its own records. There is no Undo. Form submissions have their own erasure path: use **Delete submission** in [Forms and replies](https://docs.amadalis.ai/site/forms-and-replies/#read-replies). An export already downloaded cannot be recalled. Contact [Amadalis support](mailto:support@amadalis.ai) about retained order details or other records outside these erasure paths.

### What happens to archive copies after erasure

If your site keeps [archive exports](https://docs.amadalis.ai/reference/glossary/#archive-export), the visitor’s entries there are marked for removal and rewritten by the date shown on the receipt. If the receipt says marking failed, ask Amadalis support to complete the archive removal.

Erasing also clears the visitor’s live personalization. If that part fails, the receipt says so; the stored records are still erased.

For the shorter workflow, use [Consent and visitor data](https://docs.amadalis.ai/privacy/consent-and-visitor-data/). For the counting boundary, use [Counting and identity](https://docs.amadalis.ai/privacy/counting-and-identity/).