Safety
Customers will test the line. Decide where it is first.
The most common boundary requests have known patterns. Decide your answers in advance so you are not deciding under pressure.
The recurring requests
| Request | Typical risk | Platform-safe response |
|---|---|---|
| Personal contact (number, WhatsApp) | Loss of platform protections, doxxing | Decline; keep all contact on-platform |
| Personal social accounts | Cross-identification with real identity | Point to work accounts only |
| Meeting offline | Physical safety, platform ToS | Decline firmly; report if persistent |
| Gifts or mail | Address exposure | Use a P.O. box or wishlist service that hides your address, where available |
| Identifying information | Guessing location, workplace, real name | Do not confirm or deny; change subject |
| “Prove it's you” photos | Harassment, manipulation | Decline; it is often a control tactic |
Enforcement tools
- Block and mute — use them early and without guilt.
- Report — persistent boundary-pushing violates most platforms' terms.
- Escalate — threats, stalking or doxxing attempts should be documented and, where appropriate, reported to authorities.
Scripts you can reuse
- “I keep all contact here on the platform — that protects both of us.”
- “I don't do offline meetings. Please don't ask again.”
- “That's not something I offer. I'm happy to keep talking about X instead.”