Understand the information involved in a visit
Our privacy notice describes browser requests, stored preferences, Google Analytics and support correspondence. If a question concerns a purchase or account content, identify that matter privately and ask about the particular information involved.
Do not treat an interface label as a promise of end-to-end encryption or exclusive access. Such a guarantee would have to be stated for the relevant feature, not inferred from the word private.
Review what a public profile can reveal
A public companion card can display Personality text. Cloning can expose the character's physical traits as well, so inspect visibility before sharing a profile.
Use invented history rather than a real person's address, workplace or private event. A conversation and a public character submission have different audiences.
Secure the routes into the account
- Protect the password or provider account used for sign-in.
- Check the address before entering credentials or payment information.
- Sign out when using a shared device.
- Keep purchase references inside private support channels.
- Review a third-party tool's permissions before connecting it to account or browser data.
Provide enough context without exposing unrelated details
For a report, identify the relevant page, character or action and an approximate time. Redact unrelated conversations and remove credentials from screenshots.
For a data request, explain the scope. Deleting a conversation, removing a companion and closing an account are not interchangeable instructions.