Know which information you are submitting
Our privacy notice explains page requests, browser preferences, Google Analytics and support correspondence. For a question about account content or a purchase, send the relevant reference privately and describe the information you need.
Do not infer end-to-end encryption or exclusive access from the word private in an interface. A specific feature would need to state such a guarantee; the general notice does not provide one.
Check public profile fields independently of a chat
A published character can expose its Personality text on the card. Cloning can also reveal the physical traits used for that character, so inspect the visibility setting before sharing.
Build a fictional history instead of embedding a real phone number, workplace or personal event that identifies someone. A private conversation and a public character submission are different choices.
Protect the ways into the account
- Use a distinct password or protect the sign-in provider you selected.
- Read the destination address before entering credentials or billing information.
- Finish shared-device sessions by signing out.
- Send receipts only through a private support route.
- Check permissions before giving a third-party tool access to browser or account data.
Make a report specific without oversharing
Identify the page, character or conversation and explain the concern with an approximate time. Crop unrelated private content out of screenshots and remove any credentials.
For a data request, say which account and what action you mean. Removing a chat, deleting a companion and closing the entire account do not describe the same request.