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

# Data and privacy

> What data Axosun sees: secrets are always cleared, users’ personal data is hidden by default.

> [!WARNING]
>
> Axosun is currently unavailable, and its return to service is not planned in the near future.

Axosun works with infrastructure data, but not with secrets and not with personal data “as is.” There are two levels of protection: secrets are cleared by **Always and unconditionally**, personal data of users is hidden by **by default** (configures).

> [!NOTE]
>
> Administrator/Security Administrator Required Rights: Change privacy settings via Axosun Policy (**Axosun** → **Policy** tab).

## What does the assistant see?

For each launch, a single context package is assembled: health summaries, node and Flow statuses, sample results, incidents, graphs and versions of Flow, operations/metrics/node services, log events, sanitized context of abuses.

## Secrets: Always cleaned out

Sanitation is applied to the **any** string sent to the model, regardless of the settings, both at the input and in the responses of the model (if the model collects the secret from the fragments, it will be cleared from the output).

* API keys (including LLM provider keys), bearer tokens, JWT
* Private key blocks and SSH keys;
* URL with login/password and tokens in query parameters;
* Subscription links, URIs `vless://` and `trojan://`;
* The values of the fields with names such as "password", "api key", "private key", "client secret", "webhook url", UUID VLESS, trojan passwords, keys and short ID Reality, private certificate keys.

Instead of a value, the model sees a marker of the form `[REDACTED:…]` – it can reason “there is a token here”, without knowing the value itself.

The administrator can expand the list: setting `redact_extra_terms` adds its own substrings (excluding the register), which will also be cleaned.

> [!NOTE]
>
> You can't turn off secret cleaning. It's not a setup, it's an unconditional property of the product. For more information on storing the secrets of the panel, [Secret Storage](https://docs.axottle.com/en/security/secrets.md).

## Personal Data of Users: Hidden by Default

When working with Remnawave users, the `redact_user_personal_data` switch works (**is on by default**). While it is on, the following are hidden: email, Telegram ID, username, description, device identifiers (HWID), short UUID. Hiding is applied at the tool edge - immediately before the transfer of model data, and not only "by writing in policy".

User Secrets – UUID VLESS, Trojan Passwords, Subscription Links – Are Cleared **always**regardless of the state of the switch.

## User samples are limited

The Assistant never receives full user lists:

* tools by users return counters plus a limited sample (by default up to 100 records, configured in the range of 1-1000);
* Estimate “how many users are affected” – only counters, without personal data;
* The tracing of the subscription projection is only the number of keys, never the URL.

## What's never passed on to a model

* API keys in an open form - only a link to the record in the secret repository is stored in the model profile;
* Subscription links;
* VLESS/trojan connection secrets;
* Reality's private keys;
* Full Xray JSON Remnawave configuration profiles in consolidated tools (summary only).

## What the Administrator controls

| Setting up | By default | Can I disable? |
| - | - | - |
| Clearing secrets | Includes | No - always works |
| Disclosure of Personal Data (`redact_user_personal_data`) | Includes | Yes (not recommended) |
| Additional terms for cleaning (`redact_extra_terms`) | empty | Configured |
| Access to Users (`users_access_enabled`) | OFF | Yes |
| Access to Subscriptions (`subscription_access_enabled`) | OFF | Yes |
| Maximum users in sample (`max_users_returned`) | 100 | Configured (1–1000) |
| Remnawave (`audit_enabled`) | Including | — |

## Verification

**1. Check the settings.**

Panel → **Axosun** → tab **Policy**: make sure that `redact_user_personal_data` is enabled.

**2. Test it in practice.**

If access to users is enabled, ask the assistant about the user: in the response, email, Telegram and device identifiers should be masked, and subscription links should be absent.

> [!TIP]
>
> In the answers of the assistant instead of secrets - markers `[REDACTED:…]`, personal data of users are disguised.

## Rollback

Return to default values: turn on `redact_user_personal_data`, turn off `users_access_enabled` and `subscription_access_enabled`, return `max_users_returned` to 100, clear `redact_extra_terms` (if added extra).

> [!WARNING]
>
> Disabling the concealment of personal data transfers email, Telegram and device IDs of your users to an external LLM provider, disable only knowingly and in accordance with your data protection obligations, while cleaning secrets still works.

## Related pages

* [Model of rights](https://docs.axottle.com/en/axosun/permissions.md)
* [Storage of Secrets](https://docs.axottle.com/en/security/secrets.md)
* [Journal of Operations and Audit](https://docs.axottle.com/en/panel/journal-and-audit.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.