SnakeRank
← SnakeRank

Privacy Policy

Last updated: 2026-11-16

Guest play is free. Ranked-run packs are available. Play without an account. Sign in to count a score for an app. Signed-in accounts can purchase USD $9.90 packs of six ranked scores. Each accepted score uses one welcome or purchased score. New verified accounts receive 2 welcome scores. Purchase terms and refunds below apply to paid packs.

1. Who is responsible

The operator of the SnakeRank service is responsible for the processing described here. Contact: support@snakerank.app. This service is intended for adults aged 18 or older.

2. Current game data

3. Accounts and payments

Email sign-in uses your email address, one-time codes, terms-acceptance version and account/session records. Sign-in codes expire after 10 minutes. The legacy email flow stores hashes of verification codes and email session tokens. When Google or Apple sign-in is configured, Better Auth manages provider identities, signed session cookies and session records in our database; provider access and refresh tokens are encrypted with the server authentication secret. Cloudflare Email Service processes your email address and the code to deliver sign-in messages. These are requested account-access messages, not marketing emails.

A secure, HttpOnly first-party cookie called sr_session keeps you signed in for up to 30 days. Signing out invalidates that session. Account records include your account identifier, email, creation time and accepted terms version; authentication records include challenge timing and verification attempts. Your email address is not displayed on the public leaderboard. For purchases, attempt-ledger records link credited packs, issued runs, refunds and payment references to your account.

For purchases, Waffo Pancake processes checkout and card data under its own applicable notices. SnakeRank receives purchase references, amount/currency, payment/refund status and information needed to fulfill and support the purchase. We send your verified account email and internal account identifier to Waffo to prefill checkout and attribute the purchase to your account. We do not store full card numbers or security codes. Production checkout is available to signed-in accounts after purchase terms are accepted.

Optional social sign-in and analytics

When configured, Google sign-in, Google One Tap and Sign in with Apple provide your provider account identifier, name, verified email address and, where available, profile picture. Apple may supply a private relay email. We use the verified identity to provide account access; your email is not displayed on the leaderboard. These options remain unavailable until their provider configuration is completed.

When configured and you allow optional analytics, Google Analytics measures consented page views on instrumented site pages, App and category browsing, login, game, sharing, submission and checkout interactions, and verified purchase aggregates such as value and currency. For deduplication, a verified paid intent may include a SHA-256 pseudonymous transaction identifier; the hash is pseudonymous data and is not anonymous. Browser purchase capture is not a complete server sales report. Microsoft Clarity records interactions to help us improve the site. We mask account content and supporter-name inputs and do not deliberately send raw payment references, email addresses, sign-in codes, supporter nicknames or search text as analytics events. You can decline or change your choice through Analytics preferences; Google Analytics, Microsoft Clarity and Cloudflare Web Analytics are not loaded before consent and stay stopped after you decline. A purchase is sent to Google Analytics only if that choice is still allowed when the payment is confirmed. The payment webhook only credits the pack and does not send analytics. Withdrawing consent or never allowing it skips the purchase event, including a later retry in this browser. Crediting the pack does not depend on analytics. Your choice is remembered in first-party local storage. If that saved choice cannot be updated, the withdrawal is also kept in this tab's session storage and a host-only first-party cookie named snakerank_analytics_withdrawn (Path=/, SameSite=Lax, Secure on HTTPS, kept for up to one year). The cookie records the denial and the time it was chosen. A later Allow or Deny replaces an older one, including an Allow chosen in another tab. An open tab that already declined adopts that newer Allow on its next check or its next page. It does not broadcast the older denial, and it does not write that denial over the newer Allow. A message without a time does not replace a saved choice. If those times cannot be compared, analytics stays off on the tab that cannot tell. Allowing analytics again clears an older fallback. Microsoft and Google process analytics under their respective privacy policies.

When configured, Cloudflare Web Analytics can record cookieless page views. It loads only after you allow analytics, and it is removed if you decline or withdraw that choice. If analytics has already started, later requests to Google Analytics, Microsoft Clarity, and Cloudflare are dropped until you allow analytics again, including another open tab. Google Analytics is also set to denied and Microsoft Clarity is stopped. It does not load while you have not chosen, and a later page does not start it again after you decline. It records page views only; named game, sign-in, and purchase events are not sent to it. Cloudflare processes that measurement under its privacy policy.

The App directory stores public listing names, descriptions, categories, website links, source links, source click counts at import and copied media from public listings. Source media is stored in our Cloudflare R2 bucket and delivered through our own site CDN. Public rankings use only validated Snake runs. Imported click counts and recorded visits are not shown as rankings. To limit duplicate visits, we store a daily pseudonymous hash derived from the request IP and browser user agent; this is not proof of one person.

App submissions: when you submit an App, we store its name, website, description, category, uploaded logo, your account identifier, submission time and review decision. Submissions remain private to you and administrators until approval; approved App information and logos are public. We record your confirmation that you have permission to provide this content. Contact support to request corrections or deletion. Submission and review records are kept while needed to operate the directory and address disputes; automatic deletion is not implemented.

4. Purposes and legal grounds

We use game and account information to provide requested play, validate scores, deliver purchases and support users. Where GDPR-style legal bases apply, these activities are based on providing the requested service/contract; preventing abuse and maintaining security relies on legitimate interests balanced against your rights; legally required records rely on legal obligations. Where consent is required for an optional feature, we will request it separately. We do not use SnakeRank for targeted advertising or sell personal information.

5. Sharing and locations

Cloudflare provides hosting, database infrastructure, sign-in email delivery and support-email forwarding. The current production database is in Cloudflare's western North America region; infrastructure requests may be handled in other countries. Information may therefore be processed outside your country. We use provider contractual and security controls and apply transfer safeguards where required; no specific adequacy decision or transfer certification is promised here.

Pressing a share button opens X's composer; we do not automatically post to your account. X and other linked app websites process information under their own policies. We may disclose information where legally required or needed to investigate abuse, and to service providers for the purposes described here. Public leaderboard information is visible to visitors and may be copied by others.

6. Retention and security

We keep submitted scores and supporter records while needed to operate the leaderboard, investigate abuse and resolve requests. Guest scores stored only in the browser are under your control. Submitted scores may be removed when required to operate the service or resolve a request. Cookie expiry and run-token expiry do not automatically delete database records. We have not implemented an automatic retention-deletion schedule. Support messages are retained while needed to resolve the matter and related disputes. We retain account records to provide your account and resolve related requests or security issues. Sign-in code and session expiry prevent further use but do not automatically delete the underlying database records; explicit sign-out removes the corresponding session record. Purchase records are retained to honor unused credits, reconcile fulfillment and refunds, investigate disputes and satisfy applicable legal record obligations. Purchase records have no automatic expiry or deletion schedule. Contact support for access or deletion requests; necessary financial or dispute records may need to be retained.

We use HTTPS, hashed run/session credentials where applicable and restricted backend access. No internet service is perfectly secure. We will respond to security incidents and give notifications required by applicable law.

7. Your choices and rights

You can play for an App without submitting a supporter name, avoid public submissions, clear browser storage or contact us to request access, correction or deletion. Depending on your location, you may also request portability or restriction, object to certain processing, withdraw consent without affecting earlier lawful processing, or complain to a privacy authority. Email support@snakerank.app; we may ask for proportionate evidence that the records belong to you and will respond within the applicable legal deadline. Anonymous browser records can be difficult to identify after cookies are cleared. Necessary legal/security records may be retained where the law permits or requires.

We do not knowingly offer the service to children under 18. Contact us if a child has supplied data so we can review and remove it as appropriate. Do not send identity documents unless specifically needed and a suitable secure process is provided.

8. Updates

We will update this date when practices change and provide notice of material changes through the site or, where relevant, your account email. New optional uses requiring consent will be offered separately. See our Terms of Service and Refund Policy.