Understand your connection and data controls

Authorize on Fanvue; do not share your password

The OAuth connection sends you to Fanvue to authorize access. The application stores access and refresh credentials so it can use the permissions you granted; it does not need your Fanvue password. Stored OAuth tokens and application connection secrets are encrypted by the application. This is one protection, not an absolute security guarantee.

• Requested permission categories include your own/creator profile, conversations, fans, insights and media.
• Read/write chat permissions support reading context and sending configured replies. Read/write media permissions support media workflows.
• Review the actual Fanvue authorization screen: account eligibility and the permissions granted by Fanvue determine what is available.

What is used to prepare a reply

Conversation and fan data, persona settings, selected memory, media metadata and available purchase context can be processed to provide the configured workflows. The selected AI processing service receives the context needed for its request; this is not a claim that conversations stay only on your device.

Available models and processing routes depend on account settings and service configuration. Review the selected model and our Privacy Policy before using sensitive information. Do not place passwords or unrelated private information in a persona or test prompt.

Pause automation before changing a live setup

1. Use the conversation or account controls to pause the scope you intend to stop. In Autopilot, use Pause & edit.
2. Review enabled campaigns, audiences and exclusions before starting again. Saving a draft is not the same as enabling live delivery.
3. Check sent activity and error states. A successful Playground test is not proof of live delivery or a guarantee of response accuracy.

Removing a creator is different from deleting your Fanvue account

The connected-account removal workflow deletes the creator’s application record and associated operational data such as conversations, messages, memory and campaign settings. It does not delete the original account or messages on Fanvue.

Some billing and operational records are handled separately. Removing a creator is not a promise that every backup or legally required record is instantly erased. The Privacy Policy explains the retention principles; contact support for an account-level deletion or data-access request.

If you want to revoke the underlying authorization, also review the app permissions on Fanvue. Pausing automation, removing a creator in this application and revoking authorization are distinct actions.

Questions and incident reports

Contact info@fanvueautomation.eu with the affected workflow and time. Do not email access tokens, passwords or an unredacted fan conversation. Share only the minimum information needed to investigate.