Disassemble Oleg's document. Return JSON {"remove":[...],"keep":[...],"why":"..."}: remove — what to remove before sending to AI; keep - what is safe to leave and is needed for the summary; why - briefly why what is removed is dangerous. Return only JSON, no text around it.
Mechanics: the cloud service processes the request on other people's servers. Some of the data can be stored in history, end up in logs, and used to improve models - that is, the data leaves your computer. What to remove almost always: passwords, codes, CVV; passport and similar numbers; home address and geotags; medical diagnoses; trade secrets and internal documents of the employer; other people's personal data (you are responsible for them). The technique is depersonalization: instead of real data, substitute placeholders ([NAME], [SUM], [CITY]), and insert the result back into your own. The second trick is the “what if this is published?” rule: if leaking this line would be unpleasant, don’t insert it. Insider: the most dangerous thing is not passwords (they are rarely copied), but working documents - contracts, customer base, code with access keys: they are loaded “for speed”. A typical mistake: thinking that by deleting a message from history, you have deleted data from the servers - copies could remain.
Unlock access to submit solutions for instant AI review.