How to Send Nudes Safely

Keep your face out of frame. A face is one of the strongest and easiest ways to connect an intimate image to your identity. A unique tattoo, an identifiable room, leftover metadata, or the account next to the link can be enough on their own.

Clean the background. A plain wall is better than a room full of clues. Move work badges, mail, diplomas, sticky notes, family photos, posters, and distinctive décor out of shot. Close blinds on a window that shows a landmark or a street you could be placed by.

Check reflections. A mirror or television can reveal a person or a room you thought was out of frame. Glance at glass and screens before you send.

Crop first, then cover, then blur. Crop identifying details out entirely where possible. If cropping is impractical, cover them with clothing, a prop, shadow, or an opaque mask. Use blur only as a fallback, and only if it is strong enough that the original detail cannot reasonably be recognized. In PrivateNote, Take photo lets you crop before encryption; treat the blur brush as a last pass, not a substitute for cropping.

Capture inside the sharing tool when you can. Taking the photo in your regular camera app often creates a copy in a cloud-synced photo library. Take photo in the PrivateNote composer uses the live camera in the browser and does not intentionally save the captured image to your photo library. The JPEG is then encrypted before upload. Picking an existing library picture does not give you that benefit.

If you already took the photo with the regular camera, check whether it has synced to iCloud Photos, Google Photos, or another backup service. Delete copies you no longer want from both the device and the synchronized library, including Recently Deleted or Trash. Do not toggle your entire photo backup system on and off around a single picture.

Re-encode instead of trusting EXIF stripping. Photos often store embedded metadata—GPS, timestamps, and phone model—in more than one structure. Encryption does not remove that; it only scrambles the file as-is. PrivateNote can create a new encoded version of supported images in the browser before encryption, discarding common embedded metadata rather than uploading the original file unchanged. Leave Remove location & photo metadata on. See how to share photos securely.

Resize the file. You do not need a 48-megapixel original for a phone-sized view. Downsizing reduces leftover detail from zooming and often drops hidden metadata with it.

Avoid keeping highly sensitive images in your ordinary cloud-synced photo library. Those libraries optimize for availability, synchronization, and retention—often the opposite of what you want here. If you choose to retain one, prefer a protected or encrypted location with strong device and account authentication, and understand whether it is backed up or synchronized elsewhere.

PrivateNote is a handoff, not an archive. Expiration removes our copy of the encrypted file; it does not create a private album on your device.

Do not confuse encryption with disappearance. End-to-end encryption protects an image in transit and, in PrivateNote’s model, keeps plaintext off the server. It does not govern what the recipient does after they decrypt and view it. The same gap exists in encrypted chats—see why secrets do not belong in chat.

Treat view-once as risk reduction, not DRM. One-time secret links keep photos from sitting in a thread for years. They cannot stop someone photographing the screen with another device.

Assume today’s partner can become tomorrow’s leak. The person you trust now may not be trustworthy after a breakup. That is why a less-identifying frame still matters in a committed relationship: leftover copies outlive the relationship.

Verify who you are actually talking to. Sextortion typically starts with a fake profile obtaining an explicit photo, then threatening exposure. Never send intimate media to someone you have not independently verified. A recipient verification code helps when the delivery channel itself may be weak, but it does not prove identity.

Ask them to delete it when they are done. This is not a technical control and does not prevent screenshots, but it makes your expectation clear: the image was intended to be private and temporary, not forwarded or published.

Keep the accompanying text anonymous. A sanitized photo next to “Hey, it’s Sarah from accounting” undoes the prep work. Consider the entire payload: image, caption, and profile handle.

None of this holds if their phone is unlocked on a bar table. Ask them to use a passcode or biometric lock. Unique passwords and two-factor authentication on their accounts make it harder for someone else to open the thread or the cloud backup later. A password manager helps if they cannot keep unique logins straight.

Think about notification previews. Do not describe the contents in the message carrying the link. Lock-screen notifications can expose the context even when the photo itself is encrypted. For particularly sensitive exchanges, both people should consider hiding message previews on the lock screen.

If they will not lock the device, treat that as a reason not to send.