Privacy
Privacy policy
The short version: we never store your member and customer lists. Export files and the MoveToWhop Sync extension are read in your browser, and if you log in with Patreon or Gumroad, their member lists pass through our server to your browser without being kept. We only handle what we need to create things in your Whop, plus anonymous counts of how our AI prompt and agent briefing are used, and we don't sell personal data.
Last updated
At a glance
- We never store member or customer lists. Export files you load into the migration tool or the member CSV converter are read and cleaned on your device. They aren't uploaded to us.
- The MoveToWhop Sync browser extension reads only your own signed-in account, in your browser. Member lists it reads stay in your browser; it never asks for or stores your password.
- Logging in with Patreon or Gumroad is read-only and short-lived. Their member lists pass through our server to your browser in memory, never stored or logged, and the login is dropped when the sync ends (within 30 minutes at most).
- Whop sign-in tokens are kept in encrypted cookies so our server can make Whop API calls for you during a migration. Signing out revokes the token and clears the cookies.
- Syncing from a link reads only public pages, without logging in. Member lists stay in your browser; what you choose to move passes through our server to Whop.
- Source platform API keys are used once and never stored.
- If you ask us for help, we keep the details you send so we can reply.
- No advertising or cross-site tracking cookies. We count prompt copies, agent-briefing fetches and moves started without any personal data (see usage counts).
Member and customer lists
When you load a member, customer or subscription export (for example a CSV from Skool, Kajabi or Patreon) into the migration tool or the member CSV converter, the file is parsed and cleaned in your browser. Names, emails, plans and renewal dates from that file are not sent to our servers.
So your work survives the Whop sign-in redirect and reloads, the migration tool saves your progress, member list included, in this browser's storage. Start over clears it.
The MoveToWhop Sync extension reads member lists the same way: in your browser, from your own signed-in tab, straight into the migration tool (see below).
If you log in with Patreon or Gumroad instead of loading a file, the list comes from that platform's API through our Worker (see below) and is then handled in your browser exactly like a file.
Whop's API doesn't let third-party apps add members to a Whop, so the tool doesn't need your member list on a server. Instead it prepares claim links for you to share with your members.
One exception: our agent tools (the MCP server and the /api/agent API) include a converter that AI agents can call with a CSV. If an agent sends one, it is processed in memory to return the cleaned result and is not stored or logged. Agents are instructed to ask you first, and the in-browser tools above remain the default.
Connecting your Whop
You connect Whop with Whop's official sign-in (OAuth). We never see your Whop password. When you sign in we ask Whop for your basic profile and email, for permission to see and create Whop businesses, and for permission to read and post in forums (Whop accepts forum posts only from your own sign-in, so the welcome post and any community posts you move are posted as you). Once the business to move into is set (your only Whop, the one named like your site, one you pick, or a new one the tool creates if you have none), Whop asks you to approve write access to that business so we can create products, pricing plans, courses, forums and chat channels in it.
The access tokens Whop issues are stored in encrypted cookies in your browser. Our server, a Cloudflare Worker, reads them only to make the Whop API calls you start in the tool. Signing out of the tool revokes the token with Whop and clears the cookies.
When you press Move to Whop, the details you chose to move, such as product names, prices, course outlines, lessons, community posts and sent newsletters, and your business name, pass through our Worker to Whop's API so they can be created in your Whop. Images and files you move are copied the same way: the Worker fetches each one from its address on your old platform and uploads it to Whop. We use them only to make those API calls and don't store them.
Syncing from your link or the browser extension
When you paste a link to your store, school or community, our Worker fetches that public page (for Skool and Patreon, the public About or membership page instead) the way a logged-out visitor would. When it is a school's home page with no course outline (Thinkific, Teachable, LearnWorlds), it also fetches up to 3 course pages that page links to on the same school. It identifies itself as MoveToWhopBot, never logs in, never sends cookies, and stops at any page that blocks bots. It reads product names, prices, course outlines and your brand name from the page. When the page doesn't include that data in a structured form, the page's text and the page data it embeds (title, meta tags, structured data) are sent to Cloudflare Workers AI to draft it, and AI-drafted prices and course outlines are marked for you to check. We don't store the page or the result. The result goes back to your browser only.
The MoveToWhop Sync browser extension (Chrome, Edge and Brave) syncs your own account without export files. It runs only in your browser, on platform tabs where you are already signed in, and reads nothing until you approve it for that platform and it confirms you own or run the account. Depending on the platform, it reads your products and prices, courses and lessons, community posts and comments, member list, payments (orders and subscriptions with their status), email subscribers and leads with their tags, sent newsletters, and your website's address with the list of its pages, and passes them to the migration tool open in your browser. Member lists, payments and subscribers stay in your browser. What you choose to move (products, courses and lessons, community posts and comments with their authors' names, sent newsletters, and the images and files in them) passes through our Worker to Whop's API without being stored. The extension never asks for your password and never stores your login; the only thing it saves is that you approved it for a platform. On Kajabi, Hotmart and InviteMember, whose dashboards authenticate their own API with a token kept in the page, it uses that token only toward that platform's own API, in that tab, and never saves it or sends it anywhere else. Kajabi and Podia keep community posts on your own site (yourname.mykajabi.com, yourname.podia.com), so the extension reads them there. On Skool it reads your member list through Skool's own member export, the way its Export button does; Skool may email you a code first, which you type in the migration tool. For that export it reads one cookie, Skool's own device id (client_id), and sends it only to Skool (api2.skool.com) with the export request, as Skool's Export button does; it never stores it or sends it anywhere else, and it reads no other cookie.
Logging in with Patreon or Gumroad
Where the migration tool offers Log in with Patreon or Log in with Gumroad, you sign in on that platform's own page (OAuth) and approve read-only access. We never see your password. We ask Patreon to read your profile, your creator page and its tiers, your members and their emails, and your posts. We ask Gumroad to read your profile and products and your sales.
The platform gives our Worker an access token. It is kept only in an encrypted cookie that page scripts can't read, limited to that platform's sync address on this site, for at most 30 minutes. The longer-lived refresh token the platform may also send is thrown away. When the sync ends, or you close the tab or leave the page mid-sync, the tool asks the Worker to drop the cookie and to revoke the token with Gumroad. Patreon offers apps no way to revoke a token, so you can also remove MoveToWhop from your connected apps on Patreon or Gumroad whenever you like.
With the token, the Worker reads your products and prices (Patreon tiers, Gumroad products and memberships), your business name and page address, and on Patreon your posts. Member lists are read a batch at a time and each batch goes straight back to your browser: for each member, only their name and email, what they bought or which tier they're on, their status, price, billing interval and renewal or charge dates. Addresses, notes, license keys, card details and custom fields are never read out. Nothing is stored or logged on our side; your browser then keeps the list with your saved progress, like a loaded file.
Source platform API keys
If Sync can't read your Kajabi public page and the browser extension can't run, you can paste a read-only Kajabi API key (a Client ID and Client secret). The key is sent once to our Worker, used to read your products and course outlines, and never stored. The key never reads members. We recommend revoking the key in Kajabi once your migration is done.
We never ask for your password on any platform.
Help requests
If you ask us to run a migration for you, the form collects your name, email, the platform you're moving from, an approximate member count, any notes you add and, if you answer it, how you heard about us. We use these to reply and do the work. Emails you send to hello@movetowhop.com are handled the same way. Ask us any time and we'll delete them.
Hosting and cookies
This site and its API run on Cloudflare. Like any host, Cloudflare processes technical data such as IP addresses to deliver the site and protect it from abuse.
The only cookies we set are the ones that keep your Whop connection working during a migration (including the encrypted session described above), and only once you start connecting Whop, plus, if you log in with Patreon or Gumroad, a 10-minute cookie that ties the login to your browser and the encrypted access cookie described above. We don't use advertising or cross-site tracking cookies.
Usage counts
To see which parts of the site help, we count four things: when someone copies the prompt for an AI assistant, when someone opens an AI assistant with it (which button, and on which page), when an AI agent fetches our agent briefing, and when a move starts in the migration tool (which platform it's from, and whether the visit came from an AI assistant such as chatgpt.com or from an agent's handoff link). Each count stores the page path without its query string, the referring site's host (for example chatgpt.com), the button and page type, the short tag the copied prompt adds to the briefing link, and a browser or bot family (such as “browser” or “chatgpt-user”) read from the User-Agent. It never stores an IP address, the prompt text, a query string or a link you pasted, your Whop business, a cookie or any other personal data. To tell a move that came from an AI assistant, the migration tool keeps that assistant's host in this browser tab's session storage until the tab closes. The counts are kept in Cloudflare Workers Analytics Engine.
Referral links
When you click “Create a free Whop” you go to whop.com with our referral code in the link, and if you don't have a Whop yet, the one the migration tool creates for you carries that code. That's how Whop credits us with a referral commission (see how we make money). Once you're on whop.com, Whop's own privacy policy applies.
Your choices
- Sign out of the tool at any time to revoke our access to your Whop.
- Revoke any API key you created for the migration on the platform that issued it.
- Remove MoveToWhop from your Patreon or Gumroad connected apps at any time.
- Email hello@movetowhop.com to see or delete anything you've sent us.
Changes and contact
If we change how we handle data, we'll update this page and its date. Questions: hello@movetowhop.com.