---
title: "Data retention, raw IP storage and data locations"
description: "Set how long browser intelligence data is kept, decide whether full IP addresses are stored, and read where each kind of your data is stored."
canonical_url: "https://noxtica.com/docs/compliance/retention-and-locations/"
markdown_url: "https://noxtica.com/docs/compliance/retention-and-locations/index.md"
last_updated: 2026-10-27
published: 2026-10-27
section: "compliance"
section_title: "Compliance & Legal"
site: "Noxtica"
language: "en"
source: markdown
---

# Data retention, raw IP storage and data locations

An administrator uses three Backoffice pages to control and read how Noxtica stores data for the workspace: **Data Retention**, which includes the Raw IP storage opt-in, **Data Locations** and **RUM Data Lifecycle**. This page explains each control, what it changes and what to check afterwards.

The controls here apply to browser intelligence data and real-user monitoring data. Identity verification data follows a separate rule at the end of this page.

## What it is

Availability: depends on your plan, role and the modules enabled for your organisation.

### Data Retention

Open Backoffice → Privacy & Legal → Data Retention. The page has four parts.

| Part | What it does |
| --- | --- |
| Data policy | Two settings: **Data retention (days)**, "how long to keep browser intelligence data", and **Check interval (days)**, "minimum days between full re-collection per device". |
| Retention schedule | A read-only table of the effective window for each data category, with a Source badge. |
| Run retention now | An on-demand sweep that applies the saved window to your workspace. |
| Raw IP storage | An opt-in to store the full client IP address alongside the hashed one. |

The Backoffice accepts 1 to 365 days for **Data retention (days)** and 1 to 30 days for **Check interval (days)**. Every package starts at 7 days for **Data retention (days)**. The values in force and the plan defaults are shown in Backoffice and can change.

The retention schedule lists two categories:

| Category | Window comes from |
| --- | --- |
| Detection events | Your saved retention days ("Your override"), else the plan ("Plan default"), else "Default". |
| Audit log | The plan ("Plan default"). You cannot override it. |

The check interval controls how often a device is fully re-collected. It does not set how often data is removed. The purge job runs daily and you cannot configure it. Backoffice states that automated export before purge is not wired in this view. To archive data before it is removed, use the export tools. See [Audit log and data export](https://noxtica.com/docs/security/audit-log-and-exports/). Plan retention by data class is described on [Pricing](https://noxtica.com/pricing/).

For detection events, removal by retention is a soft delete. Records older than the window are hidden from views and exports. Permanent removal is a separate step that a Noxtica platform administrator performs. This page gives no timeline for it.

Some removal steps, such as audit-log removal and deletion of stored replay objects, can be paused platform-wide while Noxtica reviews its erasure safeguards. Backoffice does not show that state, and the schedule shows the window that applies, not whether a step is running now. If a window matters to your policy, ask your account team.

### Raw IP storage

By default Noxtica keeps a hashed IP and stores no raw IP. When you opt in, it also stores the raw client IP address so the operator console can search and correlate by exact IP during fraud investigations. The raw IP is purged on the same retention schedule as the rest of the submission data.

The raw IP is personal data. Backoffice warns you to enable it where your data processing agreement authorizes raw IP retention for fraud investigation and where your lawful basis and storage limitation are documented. Ask your counsel.

Turning the setting off permanently deletes every raw IP already stored for your workspace. The result message reports how many stored fingerprint records were cleared. This cannot be undone.

### Data Locations

Open Backoffice → Privacy & Legal → Data Locations. The table is read-only and shows five kinds of data. Each row has these columns.

| Column | What it shows |
| --- | --- |
| Service | Event data, Event payloads, Metrics, Warehouse analytics or KYC evidence. A "platform default" note means no location was chosen for your workspace. |
| Provider & region | The store and the location name, for example a Cloudflare or GCP store. |
| Jurisdiction | EU, US or TR jurisdiction, or "jurisdiction not assigned". |
| Retention | "retained N days" for the row. |
| Usage | A counted or estimated size with an "as of" time, "not applicable — this class has no usage meter", or a message that the figure cannot be read yet, with a reason. |

You cannot change a location from Backoffice. A Noxtica platform administrator sets placement. If you have a location requirement, ask your account team. The page shows what is configured. It is not a residency commitment, and your contract and the [DPA](https://noxtica.com/dpa/) are the source for commitments.

The Retention figure on the KYC evidence row is not a deletion date. Noxtica does not remove verification details or evidence by itself.

### RUM Data Lifecycle

Open Backoffice → Web Analytics & Privacy → RUM Data Lifecycle. It lists each real-user monitoring lane that can be purged on demand, what is stored and its current window. You can set the error-detail retention for a domain from 1 to 90 days and start a permanent purge of a lane. A purge needs a typed confirmation phrase and a fresh step-up check, and it cannot be undone. Replay retention is set per domain in Capture Policies, from 1 to 90 days.

The default window is 7 days on every package for error details, console logs, replay recordings and APM data. Error details, console log lines and APM data are held in the analytics warehouse, which removes them after 7 days: you can shorten their window but not extend it. Base RUM counters are platform-managed, kept for up to three months and not configurable.

### Identity verification data

Verification details and evidence are not part of these schedules. The Data Retention page covers browser intelligence data and never touches verification records. When the identity verification module is enabled, the page shows a note that these records are retained until a tenant administrator deletes them, with a link to KYC Erasure Requests. An administrator deletes verifications in KYC Verifications and works erasure requests in KYC Erasure. See [Requests and deletion](https://noxtica.com/docs/compliance/requests-and-deletion/).

## Prerequisites

- The administrator role. Saving retention needs the settings permission.
- A multi-factor method on your account. Saving retention, saving the raw IP setting, running retention now and purging RUM data ask for a fresh check.
- For raw IP storage, a documented decision from your privacy owner. The setting is off by default.
- For Data Locations, nothing beyond access to the page.

## Steps

### 1. Set the retention window

1. Open Backoffice → Privacy & Legal → Data Retention.
2. Enter **Data retention (days)** from 1 to 365 and **Check interval (days)** from 1 to 30.
3. Select **Save settings** and complete the step-up check.
4. If you shortened the window, confirm "Shorten data retention?". Data older than the new window becomes eligible for soft deletion at the next retention run.

### 2. Run retention now (optional)

1. Under **Run retention now**, select **Run retention now**.
2. Confirm. The run applies the saved window and cannot delete anything the schedule would keep.
3. Read the result. It lists soft-deleted fingerprints, events, visits, tracker batches and tracker metrics, and a section "What this run could NOT reach".

A workspace can start 4 runs in one hour. A run already in progress blocks a new one.

### 3. Decide raw IP storage

1. In the same page, find **Raw IP storage (opt-in)**.
2. Read the warning and the badge, which shows "Disabled" or "Enabled".
3. Move the toggle and select **Save**. Complete the step-up check.
4. When turning it off, read "Turning this off will permanently delete every raw IP already stored for this tenant." before you save.

### 4. Read your data locations

1. Open Backoffice → Privacy & Legal → Data Locations.
2. Read each row. Note any row marked "platform default".
3. Send questions about placement to your account team.

### 5. Set error-detail retention for a domain

1. Open Backoffice → Web Analytics & Privacy → RUM Data Lifecycle.
2. Select the domain.
3. Enter **Retention (days, 1–90)** and save.

## Verify it works

- The retention schedule shows your days for Detection events with the "Your override" badge.
- The audit log shows `settings_updated` with the new values.
- After a run, the history on Data Operations shows a "Retention run" with a status. See [Requests and deletion](https://noxtica.com/docs/compliance/requests-and-deletion/).
- Raw IP storage shows the new badge. The audit log shows `raw_ip_storage_enabled` or `raw_ip_storage_disabled`. When you turn it off, the audit entry records the number of scrubbed records and never the IP values.
- Data Locations lists five rows with a provider and region on each.

## Troubleshooting

| Symptom | Cause | Fix |
| --- | --- | --- |
| Save shows "Enter a value between 1 and 365." | The retention value is outside the accepted range. | Enter a whole number from 1 to 365. The check interval accepts 1 to 30. |
| Save asks you to verify again. | Saving retention needs a fresh multi-factor check. | Complete the prompt. |
| The retention schedule is missing. | The schedule is fail-soft. A failed read hides the panel without affecting the form. | Reload the page. |
| Run retention now answers "A retention run is already in progress for this workspace." | A run started in the last 30 minutes is still running. | Wait for it to finish. |
| Run retention now answers "Too many manual retention runs. Try again later." | The limit of 4 runs per hour was reached. | Try again after the hour passes. |
| The result says the run was a PARTIAL run or lists data it could not reach. | The run stopped early or could not reach some stores. | Treat the run as incomplete. Run it again later and read the unreachable list. |
| The audit log retention cannot be edited. | The audit log window comes from your plan. | Ask your account team. |
| A Data Locations row says its usage cannot be read yet. | The usage meter is not ready or the read failed. | Reload later. The location and jurisdiction columns still apply. |
| A raw IP opt-out reports zero cleared records. | No raw IP was stored for the workspace. | No action needed. |

## Related

- [Privacy and compliance controls in Backoffice](https://noxtica.com/docs/compliance/overview/): map of every privacy page.
- [Data subject scope, erasure requests and account deletion](https://noxtica.com/docs/compliance/requests-and-deletion/): delete end-user data on demand.
- [Session replay](https://noxtica.com/docs/observability/session-replay/): replay sampling, masking and retention.
- [Audit log and data export](https://noxtica.com/docs/security/audit-log-and-exports/): export data before it is removed.
- [Privacy Policy](https://noxtica.com/privacy/), [DPA](https://noxtica.com/dpa/) and [Subprocessors](https://noxtica.com/subprocessors/): the public legal documents.