Client data should not be used in test contexts where access, deletion and reuse are unclear. Real invoices, contracts or names are often copied into experiments for speed.
Use anonymized examples or clearly marked demo spaces, and keep production work in protected client spaces.
Start with a narrow boundary: which website, space, file, recipient or decision is affected? This makes the task reviewable instead of turning it into a broad catch-all request.
A useful work order is: “Create an anonymized test version of this case that keeps the structure but removes client data.” For important cases, add that uncertainties must be marked visibly instead of being filled in silently.
Pay special attention to current work status, confirmed decisions and open questions. These points decide whether the result is only useful for the moment or can be found, checked and continued by the team later.
Do not copy sensitive details into prompts just to try a feature.
Testing stays safe and production data keeps proper boundaries.