Privacy policy

This Privacy policy explains how Perps Fund (“we,” “us”) collects, uses, shares, and protects personal data when you use our platform (the “Service”), and the rights you have over your data. It forms part of, and should be read with, our Terms of service. Perps Fund is the controller of the personal data described here.

It applies to visitors and to account holders across evaluations and funded accounts. If you do not agree with this policy, do not use the Service.

We collect: account data (email, username, credentials, and authentication settings, including your two-factor status); evaluation and trading data (your simulated orders, positions, fills, and performance - records of activity on simulated accounts); payout data (withdrawal wallet addresses, networks, and payout history); identity-verification data, handled either by our identity-verification provider or by our support team (see the next section); payment data through our payment provider (we receive confirmation and limited metadata, not full card or wallet credentials); and technical and anti-abuse data (IP address, device and browser characteristics, approximate location, and log, usage, and cookie data).

We also derive fraud- and abuse-prevention signals - including links between accounts that share a device, IP address, payment instrument, or withdrawal address - which we use solely to protect the integrity of the Service. How and why we use these signals is described under “How we use information.”

When you sign up with a password we email you a link to confirm your address, and you cannot sign in with that password until you have used it. When you sign up we record a one-way keyed fingerprint of your IP address and the country it maps to, with your acceptance of these terms, to detect abuse of referrals. We do not keep the address itself. Security logs hold IP addresses for up to 30 days.

We keep a record of the actions our staff take on customer accounts, including which account a member of staff viewed and when.

Identity verification is required once your lifetime unverified payouts would exceed $1,000, and we may require it earlier where reasonably necessary to prevent fraud or abuse or to meet a legal obligation. Verification is carried out either by our identity-verification provider or, where that provider is not yet available to you, directly by our support team. To verify you we may collect government-identification documents, a selfie or liveness check, and related identity data, and may carry out sanctions and watchlist screening.

Where an external provider carries out the check, it processes this data as our processor under its own security and compliance controls, and we receive the verification result and the limited data needed to make and evidence a payout decision. Where you send documents to our support team directly, we receive and process those documents ourselves. We retain verification records for as long as required to meet our legal and anti-fraud obligations, and we minimize what we store.

When you create an account you agree to these policies. Separately, when you purchase an evaluation, you confirm at checkout that you are not a resident of a restricted jurisdiction or region; we record that confirmation, the date, and the version of the restricted-region list in force at the time. See Eligibility and restricted regions in the Terms for the list itself.

We use personal data to: operate the Service and your evaluations and funded accounts; process and pay profit share and referral rewards; verify identity and screen for sanctions; prevent, detect, and investigate fraud, abuse, and exploitation of the Service - including by linking and reviewing related accounts and trading and payout activity; provide support; comply with legal obligations; and maintain the security and integrity of the platform.

Our lawful bases include performance of our contract with you (operating the Service and paying you); our legitimate interests - notably preventing fraud and abuse and securing the platform, balanced against your rights; compliance with legal obligations (identity verification, sanctions screening, and record-keeping); and your consent where required, for example for certain cookies. The anti-abuse signals described above are processed on the basis of our legitimate interest in preventing fraud and protecting the Service.

To help you spot account takeover, we record the devices you sign in from: a device identifier stored in your browser, your browser and operating system, and an approximate city and country derived from your IP address. We use these records to recognise your devices and to alert you by email when an unrecognised device signs in, and the same device identifier feeds the account-linkage signals described above. We do not retain your full IP address for this purpose, and we remove a device record after twelve months without a sign-in. Separately, we retain records of accounts that have shared a device for longer where necessary to meet our anti-fraud obligations, so those linkage records may be kept beyond the twelve-month removal. Your device records are included when you request a copy of your data.

We share personal data with processors who act on our instructions: our identity-verification provider, NowPayments (payment processing), Resend (sending email), Sentry (error monitoring), PostHog (product analytics), Intercom (support chat, which receives your account identifier and email address), Google (if you sign in with Google), Discord (if you link your account), Cloudflare (a check that a sign-up is made by a person), Backblaze (encrypted backups), our hosting, caching and infrastructure providers (Vercel, Neon, Upstash, Railway), and TRM Labs, to screen a payout wallet address against sanctions lists. We send the wallet address only. Market price and funding data is sourced from Hyperliquid, a third-party venue; we do not share your personal data with that venue to obtain it. Your browser connects directly to Hyperliquid to load live prices and charts, so that venue receives your IP address and browser details as any website you visit does. We do not send it your account details.

We also send operational alerts to our own staff through Telegram and Slack, so that our team is notified when something needs attention, for example a signup, a purchase, a payout request, or an account breach. These alerts carry your pseudonymous handle, your account tier and the amounts involved. Email addresses are masked (for example ab***@example.com), wallet addresses are truncated, and account identifiers are shortened, so the full values are not sent to those services.

When a payout is paid we post its amount to our public Discord server, with your handle if your leaderboard visibility is on. We do not post the wallet or the transaction. If you turn on Public profile, your handle, avatar, points tier, current streak and monthly points are also shown on the Points board to signed-in users, and if you finish a month in its top three, on that month's kept result. Monthly points on the board never include points earned from purchases or payouts. Turning Public profile off removes you from the board and from past results. If you share a certificate, its page is public to anyone who has the link until you turn sharing off: it shows your handle, the achievement, the account size or the number of the payout, and the month and year, never an amount or your real name, and we ask search engines not to list it.

We may disclose data where required by law, to comply with sanctions obligations, or to protect our rights, our users, or the Service. We do not sell your personal data.

We use cookies and similar technologies that are essential to operate the Service - for example, authentication and security - and, where applicable, optional analytics cookies to understand and improve how the Service is used. Essential cookies are required for the Service to function; you can manage optional cookies through your browser or any in-product controls we provide.

Some anti-abuse signals, such as device characteristics, are processed on the basis of our legitimate interest in security rather than through optional cookies.

One of these signals is a first-party cookie named pf_device (it appears as __Secure-pf_device in your browser on our production domain). It holds a random identifier - nothing about you or your browsing - is not readable by page scripts (httpOnly), and lasts up to 400 days; we store only a one-way hash of its value. We use it to recognise the device you are using, for the sign-in alerts described under “How we use information” and to prevent fraud and abuse, on the basis of our legitimate interest in securing the Service. It is an essential cookie, not an optional one.

We also set a first-party cookie named pf_signed_in while you are signed in. It is a presence-only flag: its value is always 1, it holds no identifier and no personal data, and it does not sign you in or grant access to anything. Page scripts can read it, which is its purpose: our public pages use it to show the signed-in navigation straight away instead of a Sign in button. It lasts up to 400 days and is removed when you sign out or your session ends. It is an essential cookie, not an optional one.

A second presence flag, pf_app_signed_in, does the same job on our other perpsfund.com addresses, such as the docs: it is set while you are signed in on app.perpsfund.com, its value is always 1, it holds no identifier, and it is removed when you sign out.

When you follow a member's referral link we set a first-party cookie named pf_ref. It holds only the referrer's public handle or referral code, as the link carried it - nothing about you or your browsing - is not readable by page scripts (httpOnly), and lasts 30 days from the last referral link you followed; a newer link replaces an older one. If you create an account while it is set, we record that member as your referrer, which is how they are credited and how your first-purchase discount is applied; we keep that record with your account. It is set when you follow the link, not through the optional-cookie controls. We also count how many times each referral link is opened, as a number per link per day, and show that number to the member whose link it is. The count identifies no visitor: it holds no IP address, device or cookie value, and the same person opening a link twice is counted twice.

On the Referrals page we set a first-party cookie named pf_ref_shape once you have a paid referral. Its value is always 1, it holds no identifier and no personal data, and it is used only to lay out the page's loading state. It lasts up to 400 days and is removed when you sign out.

When you answer our analytics notice we store your answer in a first-party cookie named pf_mktg_consent. Its value is 1 if you accepted and 0 if you declined, it holds nothing else, and it lasts up to 12 months. Until it says 1 we load no analytics script and send no analytics event.

When you arrive from a link or from another site, we set a first-party cookie named pf_src. It records where that visit came from: any campaign labels in the link (such as utm_source), the name of the site that linked to us (never the page you were on there), the page of ours you arrived at (never anything after a question mark), and the time. It records this for your first arrival and your most recent one, holds no identifier, is not readable by page scripts, and lasts up to 90 days. If you create an account we keep this with your account, and if you buy a challenge we keep the most recent arrival with the order, so that we can tell which of our links and advertisements bring people to us.

We count how many visits arrive from each source, by day, landing page and country. These counts contain no cookie, no identifier and no address: they cannot be linked to you.

If you arrive from an advertisement and have accepted our analytics notice, we keep the click identifier the advertising platform added to the link in a first-party cookie named pf_cid, for up to 90 days, and with any order you place, for 90 days after it. We use it to tell that platform that a visit from its advertisement led to a sign-up or a purchase. If you withdraw your consent, the cookie is removed.

If you accept our analytics notice, our analytics provider (PostHog, acting as our processor, in the EU) stores an anonymous identifier in your browser's local storage so that page views in one visit can be counted together. We do not send it your name, email address or account, we do not record your screen, and nothing is stored if you decline.

While you are signed in we record a small number of steps in your account's history: the first time you see your dashboard, viewing the plans page, opening checkout and choosing a payment method, saving or sharing a share card, and the days on which you open the app and whether you traded. We use these to see where the product loses people and how often traders come back. They contain no address and no device details, they are included in your data export, and they are deleted when your account is deleted.

Our email provider (Resend, acting as our processor) tells us whether a message was delivered, bounced or marked as spam. We do not track whether you open an email. For account, security and payment emails we do not track links. For emails about your progress and our news, links pass through our email provider so that we can count clicks; we record that a link was clicked and when, not which link.

If you accept our analytics notice, we tell the advertising platforms we use (Meta, TikTok, Google and X) when you sign up, start a free trial, start a checkout or buy a plan, so that we can measure which adverts work. We send the event, the plan and the price of a purchase, a scrambled (SHA-256) form of your email address to Meta, TikTok and X, and the identifier the platform itself placed in your browser when you clicked its advert. We do not send your IP address from our servers, and we never send anything about your trading: not your results, your balance, whether you passed, or any payout. Each platform also runs its own script on our pages once you accept; that script is the platform's, it sets the platform's own cookies, and the platform receives your IP address and browser details directly, as it does on any site that uses it. Each platform handles what it receives under its own privacy policy.

You can tell us not to sell or share your personal information. Use the "Do Not Sell or Share My Personal Information" link at the foot of any public page, or turn on Global Privacy Control in your browser: we treat either as the same request. From then on we send nothing about you to an advertising platform and load none of their scripts in that browser, whatever you answered to the analytics notice. The choice is stored in a first-party cookie named pf_dns, which holds the value 1 and nothing else and lasts up to 12 months. It applies to the browser you set it in.

Our support chat is provided by Intercom, which acts as our processor. On desktop it loads on pages where chat is available and sets first-party cookies on our domain (including intercom-id-* and intercom-session-*) to keep your conversation open across pages - this happens shortly after the page loads, without waiting for you to open the messenger. It is not loaded on mobile, or in the admin console.

The table below lists every cookie we set, or that a provider sets on our pages, with what it is for, how long it lasts, and whether it is essential or set only with your consent. A name ending in * is followed by an identifier the provider adds. The providers' own cookies and their lifetimes are set by each provider and can change.

We protect personal data with technical and organizational measures, including encryption in transit, access controls, and two-factor authentication on accounts. Withdrawal addresses are whitelisted, and a newly added address is subject to a 48-hour security hold before it can receive a payout.

No method of transmission or storage is completely secure, and we cannot guarantee absolute security. You are responsible for safeguarding your credentials and for enabling two-factor authentication.

We keep personal data for as long as your account is active and as needed to provide the Service. After an account is closed, we retain certain data for longer where necessary to meet legal, tax, accounting, and anti-fraud obligations, to resolve disputes, and to enforce our agreements - for example, identity-verification and payout records are kept for the period required by applicable law.

When data is no longer needed for these purposes, we delete or anonymize it.

When you delete your account we remove your profile, sign-in details, saved wallets, devices and notifications, and we replace your email address and handle wherever we hold them. We keep, under an internal identifier that no longer names you: your trading and purchase history, your payout records including the wallet they were paid to, the result of your identity check, and records we use to detect fraud.

For 90 days after an account is deleted we keep a one-way keyed code of its username and referral code, so nobody else can register them. It cannot be turned back into the name and is not linked to you. When your account is anonymized we also ask our support-chat provider to delete your contact record. Copies of emails we sent you remain in our email provider's logs until that provider's retention period ends; we cannot delete them sooner. If you took part in a Tournament, your result stays on its ladder after you delete your account, shown as 'Unnamed trader' with no handle or picture.

The table below lists how long we keep each kind of record that has a set period, and the records that have none.

Depending on where you live, you may have rights to access, correct, delete, restrict, or object to the processing of your personal data, to data portability, and to withdraw consent. To exercise a right, contact us through the channels in the site footer; we will respond within the time required by applicable law and may need to verify your identity first.

You can download a copy of the data we hold about you from Settings. The copy does not include sign-in secrets, records we keep to detect fraud and protect the platform (such as links between devices and accounts, internal risk scores and payout review notes), staff records, or other people's data. You can ask us about those at legal@perpsfund.com.

Some data - such as records we must keep for legal or anti-fraud reasons - may be retained even after a deletion request. You may also have the right to complain to your local data-protection authority.

We and our processors may process personal data in countries other than where you live. Where we transfer data across borders, we rely on the safeguards required by applicable law, such as standard contractual clauses or an adequacy decision.

We may update this policy from time to time. If we make a material change, we will post the updated policy with a new effective date and, where appropriate, notify you in-app or by email.

For privacy questions or to exercise your rights, write to legal@perpsfund.com, or contact us through the channels listed in the site footer.