Write the decision before changing the system
This guide is a planning exercise for an application operator. It does not represent a PrivacyNodes deployment, support action or measured customer result. Classify logs by purpose: request diagnosis, security event, job outcome or audit record. Exclude authorization headers, API keys, cookies, database connection strings and complete payloads unless a policy and need justify their handling.
Rehearse the change with controlled inputs
Use stable request IDs and UTC timestamps so a short redacted record can connect an API symptom to a release or worker event. Apply rotation and deletion deliberately; disk growth is not a retention policy.
Use synthetic requests and test identities while checking the change. Do not expose secrets or customer data in a command, log excerpt or support note.
Verify the outcome and record the remaining limit
Test that an operator can diagnose a synthetic error from the retained fields. Review access and retention after a new integration changes what the application writes.
Capture UTC time, artifact or configuration revision, redacted symptoms and the next owner.
Official reference
This source was reviewed for the technical boundary in this guide; it does not document a PrivacyNodes test or provider capability.