Privacy Policy
Effective date and last updated: September 8, 2026
This Privacy Policy explains how Chillgames LLC (“Chillgames,” “we,” “us,” or “our”) handles personal information when you use chillgames.net, games hosted there, and native mobile games that we publish (together, the “Services”). This is a privacy notice, not a request to agree to every use of your information. When the law requires consent, we ask for it separately.
Our contact for privacy questions and requests is ben@chillgames.net. We do not publish a postal address in this Policy. Our Terms of Use apply separately to use of the Services.
1. Information We Handle
The information involved depends on which Service and features you use.
Information you provide
- Account and profile information. If you create a website account, we receive your email address, username, password, and any optional profile information you add, such as your full name. Supabase provides our authentication service and stores password hashes. If you sign in with Google, Google provides a sign-in credential and Supabase provides the related account information needed to authenticate you. We also record the version and time of your acceptance of our Terms.
- Public comments. If you post a game comment, we store the comment, your account identifier, username, game, and posting time. Your username, comment, and posting time are public. Do not include private information in a public comment.
- Communications and feedback. We receive the information you include when you email us, request support, exercise a privacy right, or submit feedback or a survey.
- Career applications. If you follow our careers link and submit the linked Google Form, Google and Chillgames receive the information described on that form.
- Website support payments. Stripe collects the payment, contact, and billing information needed to process a support payment. If you are signed in, we send your account email to Stripe to prefill the checkout form. We receive transaction information such as the amount, currency, status, and transaction identifiers, but not your complete payment-card number.
Website and web-game information
- Technical and log information. Our hosting, security, database, and asset-delivery providers may process IP address, date and time, requested URL, referrer, browser, operating system, device type, network and error information, and an approximate location derived from IP address.
- Cookies and local storage. We use these technologies for sign-in sessions, security, game progress, preferences, and remembering choices such as a dismissed notice or your privacy selection.
- Game and community activity. Depending on the game, we may process game state, progress, scores, number of moves or clicks, achievements, game identifiers, and leaderboard entries. Signed-in high scores can be associated with your account and displayed with your username.
- Optional PostHog usage analytics. Analytics is off until you affirmatively opt in. If you accept, we count page visits, supported game loads and achievements, using browser/device details and a random browser identifier. An analytics cookie remembers that identifier for up to 90 days after activity so we can estimate repeat visits without linking it to your account. We do not send account IDs, email addresses, names, comments, URL query strings, or URL fragments in these events. We disable session recordings, automatic interaction capture, IP-address event storage and IP-based location enrichment. PostHog and hosting providers still receive network connection information needed to deliver their services. Browser privacy signals and your choices are handled as explained in Section 5.
Some web games load files from Supabase or are embedded from another origin, including chillgames.ai and codetype-xi.vercel.app. Your browser connects to those origins when you load the relevant game, so the operator of that service receives ordinary request information such as your IP address and browser details.
Native mobile-game information
Features vary by game, version, device, and marketplace. A native game may handle:
- A random per-install player UUID created and kept on your device. It is not your IDFA, Apple ID, or a cross-app account identifier. It normally resets when the app is deleted and reinstalled.
- Local progress, settings, entitlements, and transaction records stored on your device.
- Device, app-version, IP-address, coarse-location, performance, crash, and diagnostic information made available by the operating system, app marketplace, or an integrated service.
- Advertising information described in Section 6, when the game offers ads.
- Mobile purchase information described in Section 7, when the game offers in-app purchases.
PostHog telemetry and remote feature-flag calls are disabled in current shipped native builds. Developer builds may enable telemetry for local testing; those builds are not distributed to players.
The app marketplace’s privacy label provides additional app-specific disclosures. Contact us if a marketplace disclosure appears inconsistent with this Policy.
Sources
We obtain information directly from you, automatically from your browser or device, from other users when they interact with public features, and from service providers such as Google, Apple, Supabase, Stripe, PostHog, and the app marketplaces.
2. How We Use Information
We use information to:
- Provide, secure, maintain, and troubleshoot the Services
- Create accounts, authenticate users, and remember settings
- Save game progress, operate leaderboards, and publish comments
- Provide support and respond to communications and privacy requests
- Process payments, deliver purchases, restore entitlements, prevent fraud, and keep required financial records
- Provide consented website analytics, understand feature performance, and test improvements
- Serve and measure ads in mobile games that offer them
- Enforce our Terms, protect users and the Services, and comply with law
For people in the EEA, UK, or another place that requires a legal basis, our bases depend on the use: performance of a contract or steps you request for accounts, gameplay features, and transactions; consent for optional website analytics and mobile-advertising storage or access where consent is required; our legitimate interests in security, support, fraud prevention, service operation, and proportionate product improvement; and compliance with legal obligations for matters such as financial records and valid legal requests. You may withdraw consent at any time, without affecting earlier processing.
We do not make decisions based solely on automated processing that produce legal or similarly significant effects about you.
3. When We Disclose Information
We disclose information only as described here:
- Service providers and platforms. We use the providers listed in Section 4 for hosting, authentication, storage, analytics, payments, advertising, distribution, and related operations. They receive the information needed for their role.
- Public features. We publish the information described above when you post a comment or qualify for a public leaderboard.
- Legal and safety reasons. We may preserve or disclose information when we reasonably believe it is necessary to comply with law or legal process, protect rights or safety, investigate fraud or security problems, or enforce our Terms.
- Business changes. Information may be reviewed or transferred as part of a financing, reorganization, sale, merger, acquisition, or similar transaction, subject to applicable law.
- At your direction. We may disclose information when you ask us to or give consent.
We do not sell personal information for money. We do not use chillgames.net or our current mobile-ad configuration for cross-context behavioral advertising. Section 6 explains the limited information AdMob still uses for non-personalized ads and the available controls.
4. Services We Use
- Vercel hosts chillgames.net and processes ordinary network request and hosting-log information. Vercel Web Analytics is disabled. See Vercel’s Privacy Policy.
- Supabase provides website authentication, database and file storage, including accounts, profiles, comments, and remote game assets. See Supabase’s Privacy Policy.
- Redis Cloud stores temporary state for Emoji Memory and user-linked leaderboard entries. See Redis’s Privacy Policy.
- PostHog provides opt-in website analytics. PostHog telemetry is disabled in current shipped native builds. See PostHog’s Privacy Policy.
- Stripe processes website support payments. See Stripe’s Privacy Policy.
- Discord receives internal website payment notifications containing the amount and currency. We do not include payer account IDs, names, email addresses, or transaction identifiers in these notifications.
- Google provides Google Identity, Google Forms, AdMob, Google Play, and Google Play Billing where those features are used. See Google’s Privacy Policy and AdMob’s data disclosure.
- Apple distributes iOS and related apps, provides the App Store version-lookup service used to check for updates, and processes StoreKit purchases. See Apple’s Privacy Policy.
Some providers act as our processors or service providers, while others independently determine how they handle information for their services. Their own notices explain those independent uses.
5. Website Cookies, Analytics Choices, DNT, and GPC
Website sign-in, security, preferences, and game-saving technologies operate when needed to provide a feature you request. Blocking them may prevent that feature from working.
Website PostHog usage analytics is optional and remains off unless you choose to enable it through the website’s privacy controls. Acceptance enables the analytics cookie and events described in Section 1, not advertising or recordings. You can withdraw through the same controls; we stop new analytics collection and remove the analytics cookie. Clearing site data also removes local choices and may sign you out or erase locally stored progress. Earlier refusals remain refusals, and acceptance of an earlier, narrower analytics setup is not automatically carried over to this version.
Some browsers provide Do Not Track (DNT) or Global Privacy Control (GPC) signals. Either signal keeps usage analytics off by default, including overriding an ordinary earlier acceptance. With the signal active, you can separately and explicitly enable usage-only analytics in Privacy Preferences. That choice never authorizes data sales, cross-context advertising, or session recordings. Necessary hosting logs are not controlled by the optional analytics setting.
We do not permit third-party advertising on chillgames.net. A third-party embedded game or linked service may have its own tracking practices and controls, which we do not operate.
6. Mobile Advertising
Some native mobile games offer non-personalized ads through Google AdMob. We configure AdMob to disable publisher ad personalization and set the maximum ad-content rating to Google’s General category. That content-rating setting does not determine the intended age of a game. We do not request App Tracking Transparency permission or use the IDFA.
Non-personalized does not mean no data is processed. AdMob may still process device and app information, IP address and approximate location, ad interactions, and limited identifiers for ad delivery, frequency capping, fraud prevention, security, and aggregated reporting.
The app refreshes Google’s consent information each session and requests ads only when Google reports that ads may be requested. Where available, you can reopen Ad Privacy Choices from the game’s Credits screen. You can also review Google’s Ads Settings and your device’s advertising settings. We do not intentionally send your chillgames.net account credentials or website profile to AdMob.
7. Purchases and Support Payments
Website support payments are processed by Stripe as described above. We use the resulting transaction record to confirm the payment, provide support, prevent fraud, and meet accounting or legal obligations.
In-app purchases are processed by the marketplace, such as Apple StoreKit or Google Play Billing. The marketplace may provide a product identifier, transaction identifier or token, status, and receipt information needed to deliver or restore the purchase and prevent duplicate fulfillment. The marketplace handles your payment card under its own terms and privacy policy.
8. Retention
We keep information only for as long as reasonably needed for the purposes described above, including:
- Account and profile information while the account is active and afterward as needed for security, dispute resolution, backups, or legal obligations
- Public comments until you delete them or the related account is deleted, subject to any temporary backup copies
- Temporary web-game state for a short operational period; new or updated monthly Emoji Memory leaderboards are limited to the top 100 entries and expire no later than 400 days after the board’s last update. Older boards created before these limits were introduced may remain until we complete historical cleanup
- Analytics according to our configured provider retention settings, after which it is deleted or aggregated
- Purchase and support-payment records as needed to fulfill transactions and meet tax, accounting, chargeback, and fraud-prevention obligations
- Support, privacy-request, feedback, and application records for the time needed to respond, document the request, make a decision, and meet legal obligations
- Local device or browser data until it expires, you clear it, or you uninstall the relevant app
Deletion from active systems does not always remove information immediately from security logs or backups. We delete or isolate those copies through ordinary retention cycles unless law or a security need requires longer retention.
9. Your Rights and Choices
Depending on where you live, you may have rights to:
- Know, access, or receive a portable copy of personal information
- Correct inaccurate personal information
- Delete personal information
- Restrict or object to certain processing
- Withdraw consent
- Opt out of sale, sharing, targeted advertising, or certain profiling
- Appeal our decision on a request
- Complain to a privacy or data-protection authority
To make a request, email ben@chillgames.net. Describe the Service and account or device involved. We may ask for information reasonably needed to verify your identity and authority. An authorized agent may submit a request where applicable law permits, but we may verify the authorization and your identity. We will not discriminate against you for exercising a privacy right.
You can also use the website controls described in Section 5, a game’s Ad Privacy Choices entry where available, mobile operating-system settings, Google advertising controls, or the relevant app marketplace. If information is controlled independently by Apple, Google, Stripe, or another provider, you may need to direct a request to that provider.
10. California and Other U.S. State Disclosures
The categories of information we collect, their sources, purposes, and the categories of recipients are described in Sections 1 through 4. We retain them using the criteria in Section 8.
For chillgames.net, DNT and GPC keep optional usage analytics off by default, with the separate usage-only choice described in Section 5. The website has no third-party advertising and does not sell or share website personal information for cross-context behavioral advertising. Accepting usage analytics does not change that. Current mobile advertising is configured as non-personalized and is described in Section 6.
If a U.S. state privacy law applies to our handling of your information, you may use the request process in Section 9. Whether a particular statutory right applies can depend on the law’s scope and exemptions.
11. International Processing
Chillgames and our providers may process information in countries other than the one where you live, including the United States. Privacy laws may differ in those countries. Where applicable law requires a transfer safeguard, we use an available lawful mechanism for the provider and transfer involved. Contact us for information about safeguards relevant to your information.
12. Children’s Privacy
We do not knowingly collect personal information from children under 13. Children under 13 may not create an account, post a public comment, make a website support payment, or submit personal information through the Services. Parents and guardians should review each game and its marketplace listing before allowing a child to use it; a marketplace content rating does not describe the game’s privacy practices.
If you believe a child has provided personal information to us, contact ben@chillgames.net so we can investigate and take appropriate action. This Policy does not replace any parental notice or consent that applicable law may require.
13. Security
We use reasonable administrative, technical, and organizational safeguards designed for the information we handle. Supabase stores password hashes rather than plaintext account passwords. No system is completely secure, so we cannot guarantee that information will never be accessed, lost, or misused.
14. Changes to This Policy
We may update this Policy as our Services or legal obligations change. We will post the updated Policy here and change the date above. When applicable law requires additional notice or consent for a material change, we will provide it before the change applies.
15. Contact
Chillgames LLC is responsible for this Policy. For privacy questions, requests, or complaints, email ben@chillgames.net.