How to Ask a Recipient to Keep an Email Confidential

Define “confidential” in concrete terms

Before writing, decide what boundary you need. Is the message only for the named recipient? May they show it to a specific teammate who is helping with the matter? Can they discuss the issue without sharing your exact wording? A plain request answers these questions rather than relying on a broad label.

Use names or roles when possible, and describe any permitted exception. For example, you might allow the recipient to consult one named project lead but ask them not to circulate the message to the wider team. If you do not know who may need access, ask before sending or keep the message general.

State the limits without sounding vague

Put the request near the beginning, where it is easy to notice. Use direct, courteous language: “Please keep this message between us. Don’t forward or quote it. If someone else needs to be involved, please check with me first.” That makes the audience, restricted actions, and next step clear.

Avoid wording that sounds absolute or assumes control you do not have, such as “This email cannot be shared.” A sender can ask for discretion, but cannot prevent a recipient from copying or forwarding a message. Do not imply that a confidentiality label, subject line, or email setting guarantees privacy.

Think about the message and its attachments

A confidentiality request does not make sensitive details safer to send. Include only information the recipient needs to act. Check whether an attachment contains extra pages, comments, identifying details, or other material you did not intend to share. Consider whether a short summary would meet your need instead.

If the information would be damaging if forwarded or read by someone else, pause before sending it. Ask the recipient what channel is appropriate for the material, and follow any relevant workplace process. Do not assume that email can be recalled everywhere or that every recipient’s system handles it the same way.

Check the audience before you press send

Review the To, Cc, and Bcc fields, including suggested addresses. Make sure each visible recipient belongs in the conversation. If the message is meant for one person, remove people who only need an update; you can send a separate, less sensitive summary to them if appropriate.

Check the subject line and quoted thread as well. A subject can reveal the topic on its own, while an older message below your reply may contain details or recipients you had forgotten about. Attachments should match the audience too. The request is easier to honor when the message itself does not accidentally widen the circle.

Ask for acknowledgment and agree on exceptions

A brief acknowledgment helps confirm that the recipient saw your request; it does not prove that the message stayed private. If the boundary matters, ask them to reply that they understand who may see it and what they should do if someone else needs access.

Make the exception practical. For instance, ask the recipient to contact you before forwarding, or to tell you if they cannot handle the matter without involving someone else. If they say they need to share it, decide together what limited information can be passed along and to whom.

A short example and final check

Here is a request that defines both the audience and the next step. Replace the bracketed fields with details that fit your situation; do not leave a recipient guessing about who is included.

• Are the intended readers named or clearly described?
• Are forwarding, quoting, and discussion limits explicit?
• Have you checked recipients, subject, thread, and attachments?
• Did the recipient acknowledge the boundary or flag an exception?

To: [recipient@example.com]
Subject: [brief, non-sensitive subject]

Hi [recipient name],

I’m sharing [brief description] so you can [specific purpose]. Please keep this message between us: don’t forward it, quote it, or discuss the details with others. If someone else needs to be involved, please check with me first. Please reply to confirm you understand this request.

Thanks,
[your name]