Skip to content
MoveToWhop
PlatformsCompareGuidesFee calculatorCreate a Whop
Start migration

Privacy

Privacy policy

The short version: your member and customer lists are processed in your browser and never reach our servers. We only handle what we need to create things in your Whop, and we don't sell personal data.

Last updated

At a glance

  • Member and customer lists stay in your browser. 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.
  • 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.
  • 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.

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.

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 an optional 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 and for permission to see and create Whop businesses. When you pick the business to migrate into, we ask for write access to that business so we can create products, pricing plans, courses, forums, chat channels and promo codes 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.

The details you approve in the wizard, such as product names, prices, course outlines and lesson text, pass through our Worker to Whop's API so they can be created in your Whop. We use them only to make those API calls.

Source platform API keys

For Kajabi and SamCart you can optionally paste a read-only API key instead of uploading an export file. The key is sent once to our Worker, used to read your products and courses, and never stored. We recommend revoking the key on the source platform 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 and any notes you add. 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. We don't use advertising or cross-site tracking cookies.

When you click “Create a free Whop” you go to whop.com with our referral code in the link, and a new Whop you create inside the migration tool is created with 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.
  • 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.