PII redaction
Execution evidence, asset content, logs, and diagnostic bundles should be checked for secrets and personal data before persistence or sharing. The redaction flow recognizes common high-risk material including Bearer credentials, API keys, tokens, and private keys.
Limits of automatic handling
Evolver’s execution-evidence outlet sanitizes credentials, sensitive assignments, and arguments. It reports whether content changed, whether it was blocked, the policy version, and reasons. Detection covers defined patterns; it is not a detector for every kind of personal information.
Review screenshots, office files, customer source material, file names, and project content before sharing. If experimental task handoff is enabled, review exported task packages separately: they are unencrypted, cannot be recalled once shared, and do not guarantee sensitive-data removal from images or binary files. The source display name is self-reported, not an authenticated identity. A sanitized execution log does not establish that an entire diagnostic bundle or published asset is free of sensitive data. Truncating text or adding a hash fingerprint is not anonymization: a retained prefix still contains source text.
What to review before delivery
- Command output, error stacks, and execution evidence.
- Genes, Capsules, Recipes, Skills, and publication summaries.
- Hub request diagnostics, screenshots, issues, and shared documents.
- Example data containing usernames, paths, email addresses, device details, or customer content.
Handling rules
- Stop collecting unrelated sensitive data at the source where possible.
- Preserve structure, type, time, and error codes needed for diagnosis while replacing secret values.
- Never copy live credentials into fixtures, screenshots, or demonstration material.
- Record the redaction rule and changed fields so reviewers know that evidence was transformed.
When a command changes
If redaction changes a command or a required argument, that command must not be executed or used to promote an asset. Inject secrets from a protected environment instead and keep only argument names and redacted results in the review record.
On disclosure
Stop sharing and publishing, determine scope, rotate or revoke through the owning credential system, and clean the source and derived artifacts. Masking one UI occurrence does not remove copies already present in logs, Git history, or external systems.
Related pages
EvoX Docs · Security · Release and data safety