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

# Elevated privacy

<Note>
  CLI man page: `safesquid-elevated(5)`
</Note>

<Frame caption="Privacy level selection">
  <img src="https://mintcdn.com/safe-squid-labs-12a0916f/VRx-_vpMam8ezhZz/images/admin_guide/elevated_privacy_flowchart.svg?fit=max&auto=format&n=VRx-_vpMam8ezhZz&q=85&s=3ff720f8ecac344703f1552461166bed" alt="Privacy level selection" width="480" height="160" data-path="images/admin_guide/elevated_privacy_flowchart.svg" />
</Frame>

## Overview

The `Elevated` section (`safesquid-elevated(5)`) reduces cross-site tracking by stripping third-party cookies and selected tracking headers. Without it, third-party cookies and related trackers can follow users from site to site.

## Core Mechanics (C++ Source Validation)

### First match wins

On each request and response header pass, enabled Elevated policy rows are walked top to bottom. The **first** matching row sets the privacy level for that connection; later rows are skipped.

### Privacy levels (action field)

* **NOT-REQUIRED** — No stripping; bypass elevated privacy.
* **LOW** — Drop third-party Cookie and Set-Cookie when cookie flag set.
* **STANDARD** — LOW plus remove Referer and Origin on outgoing requests.
* **PARANOID** — STANDARD plus remove User-Agent (may break browser-variant sites).

### Logging

Changes logged to privacy log and Detailed logs with filter name Elevated-Privacy. Debug header `X-Elevated-Privacy` reports level when Send Debugging Headers includes client.

## Processing flow

```mermaid theme={null}
flowchart TD
hdr[Request or response headers] --> walk[Walk Elevated rows top-down]
walk --> match{First enabled profile match?}
match -->|No| none[No elevated changes]
match -->|Yes| level{Privacy level}
level -->|NOT-REQUIRED| none
level -->|LOW| cookies[Strip third-party cookies]
level -->|STANDARD| cookies --> stripRO[Remove Referer Origin]
level -->|PARANOID| stripRO --> stripUA[Remove User-Agent]
```

## Schema Fields

### Global fields

* **Enabled (enabled)** — Master switch. When off, processors exit without header changes.

### Policy rows

* **Profiles (profiles)** — Limit privacy level to tagged connections. Blank matches all.
* **Privacy Levels (action)** — NOT-REQUIRED, LOW, STANDARD, or PARANOID.
* **Comment (comment)** — Operator note only.

## Examples

### Standard privacy for all

* **Configuration:** One row Profiles blank, Privacy Levels STANDARD.
* **Result:** third-party cookies dropped; Referer and Origin removed on requests for all matching connections.

### Paranoid for guests, bypass for staff

* **Configuration:** Row A Profiles STAFF NOT-REQUIRED; Row B blank PARANOID.
* **Result:** staff keep full headers; others get paranoid stripping.

### Cookie-only for marketing

* **Configuration:** Profiles MARKETING USERS, Privacy Levels LOW.
* **Result:** only third-party cookies stripped; Referer and User-Agent remain.

## Recommended practice

* Start with LOW or STANDARD before PARANOID — removing User-Agent breaks some applications.
* Place NOT-REQUIRED bypass rows above broad PARANOID rows.

## How to verify

1. Browse multi-site flow; inspect request headers upstream of proxy.
2. Check `privacy.log` under Reports.
3. Enable elevated log level for native privacy lines.
4. Debug header `X-Elevated-Privacy` on client when configured.


## Related topics

- [Elevated Privacy](/use_cases/data_leakage_prevention/elevated_privacy.md)
- [Login Issues on Specific Websites](/troubleshooting/unable_to_login_specific_website.md)
- [Application Binaries and Modules](/safesquid_swg/files_and_folders/application_binaries_and_modules.md)
- [Security Logs](/use_cases/audit_and_forensics/security_logs.md)
- [Debug response headers](/admin_guide/start_here/debug_response_headers.md)