nanachatBack to nanachat ↗
NANACHAT FIELD NOTEREAD SLOWLY

Controls · Safer use

Keep your exit visible. Keep your boundaries yours.

Safety is not a badge or a promise that harm cannot happen. It is a set of reachable controls, understandable states, and operating processes that must be tested.

Leave early when something feels wrong

You do not owe a stranger more time, an explanation, or a purchase. Use the visible end or leave control and move away from the conversation.

  • →Do not continue because a countdown, gift, or paid offer creates pressure.
  • →Do not share another contact method just to exit politely.
  • →If the product is unresponsive, close the active surface and avoid blind repeat actions.

Keep identifying details out of the frame

A live conversation can reveal more than intended through documents, screens, background audio, reflections, or location clues.

  • →Do not display IDs, addresses, payment details, or private account screens.
  • →Avoid sharing precise location, work schedule, or travel plans.
  • →Treat links and requests to move money off-platform as unverified.

Use Block and Report where available

Block and Report are different actions. Blocking is a user control; reporting submits a concern for review on supported surfaces. Neither action by itself proves a platform decision or a permanent cross-surface outcome.

  • →Choose the reason that best matches what happened.
  • →Provide evidence only when the form supports it and you are comfortable doing so.
  • →For immediate danger, contact the appropriate local emergency service rather than relying on an in-app report.
Keep in mind

The current product may not expose every control from every call or message state. Real-user launch remains held until those reachability and operations gaps are resolved.

Spending is never consent or access to a person

Coins, VIP, gifts, or other paid features may describe software entitlements. They never create ownership of another person, guarantee attention, or make unwanted conduct acceptable.

  • →Do not send money because someone promises a reply or relationship.
  • →Read the exact offer before continuing to checkout.
  • →Keep payment success and feature delivery separate when asking for help.

Questions, answered

What people need to know before they continue.

Does a low number of reports mean a service is safe?+

No. Report counts depend on exposure, reachability, user understanding, submission completion, review operations, and many other factors.

Will blocking guarantee no future contact?+

The interface should apply the documented block behavior, but a permanent cross-surface or cross-account guarantee requires separate operational evidence.

What if I need urgent help?+

Leave the conversation and contact an appropriate local emergency, crisis, or law-enforcement service. An in-app report is not an emergency-response channel.

nanachat

Choose your way in.