Skip to content

Privacy notice

What personal data Earncrest holds, why, who sees it, how long we keep it, and your rights. Last updated: 12 November 2026.

The short version

  • Earncrest is run by Virtascend Ltd. We’re responsible for the personal data in this notice.
  • If you’re a seller, we hold your account, your profile and what we read from your Stripe or PayPal account, to work out and publish your certificate. You choose whether people see a band or exact figures, and whether you appear on the leaderboards.
  • If you connect a social account by signing in to it, such as Facebook or TikTok, we receive only what that network shares with your permission, we never post for you, and we delete it when you remove it from your dashboard.
  • If you’ve paid a seller who uses Earncrest, we never store your name, email address, card details or PayPal account ID. We keep codes made from them that we can’t turn back into your details, with each payment’s amount and date, to count customers and spot fraud.
  • If you’re a client or lead of a seller who connects their CRM, we never keep your name or contact details. We keep only facts about each deal, such as its stage, amount and dates, to work out the seller’s close rate and other totals.
  • If you’re visiting, our analytics don’t use cookies or store anything on your device. Only the Proof Kit’s pages ask to use Meta’s cookies, and they stay off unless you accept. Searches are kept as the words searched, never who searched. If you ask us to email you about a seller or the leaderboard, join a waitlist or ask for the Proof Kit, we email you only about that, and every email has a link to stop.
  • We don’t sell personal data or show ads.
  • Wherever you live, you can download or delete your data from your dashboard, and complain to us, to the ICO or to the regulator where you live.

1. Who we are

Earncrest (earncrest.org) is run by Virtascend Ltd, a company registered in England and Wales, company number 15192371, registered office Lytchett House, 13 Freeland Park, Wareham Road, Poole, BH16 6FA, United Kingdom. We’re registered with the Information Commission (the ICO), the UK’s data protection regulator, registration number ZB787390.

Contact us at support@virtascend.com, or write to us at our registered office. Our data protection officer is John-James Gardiner: reach them the same ways, with “Data protection” in the subject line or at the top of your letter.

2. Who this notice covers

  • Sellers: sales coaches, consultants and creators with an Earncrest account (section 3).
  • Buyers: people who paid a seller whose Stripe or PayPal account is connected to Earncrest (section 5).
  • Clients and leads: people in the deal records of a seller who connects their CRM (section 5A).
  • Visitors: anyone using earncrest.org, including Check a sales coach, the leaderboards, the waitlists and the Proof Kit (section 7).
  • Anyone who reports a certificate or emails us (section 7).

3. Sellers: what we hold and why

Your account. Your email address; your password, which our sign-in provider stores only as a secure hash; if you add an authenticator app, the secret it uses, and a note of which app is yours; records of your sign-ins, including their times and IP addresses, which our sign-in provider keeps for security; and, while your account has no authenticator app, a note of the sign-in that showed both your password and a code we emailed you, with a fingerprint of that password that can’t be turned back into it. Why: to give you an account and keep it secure. Lawful basis: contract, and legitimate interests for security (keeping accounts safe from misuse).

Your profile and certificate. Your name, handle, one-line description, category, niche, country, website (your Work with me link) and, if you add one, your photo. We make a new copy of your photo and keep only that, without the original file’s details, such as the camera or where it was taken. Your choices: whether people see a band or exact figures, the currency, and whether you appear on the leaderboards. If you add them: your refund policy in your own words, your booking page and checkout page links, and whether you’re hiring closers or working with affiliates. Why: to publish your certificate as you choose. Lawful basis: contract.

Owner verified checks. The social accounts you add with a code in your bio, which a person at Earncrest checks by hand; the website domains you verify; the code you put in a product’s name in your Stripe account to show you control it; and any documents you send for an ownership review. Why: to show buyers the business is yours. Lawful basis: contract. We delete review documents as soon as we’ve decided, keeping only the decision and its reason.

Social accounts you connect by signing in. You can connect some social accounts by signing in to them instead. The network first shows you what it will share with Earncrest and asks your permission. We ask for as little as each network allows, our access can only read, and we never post or act for you. Depending on the network and what you allow, we receive:

  • Facebook: the ID Facebook gives you for Earncrest alone, the name on your Facebook profile and, if you allow it, the link to your profile. We read these once and keep no access to your Facebook account.
  • Instagram (business and creator accounts): your account’s IDs, username and name, and its follower and post counts.
  • Threads: your account’s ID, username and name and, if you allow it, its follower count.
  • TikTok: your account’s IDs, username and display name and, if you allow it, its follower, like and video counts.
  • X: your account’s ID, username and name. We read these once and keep no access to your X account.

For Instagram, Threads and TikTok, we keep encrypted tokens that let us read the account and its counts again, about once a day. Why: to show buyers that the accounts on your certificate are yours, with their counts, such as how many people follow them, and to help buyers find your certificate. Lawful basis: contract. Where it comes from: the network, with your permission. We use what a network sends us only for this. We never sell it or use it for advertising. Publicly, it appears only on your certificate, and Check a sales coach finds your certificate by the account’s username (section 4). Only our service providers handle it for us (section 8).

Removing a social account. Remove it from your dashboard at any time, and we delete it at once, with its counts and any tokens; the copies in our backups are gone within 7 days. If you remove Earncrest in the network’s own settings instead, we delete the account’s tokens as soon as we learn of it and stop updating the account, but it stays on your certificate, with its last counts and their date, until you remove it from your dashboard. You can also ask Facebook, Instagram or Threads, in their settings for apps and websites, to have Earncrest delete your data. We then delete every account you connected from that network, with its counts and tokens, and give you a confirmation code and a page where you can check the deletion. We keep a record of the request (the code, the network, how many accounts we deleted and the date) for 90 days.

What we read from Stripe. You connect Stripe through the Earncrest app, which can only read your account. We keep:

  • your Stripe account’s ID, business name, display name and website, to check it matches you, and to fill in your name and website for you to check when you first give your details;
  • for each payment: its amount, currency and date, any refunds, and any dispute’s status and amount;
  • for each payment, a code for the customer and one for the card (section 5), and whether the payment came from your own email address or domain.

From these we work out your figures each day: net revenue (as a band, or exact if you choose), refund rate, dispute rate, customers in the last 90 days, how far back your history goes, and whether one customer brings in most of your revenue. Why: to work out and publish your figures, and to check them for fraud. Lawful basis: contract for the figures; legitimate interests for the fraud checks (keeping certificates honest for the buyers who rely on them).

What we read from PayPal, if you connect it. You connect PayPal by signing in to it and giving Earncrest one permission: to search your account’s transactions. We search with our own credentials, on your behalf, so we never hold your PayPal password or a token for your account, and we can’t take payments, move money or change anything in PayPal. We keep:

  • your PayPal account’s ID and the legal name PayPal gives for it, to check it matches you;
  • for each payment you received for something you sold: its amount, currency and date, and any refund, dispute or hold against it, with its amount and date;
  • for each payment, a code for the customer (section 5), and whether the payment came from your own email address or domain, or from your PayPal account’s email address.

PayPal tells us your PayPal account’s email address when you connect it, and each time we read. When you connect it, we check the account is yours: if the address is the one you use for Earncrest, or at a domain you’ve verified, it’s connected straight away; if not, we email a link to that address, which you open while signed in to Earncrest to confirm the account is yours. Until then we read nothing from it. We keep the address until the account is confirmed, or for 7 days at most, and never show it to anyone. If the account isn’t yours, its owner gets that email, and nothing from their account is read. When we read, we use the address only for the last check above, and never store it. Your figures are worked out from your Stripe and PayPal payments together, as above, for the same reasons and on the same lawful bases; checking whose account it is relies on legitimate interests (making sure a certificate counts only its seller’s own sales). Where it comes from: PayPal, with your permission, which you can take back in PayPal at any time.

What we read from your CRM, if you connect one. You connect HubSpot or GoHighLevel through the Earncrest app, which can only read. We keep:

  • your CRM account’s ID and name, and the names of your deal pipelines;
  • for each deal: its ID in your CRM, its pipeline and stage, whether it’s open, won or lost, the dates it was created and closed, how often its stage or outcome changed and, from HubSpot, its amount and currency;
  • your choices: which pipelines count, and which figures may show.

From HubSpot, we never read contacts, companies, deal names, notes, emails, calls, meetings, tasks or files. GoHighLevel sends each deal with its name and its contact’s name, email address and phone number: we drop them as they arrive, and never store or log them (section 5A). From what we keep, we work out your sales figures each day: close rate, deals won, how long deals take to close, and the share of your closed deals your chosen pipelines hold, each only once there are enough deals behind it. Nothing from your CRM is public yet. Disconnecting deletes your deal records, pipelines and figures at once, and ends our access. Why: to work out the sales record you choose to show, and to check it for fraud, for example against the revenue we read from Stripe or PayPal. Lawful basis: contract for the figures; legitimate interests for the fraud checks (keeping certificates honest for the buyers who rely on them). Where it comes from: your CRM, with your permission.

Fraud checks. Every day we check the figures for signs of manipulation: for example, payments from the seller’s own address, one card paying as several customers, a Stripe, PayPal or CRM account that’s connected to another profile, won deals in a CRM that far exceed the revenue we read from Stripe or PayPal, or CRM records rewritten in bulk. The results and our decisions aren’t public, apart from “Under review” on a certificate a person has suspended (section 4). Lawful basis: legitimate interests (preventing fraud). See section 6.

We treat fraud flags, and reports that accuse a seller of dishonesty or of posting illegal content, as criminal offence data: the law counts suspicions of an offence, proven or not. We handle them under the condition for preventing, investigating or detecting unlawful acts (Data Protection Act 2018, Schedule 1, paragraph 10), with a policy document that sets out how we keep them accurate, secure and no longer than we need them.

Views. How many people saw your certificate and badge each day, the website domains your badge is shown on, how many clicked your Work with me, Book a call and checkout buttons, and how many Check a sales coach searches showed you, with the words searched and the website the search came from. Nothing about the visitors themselves. Lawful basis: legitimate interests (telling you how your certificate is used, and spotting copied badges).

Proof links. If you make links for your prospects: the name you give each link (we refuse email addresses and phone numbers in it), and when and how often it was opened. Nothing about who opened it. If you put a prospect’s first name in a link’s name, you’re responsible for having a reason to. Lawful basis: contract.

Emails. A code to sign in with, while your account has no authenticator app; the link back to Get verified, when you ask for it; one email when we’ve finished reading your payment account for the first time and your figures are ready; security alerts (for example, when a Stripe or PayPal account is connected, your password changes or your Work with me, booking or checkout link changes), alerts when we can’t read your Stripe or PayPal account, our decisions on your checks and your certificate, a reminder a month before a social account or website on your certificate needs checking again, an email when one of your proof links is opened, a weekly summary of your views and searches (which you can turn off), and, if you ask for a CRM, one email when it’s ready. We don’t send marketing emails. Lawful basis: contract, and legitimate interests for security alerts.

Paying for the selling tools. If you take a free place or subscribe: your plan, your free place’s number or your subscription’s status and next payment date, the Stripe IDs that link your account to your payments, and which version of the Selling tools terms you agreed to, and when. If you subscribe, we give Stripe your email address and account ID so it can take the payments for us. Stripe collects your card and billing details itself, and we never see your card number. If you take a free place, a one-way code made from your Stripe or PayPal account’s ID, so each account takes only one place. Why: to give you the tools you’ve taken or paid for, and to keep the payment records the law requires. Lawful basis: contract; legal obligation for the payment records; legitimate interests (preventing fraud) for the one-way code.

Activity log. A record of sensitive actions on your account, such as connecting Stripe or PayPal, or publishing, with your account ID. Lawful basis: legitimate interests (security, and answering questions about your account).

CRMs you ask for. Which CRMs you ask us to connect, and when, so we know which to build next and can tell you when yours is ready. Lawful basis: legitimate interests (building what sellers need).

Product analytics. Events such as “profile published”, linked to your account ID only, never your name, email address or figures. While you’re joining, the steps you reach are counted with the site’s visits (section 7), under that day’s visitor code, not your account ID. Lawful basis: legitimate interests (understanding how Earncrest is used, so we can improve it).

Do you have to give us this? No law requires it. But we need your email address and a password to give you an account, a name and a handle to publish a certificate, and a Stripe or PayPal account to work out your figures. Everything else, such as an authenticator app, a photo or social accounts, is up to you, though the Owner verified tick needs a social account.

4. What’s public

Your certificate at earncrest.org/v/your-handle shows: your name, photo, description, niche and country; when you joined Earncrest, and your verification ID; your ticks, and your Founding number if you have one; your figures as you chose them; your refund and dispute rates, customers and history, with a note if most of your revenue comes from one client; the social accounts you connected or verified, with the counts we read (followers, and posts, videos or likes) and the date we read them, unless you hide the counts; the website you verified; your Work with me link; and, if you add them, your refund policy and, with the selling tools, Book a call. A Facebook profile shows as your name, linked to your profile if you allowed it, and Facebook decides who can open that link. Check a sales coach finds your certificate by your name, handle, website or social handle, and anyone can compare it side by side with up to two others.

Your badge, your share images and, with the selling tools, your checkout page and widgets show the same figures, without your social accounts. On other websites, a badge or widget can take up to an hour to change.

If a person at Earncrest suspends your certificate while we check it, for example after a serious fraud flag, it says “Under review” and hides your figures until we’ve decided. It says that being under review isn’t a finding against you.

If you choose to appear on the leaderboards, they show your name, photo, niche, country, band (or exact figure), rates and customers. Only sellers on the leaderboards can win one of our yearly awards, which name each winner with the rate behind their award, and say how many sellers qualified.

If you’re Revenue verified and say you’re hiring closers or setters, or working with affiliates, our list of offers from revenue-verified sellers shows your name, photo, niche, ticks, when you joined, your band, rates and customers, lowest refund rate first. You can leave it at any time from your dashboard.

Your refund and dispute rates may also count towards your niche’s typical range, which shows the middle half of sellers’ rates and the median, never anyone’s name. A niche’s range appears only once 10 sellers count towards it, whether or not they’re on the leaderboards.

Unpublishing your certificate takes all of this down on Earncrest at once. Other websites may show what your badge last said for up to an hour.

5. If you’ve paid a seller who uses Earncrest

When a seller connects their Stripe account, we read their payment records from Stripe. Those records include each customer’s billing details, because Stripe always sends records whole. When a seller connects their PayPal account, we read their transactions from PayPal, and each one comes with the payer’s details, such as their name, email address and PayPal account ID.

  • What we keep about you: for each payment, its amount, currency, date, refunds and any dispute, as part of the seller’s business records; a code made from your customer details (for a PayPal payment, your PayPal account ID, or your email address if PayPal doesn’t give one) and, for a Stripe payment, one made from your card, using a secret key that only our payment-reading system holds; and whether the payment came from the seller’s own email address or domain.
  • What we don’t keep: your name, email address, postal address, phone number, card details or PayPal account ID. We use your email address and PayPal account ID for a moment, in memory, to make the code and to check the payment isn’t from the seller, then discard them. They’re never stored or logged.
  • Why: to count a seller’s customers accurately, to work out their refund and dispute rates, and to spot fraud, such as a seller paying themselves. Lawful basis: legitimate interests (honest figures for the buyers who rely on them, and preventing fraud).
  • Where it comes from: the seller’s Stripe or PayPal account.
  • Who sees it: no one outside Earncrest. Certificates show only totals and rates, never single payments or codes.
  • How long we keep it: 25 months on a rolling basis. It’s deleted as soon as the seller disconnects the account it came from, or takes back our permission in PayPal, and the secret key behind the codes is destroyed at the same time.
  • Your rights: we can’t tell who you are from the codes, so we may not be able to find your payments unless you help us, for example by telling us the seller, the date and the amount. Then you can use the rights in section 11. We can’t tell you about this directly, because we never keep your contact details, so we tell you here.

5A. If you’re a client or lead of a seller who connects their CRM

When a seller connects their CRM, we read their deal records from it. A deal usually relates to a client or lead, but we never keep who: no names, email addresses, phone numbers, companies, deal names, notes or messages. From HubSpot, we don’t ask for them at all. GoHighLevel sends each deal with its contact’s name, email address and phone number whatever we ask for: we drop them as they arrive, and never store or log them.

  • What we keep about deals: for each deal, its ID in the seller’s CRM, its pipeline and stage, whether it was won, lost or is still open, the dates it was created and closed, how often its stage or outcome changed and, from HubSpot, its amount and currency.
  • Why: to work out totals about how the seller sells, such as the share of deals they win, and to check those totals for fraud. Lawful basis: legitimate interests (giving buyers an honest picture of a seller’s sales, and preventing fraud).
  • Where it comes from: the seller’s CRM, read with the seller’s permission.
  • Who sees it: no one outside Earncrest, apart from the seller, who can download their own records. Nothing from a CRM is public yet, and nothing about a single deal ever will be.
  • How long we keep it: 25 months on a rolling basis. It’s deleted as soon as the seller disconnects their CRM.
  • Your rights: we can’t tell who you are from these records, so we can’t find yours unless you help us, for example by telling us the seller and the deal’s dates. Then you can use the rights in section 11. We can’t tell you about this directly, because we never keep your contact details, so we tell you here.

6. Automated decisions

A seller’s figures, band and leaderboard place are worked out automatically from their Stripe and PayPal data, by the rules on our Methodology page.

The Revenue verified tick is automatic too. It needs a Stripe or PayPal account we’ve read in the last 72 hours, at least 30 days of payment history, and no serious fraud flag waiting for review. One flag is raised automatically as serious: when someone tries to connect a Stripe or PayPal account that’s connected to another profile, or one we’re holding back from a deleted account (section 10). It holds the tick back until a person at Earncrest has looked at it. Every other flag goes to a person, and only a person can decide that it’s serious.

When your tick is on hold, your dashboard says so. Email support@virtascend.com and we’ll explain the decision, hear your side, have a person review it, and let you challenge it.

7. Visitors, and people who report a certificate or email us

Analytics. The pages you view, the links and buttons you click (never the text on the page or anything you type), how quickly pages load, whether the security check on a form couldn’t run, and your browser and device type. If you start joining, also which steps you reach and, when a step refuses something, which rule it was (for example, that a password was too short): never what you typed, your email address, your name or your figures. Nothing is stored on your device. To count each visitor once a day, our analytics provider makes a code from your IP address, your browser and the date, then discards your IP address, so your location isn’t recorded. The code changes every day, so visits on different days aren’t linked. Lawful basis: legitimate interests (understanding how the site is used).

Check a sales coach. Searches that find no one are kept as the words searched, never who searched, for 90 days. We never keep a search that looks like an email address or a long number. If that seller joins later, they see how many people looked them up. Lawful basis: legitimate interests (showing sellers that buyers want to check them).

Sponsored links. If a page for sellers shows a sponsor’s link and you click it, we count the click as a number for that day, and nothing about who clicked. Lawful basis: legitimate interests (telling sponsors how many people visited).

If you ask us to email you. To watch a seller’s certificate, or to get our “Before you buy” checklist: your email address, what you asked for (which seller, or the checklist, and whether you also want new buyer guides) and when you asked, confirmed and stopped. If you asked for the checklist on one of our landing pages, we also keep the page you asked on and what brought you to it (an ad network or a link, never who you are there), with our waiting list. Nothing happens until you confirm from the first email, so nobody can sign you up. Every email has a link to stop it. If you ask us to stop all email, we keep a code made from your address, not the address itself, so we don’t email you again. We never tell sellers who is watching them. Lawful basis: consent, which you can withdraw at any time.

If you join a waitlist. To hear when you can connect a payment platform, or a CRM for the sales record, or, if you join as a client, when you can check a sales coach before you pay: your email address, which one you chose (and the name you typed, if you chose something else) or that you joined as a client, the page you joined on and what brought you to it (an ad network or a link someone shared, never who you are there), and when you asked, confirmed and stopped. Nothing happens until you confirm from the first email, so nobody can sign you up. We email you when it’s ready, and every email has a link to stop it. If you join as a seller, the page gives you a link to share: if someone joins through it, we note that it was yours. Visits to these pages are counted as numbers for each day, as certificate views are, with nothing about who visited. Lawful basis: consent, which you can withdraw at any time; legitimate interests for counting visits (knowing which pages work).

If you ask to hear when the leaderboard’s rankings open. While the leaderboard is too young to rank its sellers, its page offers one email the day the rankings open: your email address, what brought you to the page (an ad network or the site that sent you, never who you are there), and when you asked, confirmed and stopped. Nothing happens until you confirm from the first email, so nobody can sign you up. We send that one email, with a link to stop, and delete your address 30 days later. Lawful basis: consent, which you can withdraw at any time.

If you ask for the Proof Kit. Our free guide for coaches, consultants and course creators: your first name and email address, the words under the form that you agreed to and whether you ticked its box for follow-ups, when you asked, what brought you to the page (the labels in the link you followed, such as the post or ad it came from, and Meta’s click ID if the link came from Facebook or Instagram), whether you’d accepted Meta’s cookies, and whether our email tool took your details. If you leave the box unticked, we email you the kit ourselves, with a link to stop, and nothing more. If you tick it, our email tool, Mailchimp, sends you the kit and three short follow-ups, the last of which invites you to get verified. Each has a link to unsubscribe. If Mailchimp can’t take your details, we email you the kit ourselves, with a link to stop. If you ask for it through a form on Facebook or Instagram instead, Meta passes your first name and email address straight to Mailchimp, which notes the form and when you sent it, and sends you the same emails. Our own site keeps no record of the request. Lawful basis: consent, which you can withdraw at any time.

Meta’s Pixel, on the Proof Kit’s pages only. If you accept Meta’s cookies there, Meta’s Pixel tells Meta that you viewed the page and, if you ask for the kit, that you did, with Meta’s cookies (section 14), your IP address and browser details. When you ask for the kit with Meta’s cookies accepted, our server tells Meta too, with your email address turned into a code (hashed), so Meta counts it once and can match it to a Facebook or Instagram account. We use this to see which of our posts and ads bring people to the kit, and so that Meta shows our ads to people likely to want it. Meta and we are joint controllers for collecting and sending this data; what Meta does with it after that is up to Meta, as its Privacy Policy explains. If you reject Meta’s cookies, or don’t answer, none of this happens. Lawful basis: consent, which you can withdraw at any time on our Cookies page.

Certificate and badge views. To count each visitor once a day, our server remembers a keyed code made from your IP address and browser, in its memory only, until the end of the day. It never reaches our database: sellers see only totals. Lawful basis: legitimate interests (telling sellers how their certificate is used).

Security. Your IP address, used in counters that stop people making too many attempts, stored only as keyed codes for a short time (from minutes to a day). Cloudflare checks every request to our website for attacks and bots, and runs the security check on our forms, using your IP address and browser details; it may set two cookies to do this (section 14). Lawful basis: legitimate interests (keeping the service secure).

Error reports. When something breaks, a report goes to our error-tracking provider, without your IP address, cookies or anything you typed. Lawful basis: legitimate interests (fixing problems).

Reports about a certificate. The reason and details you give, and either your account (if you’re signed in) or a keyed code of your IP address. Lawful basis: legal obligation for reports about illegal content or content that’s harmful to children (online safety law requires us to deal with them); legitimate interests for the rest (keeping certificates honest).

If you email us. Your email address and what you write, to answer you. Lawful basis: legitimate interests (answering questions and keeping a record of what we said).

Intimate image reports. If you email us an intimate image report (Terms, section 10A), we use it only to deal with it: to take the image and any copies down, and to reply to you. It may reveal details of someone’s sex life, which the law treats as special category data, and it accuses someone of an offence. We handle it under the same condition and policy document as other reports (section 3). Lawful basis: legal obligation (online safety law requires us to deal with these reports).

8. Who we share personal data with

Service providers that process data for us, under contracts that require them to protect it:

  • Supabase: our database, sign-in and photo storage, in London.
  • Fly.io: hosting for our servers, in London.
  • Resend: sending our emails, in the United States.
  • Mailchimp (run by Intuit): our email tool for the Proof Kit’s emails, in the United States.
  • PostHog: analytics, in the EU.
  • Sentry: error reports, in the EU.
  • Cloudflare: on its global network, carries our website between your browser and our servers, checks every request for attacks and bots, runs the security check on our forms, and runs our domain name system.
  • Microsoft: our email inbox (Microsoft 365, bought through GoDaddy), in Europe.

Stripe is the source of sellers’ payment data, which we read only with the seller’s permission, through the Earncrest app. It also takes the payments for the selling tools for us (section 3). Stripe is responsible for its own handling of payments.

PayPal is the source of the payment data of sellers who connect it, which we read only with the seller’s permission (section 3). When a seller connects it, we send PayPal only a random reference for that sign-in, never the seller’s details, so PayPal can tell us which account finished it. PayPal is responsible for its own handling of payments.

Meta (for Facebook, Instagram and Threads), TikTok and X are the sources of the social account details in section 3, which we read only with the seller’s permission. Each is responsible for its own handling of the seller’s data.

HubSpot and GoHighLevel are the sources of the deal records in section 3, which we read only with the seller’s permission, through the Earncrest app. Each is responsible for its own handling of the seller’s data.

Meta also receives what its Pixel and our server send from the Proof Kit’s pages, if you accept Meta’s cookies there (section 7). Meta and we are joint controllers for collecting and sending it, under Meta’s terms; Meta is responsible for what it does with it after that.

We also share personal data: with the public, as section 4 describes; with professional advisers, such as lawyers and accountants; with authorities, when the law requires it; and with a buyer of our business, if it’s ever sold. We never sell personal data.

9. Transfers outside the UK

If you use Earncrest from outside the UK, your data comes to us in the UK, where our database and servers are, and we handle it as this notice describes.

Some of our service providers keep data outside the UK, and some that keep it in the UK or the EU can reach it from other countries, for example to support or secure their service. The law treats both as transfers, and each has a safeguard:

  • Supabase keeps our database, sign-in and photos in London. Its staff around the world may reach them to support and monitor the service. Its contract with us includes standard contractual clauses with the ICO’s UK Addendum.
  • Fly.io runs our servers in London. Fly.io, a US company, may reach them from the United States to run and support them. It’s certified under the UK–US data bridge (the UK Extension to the EU–US Data Privacy Framework).
  • Resend sends our emails from the United States. It’s certified under the UK–US data bridge, and its contract with us also includes the ICO’s International Data Transfer Addendum.
  • Mailchimp keeps the Proof Kit’s email list in the United States. Intuit, which runs it, is certified under the UK–US data bridge, and its contract with us also includes standard contractual clauses with the ICO’s UK Addendum.
  • Meta receives what its Pixel and our server send from the Proof Kit’s pages in the United States and other countries. It’s certified under the UK–US data bridge, and its terms with us include the UK’s transfer safeguards.
  • PostHog keeps our analytics in the EU, which the UK treats as adequate. PostHog, a US company, may also process them in the United States, under the same two safeguards as Resend.
  • Sentry keeps our error reports in the EU. Sentry, a US company, may process them in the United States and other countries. It’s certified under the UK–US data bridge.
  • Cloudflare carries our website on its global network, which includes countries outside the UK. It’s certified under the UK–US data bridge, and its contract with us also includes standard contractual clauses with the ICO’s UK Addendum.
  • Microsoft keeps our email inbox in Europe, and may reach it from the United States and other countries to run and secure the service. It’s certified under the UK–US data bridge.
  • Stripe, which takes the payments for the selling tools, may process billing details in the United States. It’s certified under the UK–US data bridge.

Email us for a copy of these safeguards.

If the EU GDPR applies to how we handle your data, Fly.io, Resend, Mailchimp’s Intuit, Meta, PostHog, Sentry, Cloudflare, Microsoft and Stripe are also certified under the EU–US Data Privacy Framework, and the contracts Supabase, Resend, Mailchimp, PostHog and Cloudflare have with us include the EU’s standard contractual clauses.

10. How long we keep it

  • Your account, profile and daily figures: while your account exists.
  • Payment records and customer codes: 25 months on a rolling basis, deleted when you disconnect the account they came from, or take back our permission in PayPal. A disconnected PayPal account’s ID and name: 30 days. Records of a PayPal sign-in while you connect it: 1 day after it ends; while we wait for you to confirm the account from the link we emailed, what PayPal told us of it (its ID, name and email address) until you do, or 7 days at most.
  • Your photo: until you remove or replace it, or delete your account.
  • Your free place or subscription: while your account exists; deleting the account ends a subscription first. Invoices and payment records: six years after the end of the financial year they belong to, as tax law requires, in our Stripe account.
  • Ownership review documents: deleted when we decide; the decision and its reason, 24 months.
  • Social account checks with a bio code: unfinished ones, 7 days; decided ones, 90 days.
  • Social accounts you connected by signing in, with their counts: until you remove them or delete your account, or a network asks us to delete them for you. Their tokens: until then, or until you remove Earncrest in the network’s settings.
  • Records of deletion requests made through Facebook, Instagram or Threads: 90 days.
  • Domains never verified: 30 days.
  • Views: 13 months. Websites showing your badge: 13 months after we last saw it there.
  • Fraud flags: until decided, then 24 months.
  • Activity log: 24 months.
  • CRMs you asked for: while your account exists.
  • CRM deal records and daily sales figures: 25 months on a rolling basis, deleted when you disconnect the CRM. A disconnected CRM’s account ID and name: 30 days.
  • Searches that found no one: 90 days. Words searched that showed a seller: 90 days.
  • Proof links: 12 months; revoked ones, 30 days. Weekly summaries sent: 13 months.
  • If you asked us to email you: unconfirmed requests, 7 days; watches end after 12 months; stopped requests, 30 days; the code of an address that asked for no more email, until you ask us to forget it.
  • Waitlists, a request to hear when the leaderboard’s rankings open, and checklist requests made on our landing pages: unconfirmed, 7 days; stopped, 30 days; the rest until 30 days after we email you that it’s ready, or 24 months at most. Daily visit numbers for the landing pages: 26 months.
  • If you asked for the Proof Kit: our record, 24 months after you last asked for it, or 30 days after you stop its emails through our link. In Mailchimp, your address stays while you’re on the list; if you unsubscribe, Mailchimp keeps it marked as unsubscribed, so it’s never emailed again, until you ask us to delete it. Your answer about Meta’s cookies: 6 months, in your browser.
  • Analytics: 1 year, the period our analytics provider sets. Error reports: up to 90 days.
  • Attempt counters: from minutes to a day.
  • Reports about certificates: until decided, then 24 months.
  • Emails to us: 24 months after the conversation ends.
  • If an account is deleted while its certificate is suspended or under a serious fraud flag: its Stripe and PayPal account IDs, for 24 months, so the same Stripe or PayPal account can’t start afresh under a new account (legitimate interests: preventing fraud).
  • If you delete your account after your certificate was published: a one-way code made from your handle (not the handle itself), for as long as Earncrest runs, so nobody else can take your address and the links you shared (legitimate interests: preventing impersonation).
  • The Stripe and PayPal accounts that took free places: a one-way code made from each one’s ID, until the last free place is taken (legitimate interests: preventing fraud).
  • Sign-in records: 7 days, in our sign-in provider’s logs.
  • Backups: our database provider keeps daily backups for 7 days. Photos aren’t in backups.

11. Your rights

  • See your data and take a copy: download it from your dashboard (Your account, then Your data), as a file you can use elsewhere. The download leaves out the results of our fraud checks. Ask us for those, but we may hold them back where telling you would help someone get round the checks.
  • Correct it: edit your profile from your dashboard. Your figures come from Stripe or PayPal; if one looks wrong, tell us and we’ll check it.
  • Delete it: delete your account from your dashboard. Your certificate disappears at once, and the rest is deleted straight away, apart from: entries in our activity log (with your account ID, not your name or email address), kept for 24 months; the Stripe and PayPal account IDs and the one-way codes described in section 10, if they apply; and our backups, which roll over within 7 days. To delete only a social account, remove it from your dashboard, or ask Facebook, Instagram or Threads to have us delete it (section 3).
  • Limit or object: you can ask us to stop or limit anything we do on the basis of legitimate interests. We’ll stop unless we have strong reasons to continue, such as preventing fraud.
  • Automated decisions: see section 6.

Use your dashboard, or email support@virtascend.com. It’s free. We’ll answer within one month, or tell you within that month if we need up to two more because a request is complex. We may need to confirm it’s you first.

12. Complaints

If you’re unhappy with how we’ve handled your personal data, tell us first: email support@virtascend.com with “Complaint” in the subject line, or write to us at our registered office. We’ll acknowledge your complaint within 30 days, look into it without undue delay, keep you informed, and tell you the outcome, normally within three months.

You can also complain to the Information Commission (the ICO): ico.org.uk/make-a-complaint, or 0303 123 1113. If you live outside the UK, you can also complain where you live (section 13).

13. If you live outside the UK

Wherever you live, you can use the rights in section 11, in the same way and free of charge, and we handle your data as this notice describes. Where another country’s law applies to how we handle your data, we follow it.

The European Economic Area and Switzerland. If the EU GDPR or the Swiss Federal Act on Data Protection applies to how we handle your data, it gives you the rights in section 11, and we rely on the lawful bases this notice gives for each use. You can complain to the data protection authority where you live or work, or where you think the problem happened. The European Data Protection Board lists them at edpb.europa.eu; in Switzerland, it’s the Federal Data Protection and Information Commissioner.

The United States. We don’t sell personal information, share it for cross-context behavioural advertising, or use it for targeted advertising. We use sensitive personal information, such as your password, only to provide Earncrest and keep it secure. Sections 3 to 10 set out what personal information we collect, where it comes from, why we use it, who we disclose it to and how long we keep it. Whichever state you live in, you can ask to know what we hold about you, and to get a copy of it, correct it or delete it. Someone you authorise can ask for you, though we may ask them for proof and check the request with you. We won’t treat you differently for using these rights. If we turn a request down, we’ll tell you why, and you can appeal by replying to our answer. If we turn your appeal down, you can complain to your state’s attorney general. In California, you can also complain to the California Privacy Protection Agency.

Everywhere else. The law where you live may give you other rights, or a regulator to complain to. Email support@virtascend.com and we’ll help.

14. Cookies

We use only essential cookies, except on the Proof Kit’s pages: to keep you signed in, to remember the email address we’ve just sent a code to (for 10 minutes, or an hour while you create an account), to tie a Stripe, PayPal or CRM connection to the browser that started it (for 30 minutes, or 2 hours for PayPal), to tie a social account sign-in to the browser and page it started from (for 10 minutes), and, while you move two-step sign-in to a new authenticator app, to remember which new app you’re setting up (for 15 minutes). Cloudflare, which protects our website, may also set two essential cookies of its own to tell people from bots, each lasting about 30 minutes. No analytics cookies.

On the Proof Kit’s pages, we ask whether you accept Meta’s cookies (section 7): _fbp and, if a link from Facebook or Instagram brought you, _fbc, each lasting 90 days. They’re set only if you accept, and an essential cookie of ours remembers your answer for 6 months. You can change it at any time on our Cookies page. No other page uses advertising cookies.

15. Children

Earncrest is for people aged 18 or over. We don’t knowingly hold children’s personal data.

16. Keeping data safe

Sellers can add an authenticator app to their account. Without one, a seller’s account opens only with its password and a code we email, together; and if its password is reset, we remove what we read from Stripe or PayPal before letting anyone in, or, where a certificate has been published, hold the account until we’ve checked with its owner. With one, signing in needs the app, and actions such as connecting Stripe or PayPal or deleting the account need a fresh code. The Earncrest app can only read Stripe, and sellers can disconnect it at any time. Stripe access tokens are encrypted, and only our payment-reading system can use them. We hold no PayPal token at all: PayPal lets us only search a connected account’s transactions, and only while the seller’s permission lasts. Social account tokens are encrypted too, and only our social-account system can use them. The CRM app can only read too, and CRM access tokens are encrypted the same way: only our CRM-reading system can use them. Customer codes are made with a secret key, which is destroyed when the account is disconnected. Our database and servers are in London. Only a few people at Earncrest can see sellers’ accounts, and what they do is logged. Read more on our Security page.

17. Changes to this notice

When we change this notice, we’ll update the date at the top. If a change matters to sellers, we’ll email them before it takes effect.