Privacy notice

Fanvue embedded app

When you open the trainer inside Fanvue and approve access, Fanvue supplies a short-lived authorization token. Our server verifies your own creator profile using the read:self permission and uses your Fanvue account identifier to keep your training history and files separate from other accounts. Fanvue and Google accounts are not automatically linked by email.

The embedded app uses a short-lived session held in browser memory. It does not store your Fanvue access or refresh tokens in browser storage. We do not request access to your chats, fans, posts or media library. Your Fanvue profile is not used as a character reference or LoRA training data; you choose the image to upload. Reopen the app in Fanvue if its session expires.

Google sign-in

When you choose Sign in with Google, we request basic identity information using the openid, email and profile permissions. Google provides your account identifier, name, email address and email-verification status through AWS Cognito. We do not request access to your Gmail messages, Google Drive files, contacts or Google Photos library.

AWS Cognito stores your linked sign-in profile. The trainer uses your Cognito account identifier to associate your training requests and files with your account, and uses signed session information in a secure, HTTP-only browser cookie to verify access. Account details may also be used to verify ownership when you contact support or request deletion. These records are covered by the retention and deletion practices below.

Google sign-in information is not used as a character reference or as training data for your LoRA. We do not automatically send your Google name or email address to image-generation or GPU-training providers. Those providers receive the reference images, generated assets, prompts and file links needed for your training request; file links can contain internal account and job identifiers. Signing in does not select or import images from your Google account.

What we process

We process account and sign-in details, uploaded reference images, character names and triggers, generated training assets, training status and downloadable files. We also process payment identifiers and status, support correspondence, and technical information needed to secure and operate the service.

Your payment provider collects payment details directly. The trainer uses payment confirmations and transaction identifiers; do not send card details through support or upload fields.

Why and with whom

We use this information to authenticate your account, validate uploads, generate assets, train and deliver your LoRA, process purchases, prevent misuse and respond to support requests. Account, cloud storage, moderation, image generation, GPU training and payment providers process information needed for those functions.

The service uses AWS for cloud services and authentication, automated image screening providers including Hive, and third-party image-generation and GPU-training services. Processing may take place outside Israel. Providers receive the inputs needed to perform their part of your request; image-generation and training services need access to your reference or generated assets.

Retention and deletion

We keep account, training and delivery data as needed to provide the service and maintain access to completed purchases. Security, payment and support records may need to be retained for legal, fraud-prevention or dispute-handling purposes. Temporary download links expire and can be refreshed; link expiry is not deletion of the underlying file.

You can request access, correction or deletion by emailing support from your account email. We may need to verify ownership. We will explain any records we must retain and any limits to deletion. Avoid uploading sensitive personal information or real-person likenesses.

Cookies and security

The storefront uses cookies and browser storage for secure sign-in, session protection and preserving your in-progress training draft. Do not use a shared device for private images without clearing your local draft and signing out afterward.

Access controls and secure transport help protect your information, but no online service can guarantee absolute security. Contact support if you believe your account or files have been exposed.