You should not have to choose between tracing your agent and keeping sensitive data out of a third party. PII redaction lets Latitude scan span content on ingest and replace matches with a labeled placeholder before anything is written to storage.

It is opt-in per project, from Settings → Privacy. Turn on the categories you want and Latitude redacts them going forward:

• Email addresses, phone numbers, credit card numbers, IBANs, and US Social Security numbers
• API keys and secrets, including provider key formats, private key blocks, and connection-string passwords
• IP addresses, off by default since a version string and a dotted quad look identical

For identifiers specific to your business, add custom rules so your own account numbers or internal IDs get the same treatment. Organization owners can set a policy across every project and lock it so individual projects cannot weaken it.

It is available over the API, the SDKs, and the CLI too, through settings.redaction, so you can enforce it as part of your setup rather than clicking through the dashboard.

A note on honesty: detection is pattern based, so it reliably catches structured identifiers but not names or free-form personal detail. Redaction applies to spans ingested after you enable it and cannot be undone, so turn it on early.