This policy describes how 38-0 handles information about visitors and app users. 38-0 is a free football game that runs in your browser or mobile app, made as an independent fan project.
38-0 can be played without an account. Your matches, settings and saved campaigns are stored locally on your own device (for example via localStorage), except when you use account features.
If you create an account or subscribe as a member, we store the information needed to operate those features, such as email, user identifier, membership status, renewal/expiration dates and payment references. Account sign-in currently uses an email code; Apple and Google login are disabled.
Payments are processed by external providers; 38-0 does not store full card numbers. For in-app purchases, Apple App Store or Google Play process the purchase and 38-0 stores the store receipt/transaction identifiers, an obfuscated store account token, product ID, expiry date and entitlement status needed to validate and restore your membership.
We use Cloudflare Web Analytics to understand visit volumes. This tool is privacy-focused, uses no cookies and does not identify individual people.
On the website, we also use Google Analytics 4 and the Google tag to understand, in aggregate, how people discover and use 38-0. We may measure pages and screens visited, the path between screens, active and total time on each screen, language, platform, approximate performance, game mode, gameplay and funnel actions (such as draft completion, matches, challenges, multiplayer and checkout), plus strictly limited and sanitized source/campaign parameters.
Google may use its own cookies and identifiers to produce these statistics. 38-0 keeps only session acquisition context in sessionStorage and uses a local, non-unique marker to distinguish a first visit from a return. When an account is signed in, we send Google only an irreversible hash of the internal identifier to join journeys across devices; product events do not include email, nickname, player name, room code, token, raw challenge link or payment identifier. The native iOS/Android app does not load Google Analytics. Browser settings and blockers may prevent measurement.
For email-code sign-in on the website, we may use Cloudflare Turnstile to prevent automated abuse. The native iOS/Android app does not load Turnstile, but uses the same email-code account flow.
38-0 does not show Google AdSense programmatic ads. The Google Ads tag is configured on the website for conversion measurement and may use cookies/identifiers under Google's policies; areas that would otherwise host ads appear as 38-0 membership prompts instead.
The game does not use rewarded video to unlock actions. Extra benefits, such as the additional re-roll, are tied to 38-0 membership.
You can clear locally saved data at any time by clearing this site's data in your browser settings or removing the app from your device. If you have created an account, you can delete it from the account screen in the app or use the account deletion instructions to request access, correction or deletion of the data associated with your account, where applicable. When you delete the account, we remove the 38-0 account, trophy room and app-local payment references linked to it from our database. Deleting a 38-0 account does not automatically cancel an active subscription with Apple, Google, Stripe, Asaas or another payment provider; cancel it through that provider's subscription tools.
You can also block or clear cookies and site data in your browser settings and use the Google Analytics opt-out browser add-on, where compatible.
Membership subscription rules, cancellation details and acceptable use are covered in the Terms of Use.
Questions about this policy? Get in touch: [email protected].
← Back to the game