PepHop Chat Privacy: Visibility, Metadata and Policy Gaps
Read PepHop’s private-chat FAQ with its data-collection policy, distinguish audience settings from service processing, and keep unresolved operator details visible.
PepHop’s FAQ says chats are private by default unless shared, and treats bot visibility separately. Its privacy policy also describes email, usage and device-related processing. These statements do not establish zero provider processing. The policy’s country field contains “Bishui Plain, Liyue,” which does not resolve a real-world operating jurisdiction; seek clarification rather than inventing one.
PepHop’s public visibility statements do not answer every privacy question. Its FAQ describes private-by-default chats and separate private or public bot visibility. Its privacy policy describes other data processing. Read the documents at those different scopes.
Both pages were checked in the rendered browser for this guide. No authenticated account settings, data export or backend controls were tested.
Separate the object being made public
A bot profile and a conversation with that bot are different objects. Do not infer that a public bot automatically exposes every user’s conversation, or that a private bot eliminates all service-side account data.
| Object or process | Relevant question |
|---|---|
| Bot profile | Which profile material is visible to others? |
| Conversation | Was it shared or otherwise made public? |
| Account and usage data | What does the provider process for stated purposes? |
For a fictional case, a user discovers a public character and starts a conversation. The public profile’s existence alone is not evidence that the conversation transcript was published. Keep observations about the two objects separate.
Read the metadata layer
The policy describes email and automatically collected usage or device information. It also discusses service providers and purpose-based retention. Those statements qualify a broad assumption that a private chat setting means nothing about the visit or account is processed.
They do not independently establish a full technical data flow for a particular conversation. Avoid calling the service end-to-end encrypted or claiming no authorized person can ever access relevant records without supporting evidence.
Keep a visible policy gap unresolved
The country definition on the policy page reads “Bishui Plain, Liyue.” That fictional-location wording does not identify a real-world operating jurisdiction. It should not be copied into a business profile as an actual country.
This is a concrete limitation in the public text, not proof of a particular server location or a conclusion that every other statement is false. If operator identity or jurisdiction matters to your decision, ask for clarification through the official contact route.
Ask about the process you mean
A visibility question, a retained-data question and an operator-identity question need different answers. State which one remains unresolved rather than asking for an undefined guarantee of complete privacy.
Use non-sensitive fictional context while evaluating a service. Keep other people’s identifiers out of unnecessary examples, and avoid forwarding an entire conversation merely to ask a policy question. A useful answer identifies the object, data category or operator detail actually under discussion.
Sources and verification
This guide distinguishes published documentation from examples and observations. Feature access, policies and account screens can change; the linked source governs its own terms.