Privacy policy
Last updated:
We use account and gameplay data to run the game, publish records, and prevent cheating and abuse. Some game activity is public. We do not sell personal information or share it for cross-context behavioural advertising. There are no ads or third-party analytics trackers; we do count online players, playtime and replay views ourselves.
Who we are
bunnyhop.lol is operated by a US-based independent developer. In this policy, “we” means the developer of bunnyhop.lol. We are responsible for the personal information used to operate the game, its API, official integrations and desktop client. Contact support@bunnyhop.lol for privacy questions.
This policy applies to guests too. Playing as a guest creates a persistent player account; “guest” does not mean anonymous. Clearing browser data or signing out does not delete that account.
What we collect and keep
| What | Why / details | Who can see it | How long |
|---|---|---|---|
| Account and profile | Player ID, display name, sign-in identity (password, email, Discord or Wavedash), chosen avatar/flag, preferences, friends, blocks, progress and stats. To run your account and chosen features. | Public profile fields and stats: everyone. Email, sign-in identity and private settings: authorised staff and service providers. | Kept while your account exists, until you ask us to delete it, subject to the exceptions below. |
| Sessions and sign-in | Session token hashes, account/network association, sign-in codes, login state and, if you set a password, a salted hash of it (never the password itself) with a count of wrong tries. To keep you signed in and secure login. | You, authorised staff and hosting/email providers; session tokens are not public. | Sessions are valid for up to 1 year; email codes for 15 minutes; Discord login state for 10 minutes. Expiry stops use, but does not guarantee immediate deletion of database rows. |
| Runs and replays | Times, ranks, map/style, recorded movement and input, mouse settings, achievements and gameplay statistics. To verify play and provide boards, ghosts, replay viewing and exports. | Public runs/replays, ranks and stats: everyone, including Discord record posts. Private integrity evidence: authorised staff and review tools. | Kept as part of your account and leaderboard history until deletion or anonymisation is handled. Generated server export videos are intended to expire after about 30 days; downloaded or reposted copies can remain. |
| Security and diagnostics | Device identifier, browser/device characteristics and rendering hashes, salted IP/network hashes, input/replay data, timing, performance and error diagnostics. To prevent cheating, ban evasion and abuse, and diagnose problems. | Authorised staff, hosting providers and AI-assisted review tools where used; not public. | Kept while needed for account security, run verification and abuse investigations, including while your account exists. A limited ban record may be retained after deletion to prevent evasion; no fixed automatic purge applies to all diagnostics. |
| Messages and reports | Room chat (including filtered/blocked attempts), DMs, inbox messages, feedback, reports, replies and any diagnostic details/screenshots you attach. To deliver messages, provide support and moderate. | Chat: room participants. DMs: participants and staff for moderation. Feedback: relevant staff and review tools. Privacy requests: only the developer. | Room chat has a 90-day cleanup target; processing backlogs can take longer. DMs keep the latest 200 messages per conversation with no fixed age limit. Feedback, inbox and moderation history remain until handled under our retention/deletion criteria. |
| Voice chat | In multiplayer rooms you can talk by holding the push to talk key (X by default). The game asks your browser for the microphone the first time you press it and uses it only while the key is held. Your voice goes through our room server to the other players in the room and is played on their devices. Guests can listen but not talk. You can mute anyone, turn voice off in Settings, or block the microphone in your browser’s site settings at any time. | Heard live by the players in the room. Moderation actions (for example a staff voice mute) are seen by authorised staff. | Voice is not recorded, stored or analysed, on our servers or in your browser. Moderation records are kept like chat moderation records. |
| Purchases and gifts | Player/payment reference, amount, currency, payment/refund/dispute status and gifts. To deliver perks, resolve payment issues and keep accounting records. | Developer, payment providers and authorised staff as needed; supporter listing/amount visibility follows your settings. No card numbers are visible to us. | Kept as needed for delivery, tax, accounting, fraud prevention and disputes, including where required after account deletion. |
| Presence and usage counts | Recent presence associated with account/network identifiers, active playtime and replay views. To show online counts and game statistics and prevent duplicate view counts. | Players see online counts and public playtime/view totals; staff can access underlying operational data. | Presence entries expire after roughly minutes (about 12 without a ping), with a 24-hour rolling presence history. Replay-view network deduplication lasts about a day; account playtime, view totals and longer-term aggregate statistics can remain. |
We collect data you provide, data produced by gameplay and requests, and information from sign-in and payment services you use. Cloudflare processes IP addresses and request headers to deliver and secure the site; the game uses salted IP/network hashes as linkable security identifiers. Hashing does not make this information anonymous.
We do not apply one automatic deletion period to all records. Account data is generally kept while your account exists or until you ask us to delete it. Support, security and moderation records are kept as needed to resolve issues, enforce rules and meet legal obligations. Logs, backups and provider records follow their operational retention processes; removal from those systems may take longer than removal from the live game.
Public and private activity
Your display name, bunny avatar (or your Discord picture if you choose to show it), country flag if set, runs, times, replays, ranks, profile mouse sensitivity, playtime and statistics can be public. DPI is shown when you choose to share it. Multiplayer players receive your live game state. Public records and milestones may be posted by our Discord bot, and players can download or share replays and exports.
Email addresses, sessions, payment records, feedback and diagnostics are not public. DMs are private between participants, but staff can read them for moderation; they are not end-to-end encrypted. Private lobbies do not prevent staff access or moderation logging. Avoid putting sensitive personal information in chats, reports or screenshots.
Public material can be copied, cached or reposted by others. We can handle removal or anonymisation of our records, but cannot promise to remove every independent copy.
Cookies and local storage
We use cookies for guest/account sessions and sign-in, and a device identifier for security. The normal session cookie can last up to a year; the device cookie can last up to two years unless you clear it. Clearing site data resets the device identifier; we do not restore it from an old localStorage or IndexedDB copy. This does not erase server records or prevent security systems from recognising related activity.
The game also uses localStorage, sessionStorage, IndexedDB and caches for settings, local progress and replays, pending uploads, selected maps, custom CSS, texture/sky packs and other chosen features. These local records generally remain until replaced by the feature or cleared by you; temporary state can end with the tab. Account settings sync is optional on the website and enabled for Wavedash play.
You can clear site data in your browser settings. This may lose local progress, pending uploads and access to an unlinked guest account. Signing out, unlinking a login method or starting a new guest is separate from requesting account deletion. Wavedash uses a browser-stored session jar for its embedded game; its storage is separate from the main website.
Fair play and automated decisions
For anticheat, ban-evasion detection and abuse prevention, we use a device identifier and browser/device characteristics such as GPU information, screen, timezone, language, and canvas/WebGL rendering hashes. We also use salted IP/network hashes, input and replay data, and timing/performance diagnostics. These signals are collected when you sign in or start a session and when you submit a run, not with every request. Requests the server refuses or can't complete also add to a counter of the route, status, country, whether a session cookie was sent and a short server error, with no player ID or IP address, kept for 3 months.
Runs are checked automatically. Automated systems can reject runs, restrict access, or limit the visibility of a player’s records or messages before a human reviews them. Staff use evidence from runs, diagnostics and linked security identifiers to investigate; AI-assisted tools can help review reports and anticheat flags. We do not promise that every action is human-reviewed.
If you think a decision is wrong, ask for human review at support@bunnyhop.lol. Include your player ID and the affected run or action if available.
Why we use personal information
Where a legal basis is required, we use account, gameplay, communication and purchase data to provide the service you request and fulfil our agreement with you. Our legitimate interests include keeping play fair, preventing fraud and abuse, securing accounts, moderating the community, fixing problems and understanding first-party game usage. We use payment records to meet tax/accounting and other legal obligations. Where processing requires consent, that consent is the applicable basis and may be withdrawn without affecting earlier lawful processing.
Security processing includes the device, fingerprint, network, input and diagnostic data described above. You can contact us to object to processing based on legitimate interests; we will consider your circumstances and any compelling grounds for continuing it.
Services and international processing
Data is processed in the United States. Our providers also process data elsewhere; this is not a service that keeps all data in your country.
- Cloudflare: hosting, databases, live rooms, storage, email sending, request security and logs, processing data in the US and elsewhere.
- Stripe: payment checkout and payment/refund/dispute processing. We send your player reference and purchase details. We never see your card numbers.
- Discord: optional sign-in, identity/avatar information, community membership/reward integration, and bot posts of public records. Viewing Discord avatars loads images from Discord’s CDN, even if the viewer has not signed in with Discord. General reports/feedback and security alerts can be shared in staff channels; privacy requests are excluded from those moderator routes. Replay-link bots process messages in configured community channels to offer or post replay videos.
- Wavedash: if you play through its portal, it hosts the embedded client and provides your portal identity; the game exchanges gameplay statistics, achievements and leaderboard scores with it. Wavedash’s own platform collection is covered by its policy.
- OpenAI: AI-assisted tools used by the moderation team to review reports, feedback and anticheat flags. Relevant ticket text, screenshots, case notes and run evidence may be processed by these tools. Privacy requests go only to the developer and are excluded from moderation AI tools.
- Cloudflare Turnstile: a browser check that appears on password sign-in only when an account or the sign-in service is seeing too many wrong tries. Cloudflare processes browser and connection signals to run it.
- Have I Been Pwned: when you set a password, the first five characters of its SHA-1 hash go to the Pwned Passwords service to check it against known breaches. The password itself is not sent.
- GitHub: desktop downloads and update checks receive ordinary network/request information.
Operator-run tools also process replays to make videos and retain moderation case/tool history. We may disclose information when needed to comply with law, protect people or investigate abuse. We do not sell personal information or share it for cross-context behavioural advertising.
If you choose external texture or sky packs, your browser contacts the pack host directly. Custom CSS imports and their assets are fetched through our proxy; the host receives the requested URL, which can still contain an identifier. External links and services have their own privacy practices.
Desktop client
The desktop client loads the live game, so the website processing described here still applies. When enabled, Discord Rich Presence shares current activity and map information with Discord, which can display it to others. You can turn it off in the client settings. The client’s Discord privacy setting does not disable the game’s security processing or independent update checks.
The client checks GitHub for updates; update checks can be disabled in client settings. Local vault entries, run summaries, screenshots, exported support reports, benchmarks and cached game files are stored on your computer. Account deletion does not erase those local files; use the client or your computer’s file controls to remove them.
Your choices and privacy requests
Request your data or account deletion
The same form is in Settings → Account → Privacy & data. You can also email support@bunnyhop.lol, including if you cannot sign in. Privacy requests go only to the developer, not moderators. We may need to verify account ownership before disclosing or deleting account information. We aim to respond within 30 days.
Depending on where you live, you may have rights to access or receive a copy of your information, correct it, request deletion, restrict or object to processing, and withdraw consent. Tell us what you need and we will handle it. You may also complain to your local data-protection authority where applicable.
Deletion is handled by the developer and is not instant. Runs and replays may be removed or anonymised from leaderboards. We may keep payment records needed for tax, accounting, disputes or fraud prevention, and a limited record of bans to prevent evasion. We also consider other people’s rights in shared conversations and records, and legal obligations. We will explain relevant limits when handling your request.
Children’s privacy
The game is not directed at children under 13. You must be at least 13, or older if your country requires a higher age to use online services without parental consent. If you are under 18, you need a parent or guardian’s permission to make purchases.
A parent or guardian can contact support@bunnyhop.lol to have a child’s account removed.
Changes and contact
We will update the date on this page when this policy changes and notify players in-game or through Discord about material changes. Contact support@bunnyhop.lol for questions, requests or concerns. See also our Terms Credits.