E-RP and ERP — staying private in online roleplay

By The Furtiva team · Last updated October 2026

E-RP (erotic roleplay), also written ERP, is collaborative adult storytelling — two or more consenting adults writing a scene together, usually by text on Discord, forums or dedicated apps. It is fiction, and it is normal. What it isn't is a free pass on privacy or consent: roleplay communities leak screenshots, reuse “faceclaims” of real people, and turn a bad breakup into a public log. This guide is about keeping the person behind the character safe.

First, what e-RP actually is

E-RP is writing: character, setting, tension, scene. It is not sextortion, not a demand for real photos, and not a reason to treat the other writer as their character. Three ground rules separate healthy roleplay from harm:

Adults only, 18+, always. Sexual roleplay involving minors — as characters or as writers — is not fiction anyone should touch, and in most places it is a crime to produce or exchange.
OOC is not IC. Out-of-character, you are two real people negotiating what you'll write. In-character, you're playing roles. Confusing the two is where consent gets lost.
The writer is not the character. Nobody owes you a photo because their character would send one. Real-world images always need a fresh, explicit yes.

Negotiate before the scene, not during it

Healthy RP communities do what good scene partners do: they talk OOC first. A five-line negotiation prevents most of the trouble:

Limits and squicks. What's in, what's out, what needs a check-in. Write it down; memories differ later.
Safeword or pause signal. A word for “stop the scene right now, no questions” that isn't part of the fiction.
What's private. Agree that logs, screenshots and images stay between the two of you — and that either side can end the scene and delete everything.
Age and identity check. Confirm the other writer is an adult. If you have to guess, stop.
Aftercare and out. How you both leave the scene, and how to end the connection cleanly when it's over.

Photos, selfies and “faceclaims”

Roleplay and images mix constantly, and not all mixing is equal. The distinctions that matter:

Images in e-RP, from harmless to harmful
What it is	Consent needed	Main risk
A drawn or AI character portrait	Between the writers	Low — fictional by construction
Your own photo, sent privately	Your own informed yes	Screenshot, leak, re-use as someone else's faceclaim
Another real person's photo as a faceclaim	The person in the photo (you never have it)	Impersonation, NCII-adjacent harm, reportable
A partner's intimate photo shared with you	Per act, every time	NCII — a crime in most places if re-shared
A self-destructing Furtiva link	Still your own informed yes	Minimal file afterlife — expires or is unsent

The leak problem in RP communities

Ask anyone who has been in a roleplay server long enough and they'll tell you a version of the same story: a scene ends badly, and the logs or photos end up in a callout channel, a rival server, or a folder passed around for entertainment. The pattern is structural, not personal:

Logs live forever. Discord DMs and forum threads store complete scenes, and a server bot may already have a copy of anything posted in a channel.
Screenshots settle scores. “Proof” culture turns intimacy into ammunition the moment a scene or a friendship ends.
Drama is public. Callout and “leak” servers exist to redistribute other people's material; reputation damage follows the writer, not the character.
Doxxing bridges the gap. A faceclaim, a throwaway selfie, a voice note and one mutual server can be enough to link a pseudonym to a real person.

A safer photo workflow for roleplay

If you choose to exchange real images at all, keep the file's whole life in your own hands:

Decide first, crop second. Only send what you'd survive being forwarded — face, tattoos, room and all.
Never send from a shared identity tied to your roleplay account, name or email.
Use a link, not an attachment. A Furtiva private link is invisible to search engines, dies within 24 hours or 20 views, and leaves no copy in either chat history.
Keep the unsend token. The sender's token kills the link everywhere it was pasted — after a scene, a fight or a betrayal. One tap, no negotiation.
Any image of another person needs their consent — to be photographed and to be shared. “Faceclaims” of real, unconsenting people are not a workaround.

If your trust or your image is abused

Boundaries get crossed in roleplay more often than people admit — a scene pushed past a limit, a photo shared, a log used to threaten. None of it is your fault, and you don't owe anyone continued access. Block and report the person on the platform where it happened; if you sent a Furtiva link, unsend it from your browser. For a non-consensual intimate image, file a case with StopNCII.org (adults) or Take It Down (NCMEC) to block re-uploads, and report sextortion or blackmail to the police — don't pay.

For anything hosted on Furtiva, report abuse here: we delete the file and the link, and acknowledge every report within 24 hours.

Frequently asked

What does e-RP or ERP mean?

E-RP (also written ERP) means erotic roleplay: consenting adults writing a sexual scene together as collaborative fiction, usually over text. It's distinct from ERP in business, which means Enterprise Resource Planning.

Is ERP the same as sending nudes?

No. ERP is fiction between adults — it doesn't require anyone to send a real photo. If real images do enter the scene, they need their own explicit consent every time, and they should never be a condition of the roleplay.

Do I need consent for a faceclaim in roleplay?

If the faceclaim is a real person's photo, yes — and using it without their consent is impersonation, not roleplay. Drawings, commissioned art and entirely fictional/AI likenesses don't have that problem. Never use a real person's intimate image as a faceclaim.

Are Discord roleplay logs private?

No. Discord stores DMs and channels, server bots can capture channel content, and anyone in the conversation can screenshot or export a log. Treat every scene as archivable by the other person.

How do I share a photo in roleplay without it leaking?

Don't attach it in chat. Upload it to Furtiva and paste the private link: it's excluded from search engines, expires within 24 hours or 20 views, and you keep an unsend token that kills it anywhere it was posted.

What should I do if someone shares my photos or logs after a scene?

Block and report them on the platform, unsend any Furtiva link you still control, and file a case with StopNCII.org (adults) or Take It Down (NCMEC) to block re-uploads. If it's blackmail, keep the evidence and report it to the police — don't pay.

Sources

Discord Safety Center — reporting abuse and managing server privacy
StopNCII.org — block the redistribution of intimate images (adults)
Take It Down — NCMEC — remove images of anyone under 18
RAINN — support after sexual coercion or violence

Related guides

Discord dating safely
Discord dating servers, DMs and voice chats aren't built for private photos. See what stays in history, what bots log, and how to share a link that expires.
Sending nudes safely
A candid, consent-first guide to sending intimate photos: adults only, self-destructing links, unsend anytime — and what to do if something goes wrong.
Most private way to share photos
Compare WhatsApp, Instagram, cloud links and self-destructing private links. See which way to share a photo is truly private — and which leaves a copy.

Roleplaying and want to share a scene image? Send it as a Furtiva link — private, 24-hour expiry, unsend anytime, free. See also Discord dating and sending nudes safely.