Privacy Policy

1. Who we are

This Privacy Policy explains how the operator of Cerise ("we", "us") handles personal data when you use cerise.lol, accounts, payments, the license APIs, and the Cerise client. It works together with our Terms of Service. Cerise is run by one individual, not a company. That operator is the data controller for the data described here, and the person you reach at the contact below.

2. Data we collect

• Account. Email, hashed password, name fields, optional username and avatar, role, account status (for example active or suspended), member number, timestamps.
• Sessions and auth. Session tokens, approximate IP, user agent, expiry times. Credential and provider rows needed for sign-in.
• Licenses and seats. License keys and plan metadata, status (including revoked or suspended), expiry and cancel times, seat limits, HWID hashes, optional device fingerprint components, seat labels, bind times.
• Activation and security logs. Every successful Loader start and first seat bind, event type, outcome, reason, IP, user agent, HWID hash, and bounded security details. Those details may include a redacted launch-location category, Windows version and build, architecture, elevation, locale and UTC offset, scan-coverage status, allow-listed tool codes, VM/VPN confidence with canonical evidence codes, and a server-derived count of repeated starts. We do not collect the full executable path, Windows username, machine name, environment variables, arbitrary process names, or a full process list for this log.
• Gameplay statistics. Cerise session start, end, and last-seen times, active duration, launch counts, and all supported entries shown in the in-game Currency Bag, selected other wallet and inventory valuable balances, and cumulative observed increases and decreases (earned and spent) during a session. These figures are reported by the client, may be incomplete, and are kept as a personal activity history. We do not collect chat, character names, raw inventory contents, or every individual in-game action for this feature.
• Bans. Scope and value (for example HWID), reason, creator metadata, timestamps.
• Cloud configs. Named presets and settings blobs you save from the client.
• Discord. If you sign in with Discord, apply to the community server, or are reported to us as a server booster, we store your Discord user id and the handle and display name we saw at that moment. A community application also records your active time and launch count as they stood when you applied, the note you wrote, and the staff decision on it.
• Assistant questions. When you ask the Discord bot about your own account, your question, the last few lines you wrote in that channel, and a summary of your account are sent to our model provider so it can write the reply. We do not store the question, those lines, or the reply. Section 5 says who that provider is and exactly what it receives.
• Referrals and rewards. Your own referral code, the account that referred you and when, and one ledger row for every reward paid: the plan that was bought, the payment processor and its charge id, the days credited, the licence they landed on, and whether a refund later took them back. Boost rewards record the Discord id, the month they cover, and the days credited.
• Beta programme. A normalised form of the email address that claimed a slot. This one is deliberately kept after an account is deleted, as a marker that the slot was claimed, so the same mailbox cannot take a second slot and a second free trial.
• Billing references. Whop user id, membership id, plan id, payment id, checkout id, historical crypto invoice ids, and plan/source fields. We do not store card numbers or wallet keys on Cerise servers. Whop processes current checkout as Merchant of Record. NOWPayments may retain records for legacy or already-issued crypto invoices under its own privacy terms.
• Technical data. Request metadata used for rate limits, abuse detection, debugging, and hosting logs.
• Website analytics. Opening a page on cerise.lol reports the page address and title, the page you arrived from, your browser user agent, screen size, language, and time zone to Whop, so we can see which pages lead to a purchase. That script also builds a device fingerprint to recognise a returning browser. It runs on every page of the site, signed-in pages included, and it is the one item on this list you can switch off from your side by blocking the script.

3. Why we use data

• Provide accounts, sessions, and the website.
• Sell and deliver access, bind seats, verify signed license grants, and run the client protocol.
• Enforce the Terms: suspend accounts, revoke licenses, ban HWIDs, rate-limit abuse, investigate fraud and chargebacks.
• Process payments and reconcile processor webhooks.
• Provide support and fix product issues you report.
• Show you personal session history and summaries of time played, launches, and observed changes in supported resource balances.
• Secure the Service and improve reliability.
• Meet legal obligations where they apply.

Where GDPR or similar laws apply, we rely on performance of a contract (providing the Service you request), legitimate interests (security, fraud prevention, enforcement, product improvement), and legal obligation when required. We do not sell your personal data.

4. Enforcement and automated checks

Seat limits, replay protection, ban lists, account status, and rate limits may automatically deny activation or other API calls. Staff may also manually suspend accounts, revoke licenses, or ban hardware. Those actions use the data above and may permanently affect your ability to use Cerise.

Tool, VM, VPN, launch-location, and repeated-start telemetry is shown only to staff for review. It is client-reported, can be incomplete or spoofed, and does not by itself automatically ban, suspend, revoke, or deny access. Challenge-authenticated debugger and integrity reports use a separate path that authenticates the current Loader session. It does not independently prove every client observation.

5. Who we share with

• Whop for checkout, renewals, invoices, tax handling, and payment disputes, and for the website analytics described in section 2.
• Discord for signing in with Discord, for running the community server and its bot, and for seeing who is boosting the server.
• Groq for the Discord assistant. Asking it a question sends your Discord display name, your Cerise username, your plan and whether access is currently blocked, up to 90 days of your activity history, the last few lines you wrote in that channel, and your question. It does not receive your email, your licence key, your IP, your HWID, or anything belonging to another member.
• Resend for account email, meaning address confirmation, email change approval, and password resets.
• NOWPayments only for legacy or already-issued crypto invoice records and confirmation.
• Hosting, database, and infrastructure providers that run cerise.lol and store data under our instruction.
• Professional advisors or authorities when required by law or to protect our rights and users.

We do not sell personal data. We do not run advertising trackers and we do not build profiles for advertisers. We do run one third-party analytics script across the site, the one described in section 2, and it is there to measure which pages lead to a purchase.

6. International transfers

Servers and vendors may process data in the EU or other countries. Where required, we use appropriate safeguards offered by those providers for cross-border processing.

7. Retention

We keep account and product data while your account exists and as long as needed to provide the Service, resolve disputes, prevent fraud, and meet legal duties. Detailed Loader endpoint snapshots, including IP, user agent, and client-reported security context, are scheduled for removal after 30 days by a retention worker that sweeps once a day, and more often than that on a busy instance. A compact authentication or license-audit row may remain for up to 90 days. A compact, current-challenge-verified debugger or integrity signal may remain for up to 180 days. Ban records may remain longer so banned hardware cannot simply re-register around a block.

Compact gameplay session summaries and resource totals are kept while your account exists so the Stats page can show long-term history. They are removed when the account is deleted, except where a limited record must be retained for a legal or security reason.

Two records deliberately outlive the account they came from. The normalised email that claimed a beta slot is kept so the same mailbox cannot claim a second one, and a referral reward row is kept after an invited account is deleted, because the days really were paid out. That reward row stops pointing at the deleted account when it goes.

Current billing records may remain with Whop, and legacy crypto records may remain with NOWPayments, under their own retention rules. Questions put to the Discord assistant are passed to Groq to answer and are not stored by us, but Groq keeps its own records under its own terms.

8. Your choices and rights

You can update certain profile fields in Settings and end sessions by signing out. You may contact us to request access, correction, or deletion of account data we control, subject to law.

We may refuse or limit deletion or anonymization where we must keep data for security, fraud prevention, license enforcement, legal claims, or accounting. Deleting an account does not automatically create a refund right under the Terms.

If you are in the EEA/UK or another region with similar rights, you may also have rights to object, restrict processing, or complain to a supervisory authority. Contact us first so we can try to resolve the issue.

9. Cookies and similar tech

We use cookies and similar storage for authentication, security, and basic site function. Disabling cookies may break sign-in.

Opening a member's referral link sets one cookie holding that member's referral code, for 30 days. It is what tells us who to credit if you go on to buy, and it is read only when you sign up, sign in, or open your referrals page. It is cleared as soon as it has been used, it holds nothing about you, and nothing else reads it.

The Whop analytics script in section 2 also writes to cookies, local storage, and session storage, to recognise a returning browser and tie a visit to a purchase. None of that is needed to sign in or to run the client, so blocking that script leaves the rest of the site working normally.

10. Security

We use HTTPS, hashed passwords, signed license envelopes, access controls on admin tools, and operational practices aimed at protecting data. No system is perfectly secure. Protect your password and devices.

11. Children

Cerise is not directed at children under 16. If you believe a child created an account, contact us and we will remove it where appropriate.

12. Changes

We may update this policy. The "Last updated" date will change when we do. Continued use after a change means you accept the updated policy.

13. Contact

Privacy questions: Discord. Also see the Terms of Service.