Goblin Elf Clash / 哥布林大戰精靈
Privacy notice
If you sign up for launch updates, we collect the email address you provide only to send a subscription confirmation and news about the launch of Goblin Elf Clash. Addresses that have not confirmed will not receive launch updates.
EmailOctopus provides and processes the signup form and subscriber list. Loading the form connects your browser to its service. Its anti-abuse feature may also load a third-party verification service. EmailOctopus handles confirmation, sending, and unsubscribing, and may record email opens and link clicks.
Every launch email will include an unsubscribe link. You can also write to [email protected] with privacy questions or data deletion requests.
This website uses Google Analytics 4 and cookies to understand page views, visits, approximate location, device and browser information so we can improve the website. Google processes this data and may process it on servers outside your country or region. We do not send subscription email addresses to Analytics or enable advertising personalization or automatic form interaction tracking.
Cloudflare determines your approximate country or region from your connection IP, not your browser language. Analytics starts automatically for visitors in Hong Kong, the United States, Australia and New Zealand. Elsewhere, or if location cannot be determined, it loads only after you allow it. Automatic activation is not recorded as your consent. You can allow or decline analytics at any time using Analytics preferences in the footer. Valid saved choices take priority over regional defaults; your browser’s Global Privacy Control signal keeps analytics off. Declining or withdrawing stops further analytics and clears accessible Analytics cookies; withdrawal does not delete data already sent. Analytics choices and Analytics cookies last up to 180 days; your browser may clear them sooner.
We use browser local storage to remember your analytics choice and manual language preference. Our hosting provider may process connection information to serve and protect the website. The analytics choice does not control the EmailOctopus form or its anti-abuse services.
Gameplay analytics in the iOS and Android game stays off until you confirm sharing. Only after you confirm sharing at startup or enable Share gameplay statistics in Settings do Google Firebase Analytics (GA4) and PostHog receive screen views, faction, battle mode and outcome, round and chapter progress to help improve the game. The services also process random app identifiers, app version, device and network information. Google and PostHog may process data outside your country or region; PostHog uses its US service.
The game does not send room codes, online player identities, deck contents or replay data to analytics services, record screens, collect advertising identifiers, or enable advertising personalization. PostHog does not create player profiles or store connection IP addresses, and IP-based location enrichment is disabled; services still receive the network connection needed to deliver statistics. You can turn analytics off in game Settings at any time to stop further collection and reset local analytics identifiers. Turning it off does not delete data already received by the services or affect gameplay. The game remembers this choice locally and separately from this website’s analytics preference.
When you buy or restore the supporter pack, Apple or Google processes payment. We do not receive payment card details. The game sends the product identifier, store transaction identifier and signed transaction or purchase token to our Supabase-hosted verification service, which checks purchase and refund status with the relevant store. The verifier processes receipt proof in memory without writing it to application logs or a server database; hosting services may still process connection and operational records. Data may be processed outside your country or region. The game stores receipt proof, verified access and your card-back choice locally for restoration, rechecking and offline use; uninstalling removes this local app data. Purchase verification operates independently of the gameplay analytics setting. When gameplay analytics is enabled, Firebase may also automatically collect store purchase events, such as product, value and currency.
Optional crash diagnostics are separate from gameplay analytics and stay off until you confirm sharing. The startup screen initially selects both optional sharing choices, but no sharing starts until you explicitly confirm; you can turn either off or choose to continue without sharing. If you confirm Share crash reports at startup or enable it in Settings, Google Firebase Crashlytics receives crash/error stack traces, app version, device and operating-system information, crash timestamps and installation identifiers to help us diagnose problems. Flutter reports omit exception messages and custom player identifiers; native crash reports may include technical error details. We do not deliberately attach names, room codes, receipt proof or deck contents. If you also enable gameplay analytics, Google Analytics events may appear as diagnostic breadcrumbs. Google may process this data outside your country or region.
You can change both optional choices independently in Settings without losing access to play. Turning crash reports off stops application-submitted errors immediately; the native SDK applies withdrawal no later than the next app launch. Data already sent is not deleted by turning a setting off. When automatic reporting is off, the SDK may retain crash information locally. Newly enabling reporting discards pending reports before enabling uploads. Contact us with privacy or deletion requests; we may need information to locate records because guest play does not use an email account.
Online battles use Epic Online Services (EOS) for device-based guest identity, authentication, room discovery and peer connectivity. EOS processes a device credential, product user identifier, a display name and connection information. Room metadata includes the game mode and room code. The other participant receives data needed to play; the host device processes the battle state. Peers may receive network addressing information as part of peer-to-peer connectivity. These functions require service data independently of optional analytics and crash reporting. We do not currently store online match history or offer cloud saves. Uninstalling may remove guest credentials and local progress. Epic and network service providers may process data outside your country or region.
Last updated: 3 October 2026.
Google privacy policy · How Google uses data from partner sites · PostHog privacy policy