Data handling

This page covers the traces your Agent sends and the content you enter in the dashboard. Mibo never calls your Agent.

Redaction at ingest

Mibo redacts every trace after it receives it and before it stores it. This applies to OTLP and Your API traces alike. Redaction covers span attributes, events, and status messages. In span names, Mibo redacts only token formats, URL credentials, and, when personal data redaction is on, personal data. Step names stay matchable by node_call assertions. Span IDs, trace IDs, and timestamps are not changed.

Redacted values are replaced before the trace is stored. Mibo cannot recover the original value later.

Secrets: always on

Mibo always redacts values under keys that contain one of these segments:

• password, passwords, passwd, passphrase
• secret, secrets, credential, credentials
• token, apikey / api_key, accesskey / access_key, private_key
• authorization, cookie

String and number values under these keys are redacted. Booleans are kept. Keys are split on separators and camelCase, and whole segments are compared. For example, access_token and x-api-key are redacted, while max_tokens and tokenizer are kept. Token counts such as gen_ai.usage.input_tokens are never redacted, so token_limit assertions keep working.

In free text, Mibo also redacts:

• Authorization, Cookie, and Set-Cookie header values
• key=value, key: value, and quoted pairs that use the secret keys above
• passwords in scheme://user:password@host URLs
• Bearer tokens, JWTs, and private key blocks
• AWS, GitHub, Slack, Stripe, and Google keys, sk- keys, and Mibo API keys

JSON inside a string, such as tool arguments or gen_ai.*.messages, is parsed, redacted, and re-serialized, so it stays valid JSON.

Redaction is pattern-based. It does not catch every secret. For example, a password written in prose without a separator, or a URL-encoded password%3D... pair, is not redacted. Keep secrets out of your traces where you can.

Personal data: opt-in per project

Personal data redaction is off by default. When it is on, Mibo also redacts:

• email addresses
• phone numbers
• card numbers that pass a Luhn check, including card numbers sent as JSON numbers
• IPv4 addresses

Only the project owner can change this setting:

1. In the sidebar, open Project details.
2. In the Privacy card, turn on Redact personal data.

The setting applies to traces Mibo receives after you change it. Traces already stored are not changed.

Placeholders

Redacted values become typed placeholders of the form [REDACTED:<type>], for example [REDACTED:secret], [REDACTED:email], [REDACTED:phone], [REDACTED:card], and [REDACTED:ip]. A Bearer token keeps its scheme: Bearer [REDACTED:secret]. Values are never truncated.

Assertions run against the redacted trace. If a check targets a value that Mibo redacts, write the expected value or regex against the placeholder. For example, use \[REDACTED:email\] instead of the original address.

Nesting limit

Mibo rejects a trace whose attributes nest more than 100 levels deep, counting JSON inside strings. The request returns 400 TRACE_TOO_DEEP and the trace is not stored.

Encryption at rest

Mibo encrypts trace content at rest. Evaluation results reference the trace instead of storing a copy of it. Result details are encrypted at rest too: reasons, expected and actual values, semantic reasoning, assertion configuration, and error text.

AI features

Semantic assertions, scenario routing, and Use real trace in the Test Architect send trace content to an external AI model provider. That content has already been redacted at ingest.

The AI chat used by the Test Architect removes secrets from your messages and the conversation history before it builds the prompt. It uses the same [REDACTED:secret] placeholders. The tests already in the editor are sent as they are. The chat filter covers secrets only. It does not remove personal data, so avoid pasting personal data into the chat.

Deletion

Deleting an Agent, a project, or your account hides it immediately. The deletion also covers its test cases, traces, evaluation results, and logs. Mibo permanently purges their content 7 days later. After the purge, Mibo keeps records without trace, test, or result content, such as IDs, timestamps, statuses, and scores. Project and Agent names and settings are kept.

What you delete	Where	What it includes
An Agent	The Delete agent button next to the Agent in the sidebar	The Agent, its test cases, its traces, and their evaluation results and logs
A project	Delete Project in the sidebar	The project, all its Agents, and everything they include
Your account	Delete my account on the Profile page	All your projects and everything they include. See Delete your account.

The sidebar shows Delete agent only when the project has more than one Agent. It shows Delete Project only when you have more than one project.

Other deletions:

• Clear Runs on a test removes its past results. In-progress runs are kept. Cleared results are purged after 7 days.
• Deleting a single test case removes it permanently right away. Its past results and logs are kept. To purge them too, use Clear Runs before you delete the test.

Deleted traces and runs still count toward your monthly plan usage, so deleting does not lower it. Deleting an Agent or a project frees its slot in your plan.

Traces you do not delete stay stored. Your plan’s history window limits what the dashboard shows, not what Mibo stores.