Reduce the sharing scope
Select only the files, functions, and configuration needed to explain the problem. Removing unrelated code reduces both the risk of disclosure and the review burden on the recipient.
If you can create reproducible code, prepare a minimal configuration that does not use production data and replaces it with fictitious names and values.
Points to note for each sharing destination
| Sharing Method | What to Check |
|---|---|
| Public Issue or Forum | Assume the post may remain searchable, and remove organization names and internal URLs |
| Internal chat | Check how long channel participants and history are kept |
| Email or External Contractor | Check recipients, attachments, and contractual sharing scope |
| Screen Sharing | Pre-hide notifications, tab names, history, and file paths |
Check before sending
- Make a shared copy and avoid editing the original file directly.
- Remove or mask credentials, personal information, organization-specific information, and real data.
- Full-text search for original project name, domain, and customer code.
- Confirm the recipients and visibility. If necessary, also specify an expiration date and deletion procedure.
Do not rely on automatic detection alone. The person sharing the content should perform a final read-through of the entire masked result.
Try It in Your Browser
Your input is processed entirely in your browser. Keep the original data, review the output, and only then save or share it.
Select a masking tool from supported languages