FanWake uses the official Fanvue API to automate fan conversations in your voice. Here is exactly how it connects, what it reads, and what it does with it.
The connection
FanWake is built on the same API integration channel that Fanvue provides for authorized third-party tools. It does not scrape, simulate browser sessions, or use any unofficial access method.
From the dashboard, go to Account and click Connect Fanvue Account.
You're redirected to Fanvue's official OAuth login. Your credentials go directly to Fanvue — FanWake never sees them.
Fanvue sends FanWake a scoped access token. FanWake stores only this token. You can revoke it any time from either platform.
Official integration. Using the official Fanvue API means your account operates within Fanvue's own terms and guidelines for authorized automation — the same way any other Fanvue-approved tool connects.
The AI pipeline
Every reply FanWake sends goes through seven steps. Here is exactly what happens between a fan pressing send and your reply arriving.
The moment a fan sends you a message, Fanvue's API notifies FanWake. This happens in real time — there's no polling or delay on FanWake's end.
FanWake retrieves the recent message history for that fan — up to 50 messages on the Pro plan, 20 on Starter. This gives the AI the full thread to work from, not just the latest message in isolation.
FanWake loads the persistent Fan Memory profile for that fan: their name, interests, things they've mentioned over time, and any notes you've added manually. This prevents the AI from asking questions it already knows the answer to.
FanWake combines your character's name, backstory, communication style, Q&A training pairs, emoji preferences, and active conversation rules into a unified context. This is the "voice" the AI writes in.
The full context — conversation history, fan memory, persona — is sent to the AI model. The model generates a reply that fits your persona and the specific moment in that conversation. Average generation time is under 60 seconds.
Depending on your approval mode, the reply is either queued in your dashboard (and optionally pushed to Telegram for one-tap approval) or sent automatically. You can switch modes at any time without affecting active conversations.
The approved or auto-sent reply is delivered directly to the fan through the official Fanvue API. From the fan's perspective, it arrives as a normal message from you — there is no external link, no redirect, no sign that a third-party tool was involved.
Your data
Transparency about data handling is important to us. Here is a plain-language breakdown of exactly what FanWake touches and what it does not.
What FanWake accesses
Your Fanvue inbox messages and fan list — only what's needed to generate replies and identify re-engagement targets. FanWake does not access your Fanvue payment data, financial history, or account settings.
What FanWake stores
Your persona configuration, Fan Memory profiles, and PPV templates are stored in your account. Message content is processed in real time and is not retained beyond what's needed for the active context window.
Your Fanvue credentials
Your Fanvue password never touches FanWake's servers. The OAuth flow means you authenticate directly on Fanvue's own login screen. FanWake receives only a scoped access token — not your credentials.
Infrastructure
FanWake runs on EU-based cloud infrastructure. All data is encrypted at rest and in transit. Fan Memory and persona data are stored only in your account and are never shared with other creators or used to train AI models.
For the full details, read our Privacy Policy.
The AI model
FanWake uses leading large language models to generate replies. The default model is selected for the best balance of quality and speed. Pro plan creators can choose their preferred model from the settings.
Up to 50 messages
Context window
Pro plan
1–3 minutes
Reply time
Average
10 languages
Languages
Auto-detected
No credit card. Live in 2 minutes. Works with Fanvue.