The short answer
Avoid sending client lists, identity documents, passwords or private contracts to a personal account. Removing names alone may not prevent identification.
Try it in three steps
- Start with invented practice text rather than client files.
- List fields needed for the task and identifiers to replace.
- Check your organization's tool and data rules.
A practice prompt
Before you start
The company and contact below are fictional. Design masking rules first.
Practice material (fictional)
Example Lantern Co., contact Sample Lin, order DEMO-001, October 1, 12 units. The task needs daily unit totals only.Replace placeholders in the prompt with this material, or append the material if there are no placeholders. Reading time excludes doing the exercise.
Design masking rules that remove or replace identifying details in a fictional table with company, contact, order ID, amount and date. Do not request the original file.What to look for (not a recorded test result)
The aggregation does not need company, contact or order ID. Permission to share dates and counts still depends on organizational rules.
If it goes wrong
If real records are essential, confirm an approved environment and authorization; a keep this secret prompt is insufficient.
Check your result
You can explain what leaves the device, who receives it and whether that is approved.
References and scope
The links below support the concepts or product navigation. The steps and exercises are our teaching suggestions, not official certification or measured customer outcomes. Product interfaces and availability may change. References checked on 2026-10-17.