Sanitize/Available now

Log Sanitizer for AI Sharing

Use this log sanitizer before you paste logs into AI, support tickets, GitHub issues, Slack, Jira, or email. It removes secrets, PII, and private infrastructure details while keeping the error message, stack trace, and other useful debugging context readable.

Remove PII from logs: Hide emails, phone numbers, IP addresses, customer IDs, and account details before sharing.
Redact secrets fast: Replace API keys, tokens, cookies, auth headers, URLs, hostnames, and local paths with clear labels.
Keep the useful part: Leave status codes, timestamps, stack traces, and error messages readable for troubleshooting.
Use it fully in-browser: Pasted text and uploaded files are cleaned in this browser instead of being sent away for processing.
Add custom fields to hide: Save private names, tenant IDs, workspace IDs, emails, and repeating patterns your team uses.
Reuse your setup later: This browser remembers your choices, and custom rules can be imported or exported when you switch devices.

More details appear below

Clean logs before sharing

Paste a log, choose what to hide, then copy a safer version for AI, support, tickets, or coworkers.

Try a sample log

Before: original log

After: cleaned copy

2026-05-01 10:42:18 ERROR Checkout request failed

Customer details
email: [EMAIL]
phone: [PHONE]
ip: [IP_ADDRESS]
card: [PAYMENT_CARD]

Request details
request_id: [ID]
url: [URL]
path: [LOCAL_PATH]

Secrets and infrastructure
Authorization: Bearer [JWT]
OPENAI_API_KEY: [OPENAI_KEY]
database: [DATABASE_URL]
kafka_broker: [BROKER]
Topic : [RESOURCE]
aws_role: [AWS_ARN]
Cookie: [COOKIES]

Safe debug context to keep
message: upstream timeout after 30000ms
status: 504
retry_after_ms: 30000

14 sensitive items detected

Review the removed item types below, then copy or download the cleaned version.

26 lines scannedInput 901 charsOutput 491 charsOutput 26 lines

Database URLs: 1 removedOpenAI keys: 1 removedJWTs: 1 removedCookie headers: 1 removedEmail addresses: 1 removedPhone numbers: 1 removedPayment card fields: 1 removedIPv4 addresses: 1 removedMessaging brokers: 1 removedMessaging resources: 1 removedAWS ARNs: 1 removedURLs: 1 removedUnix home paths: 1 removedTrace and log fields: 1 removed

Cleaning strength

Keeps logs easy to read while hiding common sensitive details.

Keeps

Debugging context

18 cleaning types activeThis count changes when you select or remove cleaning types below.

Choose what to hide

Turn off anything you want to keep visible in the cleaned copy.

Keys and tokensAPI keys, JWTs, auth headers, database links.Config valuesEnv variables, connection strings, DSNs, and app config.Email addressesCustomer and team email addresses.Phone numbersPhone numbers copied into logs or tickets.Identity numbersSSNs and strict-mode financial identity formats.Payment cardsCard fields and card-like numbers in strict mode.IP addressesNetwork addresses from logs and traces.Device addressesMAC addresses and device identifiers.Hosts and domainsServers, hostnames, referrers, and internal domains.Web linksPublic or private URLs.CookiesCookie and set-cookie headers.Computer pathsMac, Linux, and Windows user paths.IDs and tracesUser, customer, account, request, and trace IDs.Log and trace IDsLog IDs, event IDs, trace hashes, and object IDs.Infra detailsTenants, environments, clusters, namespaces, and services.Queues and topicsKafka brokers, topics, queues, streams, and consumer groups.Cloud resourcesAWS ARNs, buckets, storage links, and cloud resource IDs.Browser detailsUser-Agent and app client strings.

Custom things to hide

Bring custom rules from another browser or teammate. The file is read in this browser and your logs are not uploaded.Download only your custom rules, never the log text, so you can reuse your cleanup setup later.

Add private names, tenant IDs, workspace IDs, emails, or patterns once. This browser remembers them for next time; export the rules before clearing browser data or moving to another device.

Saved custom rules

LabelText to hideReplacementMatch type

Ignore case

Why sanitize logs before sharing

Raw logs often carry more than error details. They can include personal data, secrets, internal infrastructure names, and copied request context that should not be pasted into AI chats, tickets, or public issues.

AI prompts can keep too much context

Clean the log first so you are not pasting customer details, tokens, or private URLs into an external assistant.

Issue trackers spread fast

A log shared in GitHub, Slack, Jira, or support can be copied, forwarded, indexed, or retained longer than expected.

Secrets should be treated as exposed

If a real key, token, password, or cookie appears in a log, remove it from the shared copy and rotate it in the real system.

What this tool offers

A guided log cleanup workspace that helps you remove sensitive data without turning the output into unreadable noise. It is built for fast review before you paste a log into AI, support, or issue trackers.

Clean before you paste

Use the sanitizer before sharing logs with AI, support, GitHub, Slack, Jira, or coworkers.

Readable placeholders

See labels like [EMAIL], [JWT], or [LOCAL_PATH] so the cleaned copy still explains what changed.

Large-log friendly workflow

Paste text, upload .log, .txt, or .json files, review the result, and open fullscreen when the output is long.

Rules that match your environment

Add exact text or regex-based custom rules for private names, tenants, workspace IDs, and internal patterns.

Privacy and saved settings

The privacy model stays simple: the log text stays in this browser, your setup is remembered for convenience, and exported files contain rules only.

Your log text stays here

Paste text or load a file, clean it, copy it, and close the page. The cleaning happens in this browser.

Work faster next time

Cleaning strength, selected hide options, custom rules, and panel size are remembered on this browser for repeat use.

Know the catch

If browser data is cleared or you move to another device, saved preferences can disappear unless you export your custom rules first.

Example input and output

The output keeps the result useful while replacing risky details with clear labels.

Before

2026-05-01 ERROR checkout failed
Authorization: Bearer eyJhbGci...
OPENAI_API_KEY=sk-proj-example
email=jane.customer@example.com
url=https://api.internal/customers/92823
path=/Users/jane/projects/app/error.log
status=504
message=upstream timeout after 30000ms

After

2026-05-01 ERROR checkout failed
Authorization: Bearer [JWT]
OPENAI_API_KEY=[OPENAI_KEY]
email=[EMAIL]
url=[URL]
path=[LOCAL_PATH]
status=504
message=upstream timeout after 30000ms

Why placeholders help

Readable labels such as [EMAIL], [JWT], and [LOCAL_PATH] make the cleaned copy easier to understand without revealing the real value.

Descriptive guide

How to Remove Secrets From Logs Before SharingRead the checklist

What the sanitizer can hide

The built-in cleaner is designed for real logs, stack traces, copied request context, and support snippets that often include accidental share-risk details.

Secrets and credentials

API keys, JWTs, bearer tokens, cookies, auth headers, database URLs, and config-style secret values.

PII and customer data

Emails, phone numbers, payment card fields, identity-like values, customer IDs, request IDs, and trace IDs.

Internal infrastructure

Hostnames, private URLs, tenant names, brokers, topics, cloud resource names, and internal-only references.

Local environment clues

User paths, device details, browser strings, file locations, and copied machine-specific context.

Use cases

Before sharing with AI

Remove secrets, customer details, and internal service names before asking an AI assistant to help debug.

Before sending to support

Hide cookies, auth headers, account details, request IDs, and private URLs before opening a vendor ticket.

Before posting in GitHub issues

Strip tokens, local paths, hostnames, trace IDs, and internal infrastructure names from repro logs.

Before sharing with teammates

Keep the debugging context readable while cleaning private fields that should not travel across chats or docs.

How it works

The sanitizer scans the log in this browser, replaces risky values with readable placeholders, and shows a review summary before you copy, download, or share anything.

Paste or upload a log

Add logs, stack traces, copied console output, or .log, .txt, and .json files to the original log panel.

Choose what to hide

Use readable or strict cleaning, turn hide types on or off, and add custom rules when your environment uses private names or patterns.

Review the cleaned copy

Check the summary, inspect the placeholders, open fullscreen if needed, then copy or download the safer version.

FAQ

Does the log sanitizer upload my logs?

No. Your log text is handled in the browser. The tool does not upload pasted logs or uploaded log files.

What kinds of sensitive data can this log sanitizer remove?

It can hide API keys, JWTs, cookies, emails, phone numbers, IPs, URLs, paths, IDs, hostnames, and many other share-risk values commonly found in logs.

Why remove PII from logs before using AI or support tools?

Logs often contain personal details, customer information, and internal system data. Cleaning them first lowers privacy risk while still preserving enough context to debug.

What does the tool remember?

It remembers your cleaning strength, selected cleaning types, custom rules, and panel layout on this browser so you do not repeat setup.

What is import/export for?

It helps you move custom rules between browsers or share cleanup rules with a teammate. Export includes rules only, not log text.

Should I still review the output?

Yes. Review the cleaned copy before sharing, especially if the log contains unusual internal formats.

What should I do if a real secret is found?

Treat it as exposed. Rotate or revoke the secret before relying on deletion from chat, tickets, or issue trackers.

Can I upload log files?

Yes. You can upload .log, .txt, and .json files. The file is read in your browser and the same size limit is applied.