Last updated: 7 September 2026
Eclipse Relics (the "Game") is developed and operated by Klaam Games ("we", "us", "our"). Klaam Games is the data controller for the personal data described in this policy. This policy explains what data the Game uses, why it is used, who receives it, and the choices and rights available to you.
Gameplay analytics and Ad measurement are separate choices. From version 1.0.1, the Game sends first-party gameplay and technical analytics on the basis of our legitimate interests in fixing bugs and improving the Game. You can turn this off at any time under Settings → Gameplay data; turning it off does not limit gameplay. Optional Ad measurement uses Tenjin with Meta, AppLovin and Unity Ads, and Google Analytics for Firebase with Google Ads. These marketing services are off by default and start only after you accept the current in-game Ad measurement choice. You can decline or change your choice under Settings → Ad measurement without limiting gameplay. On iOS, Apple's App Tracking Transparency ("ATT") choice is requested first; ATT authorization is also required for direct Google measurement and for Tenjin's advertising identifiers, named gameplay events and purchase details. Independently, Apple may provide aggregate SKAdNetwork measurement whether or not you enable Ad measurement or ATT. Builds released before version 1.0.1 ask for permission in-game before any optional gameplay analytics starts.
In the Game, open Settings → Delete Account and confirm the request. The Game sends the request to our server and removes local data only after the server confirms that the PlayFab player account has been permanently deleted.
If you cannot open the Game, email darthluvjoy@hotmail.com. Include your in-game display name and, if available, your player ID so we can identify the correct account. Do not send passwords or payment-card details.
Deletion removes the player account, saved progress, inventory, currencies, leaderboard and event entries, guild membership and applications, player-linked chat and activity entries, and other player-linked backend data. If other members remain, a guild itself, including its name and settings, may remain and leadership may be reassigned. Information that must be retained for legal, transaction, fraud-prevention, or security purposes may be kept only for the required period. Requests sent to analytics and attribution providers are queued after the PlayFab deletion is confirmed and are normally completed within 30 days.
| Category | Examples | Why | Required? |
|---|---|---|---|
| Account and profile | A pseudonymous PlayFab player ID, a random guest sign-in credential stored on your device, display name, account and login timestamps, and an optional recovery email address and password submitted to PlayFab if you choose to protect or recover your account. | Sign-in, saving and restoring your account, account recovery, account management, support, and security. | A guest account is required to provide the online Game. Recovery email and password are optional. |
| Game and multiplayer data | Progress, heroes, gear, inventory, currencies, energy, rewards, battle results, leaderboard scores, Boss Rush and raid results, guild membership, applications, roles, and presence. | Provide gameplay, synchronization, leaderboards, guilds, raids, events, and fraud prevention. | Required to provide the online Game. |
| User-generated content | Chat messages and guild names, mottos, descriptions, announcements, and activity entries that you choose to submit. | Provide chat and guild features, moderation, abuse prevention, and support. | Optional; only collected when you use these features. |
| Purchases | Product, price, currency, transaction status, purchase history, and receipt or signature data used to validate a purchase. We do not receive or store your payment-card number. | Validate, grant, restore, support, and prevent fraud involving in-app purchases. | Required when you make a purchase. |
| Connection and security | IP address, approximate country derived from IP, app and operating-system version, timestamps, and technical or fraud-prevention signals. | Connect to the backend, protect accounts, investigate abuse, and maintain service reliability. | Required for the online service. |
| Gameplay analytics (first-party) | Sessions, tutorial and gameplay interactions, battle and economy events, purchase events, technical diagnostics, pseudonymous player ID, and approximate country. No advertising identifiers, and no tracking across other companies' apps or websites. | Understand Game usage and performance, find and fix bugs, crashes, and freezes, and balance and improve the Game. | On by default under our legitimate interests (from version 1.0.1). You can turn it off at any time under Settings → Gameplay data. Earlier builds ask before enabling it. |
| Apple aggregate attribution | On iOS, the Game may give Apple's SKAdNetwork only a numeric conversion value from 0 to 4 and a low, medium, or high category for an install, tutorial, first summon, first campaign stage, or verified purchase. This Apple-only path sends no advertising identifier, named event, product, price, transaction ID, receipt, JWS, or PlayFab player ID from the Game. Apple decides whether and when to send an aggregate postback to the ad network and a developer copy. | Understand aggregate campaign performance. | Apple's separate aggregate SKAdNetwork path does not require the in-game Ad measurement choice or ATT authorization. |
| Tenjin attribution and partner measurement | When you enable Ad measurement, Tenjin may process app, SDK, operating-system and device information, IP address, locale and approximate country, install and campaign information, its installation identifier, Apple's Identifier for Vendors ("IDFV") and, where permitted, Apple's advertising identifier ("IDFA"), Android advertising or App Set identifiers, selected gameplay events and verified-purchase information. Purchase measurement can include product, price, currency, transaction ID and the receipt, signature or signed store transaction needed for validation. Tenjin may forward permitted measurement signals to Meta, AppLovin and Unity Ads. We do not send payment-card details, recovery credentials or the PlayFab player ID to Tenjin. | Attribute installs, measure selected campaign conversions and purchases, and improve campaigns. | Optional and off by default. Requires the current Ad measurement choice. On iOS, ATT authorization is additionally required for IDFA, named custom events, transaction identifiers and purchase details or proof. Without ATT authorization, separately consented Tenjin install measurement remains limited to app, device, network and permitted install information. |
| Direct Google campaign measurement | Google Analytics for Firebase can process an app instance identifier, permitted device or advertising identifiers, app and operating-system information, network information, approximate location, consent state, and automatic app-use signals such as first open, sessions, engagement and SDK diagnostics. On iOS, after a purchase has been verified and granted, the Game can submit the current StoreKit 2 transaction identifier through Firebase's supported Apple transaction API. Firebase uses Apple's transaction information to record the product, purchase value and currency. This additional measurement is limited to production App Store transactions; TestFlight and sandbox transactions are excluded. Automatic purchase information may also be collected where supported by the store integration. The linked Google Ads account uses eligible conversion information to measure and improve Eclipse Relics campaigns. This measurement uses identifiers and is not anonymous. The Game does not directly forward purchase receipts or signed-transaction payloads to Firebase, and does not send named gameplay milestones to Google. We do not attach your PlayFab player ID, recovery email, password, display name or chat content to Firebase Analytics or Google Ads. | Measure Google campaign installs and subsequent app use through Firebase's direct Google Ads integration. | Optional and off by default. Requires the current Ad measurement choice on Android and both that choice and ATT authorization on iOS. Google measurement remains off when these requirements are not met. |
First-party gameplay analytics. From version 1.0.1, the Game sends pseudonymous gameplay and technical analytics to PlayFab analytics by default, based on our legitimate interests in understanding how the Game is played, finding and fixing bugs, crashes, and freezes, and improving and balancing the Game. This data is used only by us, is tied to your pseudonymous player ID rather than your name, and is never used to track you across other companies' apps or websites. You can object and turn it off at any time under Settings → Gameplay data: collection stops immediately, queued analytics events are cleared, and gameplay is not limited in any way. Builds released before version 1.0.1 ask for permission in-game before enabling optional analytics.
Install attribution and marketing measurement. Optional marketing measurement uses two integrations: Tenjin with Meta, AppLovin and Unity Ads, and Google Analytics for Firebase linked directly to Google Ads. Both use the separate Ad measurement choice and never inherit the Gameplay data setting. On supported Android builds, consented Tenjin measurement may use available advertising or App Set identifiers, install information, selected conversion events and verified-purchase data. Consented Firebase measurement processes installation, automatic app-use information and the permitted verified iOS purchases described above for Google campaign measurement. We keep Google ad-personalization consent denied; eligible data is used for campaign measurement, not for personalized advertising based on this Firebase data. On iOS, verified production App Store purchases may also be measured using the current StoreKit 2 transaction identifier and the purchase information Firebase obtains from Apple. TestFlight and sandbox transactions are excluded from this additional measurement. Other supported store integrations may provide automatic purchase information. Eclipse Relics does not display third-party ads, and we do not sell personal data.
When you are asked. In releases with this updated Ad measurement choice, the Game offers the choice on the first stable startup screen before sign-in and the tutorial, when the screen and input are ready. Measurement can start after permission is obtained without waiting for sign-in. A delayed choice can also appear later at a calm point in the Game or be changed in Settings. You can take time to read the choice; a failure, interruption or lack of an answer is not consent. Existing refusals remain respected. An earlier Yes covering only the previous provider list is not reused for the expanded Firebase/Google Ads scope: the updated release asks for a new choice before enabling these marketing integrations. Earlier releases may present the choice later and do not gain the new Google integration merely because this policy is updated.
iOS and ATT. Where Apple's ATT choice is unresolved, the Game requests Apple's native choice first and then presents the separate Ad measurement choice. ATT authorization alone does not enable Tenjin or Firebase. If you decline the Game's choice, neither marketing service starts. If you agree and ATT is authorized, Tenjin may receive permitted identifiers, app, device and network context, named conversion events such as tutorial completion, first summon, first battle win, campaign stage clear and retention, and verified-purchase details and proof. Tenjin may forward corresponding permitted measurement signals to Meta, AppLovin and Unity Ads; the Game does not send StoreKit purchase proof directly to these ad networks. Direct Firebase/Google Ads measurement also requires both permissions.
If you agree to Ad measurement but ATT is denied or restricted, direct Google measurement remains off. The Game sends no IDFA, named gameplay event, transaction ID or purchase details/proof to Tenjin. Tenjin may still process IDFV and app, device, network and install information where iOS permits. This is install-level processing, not an anonymous or data-free mode. The separate Apple SKAdNetwork path described below remains available.
Apple's separate aggregate measurement. The Game may update Apple's SKAdNetwork conversion value for aggregate install, tutorial, summon, stage-clear and purchase measurement independently of both choices. This client path gives Apple only the numeric and coarse category, not an IDFA, IDFV, named event, product, price, transaction ID, receipt, JWS or PlayFab player ID. Apple may send the resulting postback to the relevant ad network and a developer copy to Tenjin's postback endpoint. Apple controls the reporting, timing and privacy protections; enabling the Firebase integration does not change the Game's existing SKAdNetwork conversion-value scheme.
Identifiers and sharing. Tenjin and Firebase use app or device identifiers for the purposes described here. The Game does not attach your PlayFab account identity or recovery credentials to either marketing SDK. The absence of a PlayFab player ID does not make the provider/device information anonymous or prevent permitted campaign tracking.
Changing your mind. Turning Ad measurement off stops the Game's new marketing-event routing, calls Tenjin's opt-out function and disables Firebase Analytics collection and its associated consent signals. Tenjin states that its SDK sends no API requests or processes events while opted out. The Google integration also asks Firebase to clear its locally stored analytics data and reset the Firebase app instance identifier. When Firebase processes that reset, later measurement can use a new app instance identifier if you grant permission again. On iOS, losing ATT authorization also stops direct Google measurement. A local reset does not delete data already held by Google or another provider. Withdrawal does not affect processing that occurred before it; use Delete Account or contact us for help with deletion of previously processed data.
Gameplay milestones and purchases that occur before the current Ad measurement consent are not queued by the Game for later marketing replay. Consented events may be held temporarily for delivery when a network connection returns. Ad measurement does not change Apple's ATT setting, which you can manage in iOS Settings, and does not stop Apple's separate aggregate SKAdNetwork processing. On Android, you may reset or limit the advertising identifier in the device's privacy settings. Core PlayFab data needed for sign-in, saved progress, multiplayer, purchases, security and account deletion continues to be processed so the Game can work.
Providers process data under their agreements and privacy terms. Some providers may process data outside your country, including in the United States, using the transfer safeguards available under applicable data-protection law.
Where the European Economic Area or United Kingdom data-protection rules apply, we process core account, gameplay, multiplayer, and purchase data because it is necessary to provide the Game you request. We process security and fraud-prevention data based on our legitimate interests in protecting players and the service, and we retain information where required by law. First-party gameplay and technical analytics are processed based on our legitimate interests in understanding, securing, and improving the Game; you can object at any time using the Gameplay data setting, and in builds released before version 1.0.1 this processing is based on consent instead. Tenjin install-level attribution, its partner measurement, and direct Firebase/Google Ads marketing measurement are based on the separate consent you give through the current Ad measurement choice. We use Apple's privacy-preserving aggregate SKAdNetwork measurement for our legitimate interest in understanding aggregate campaign performance where applicable law permits. On iOS, Apple's ATT authorization is a separate system permission required before we access IDFA or permit install-linked cross-company tracking; ATT authorization alone never enables Tenjin or Firebase, and declining or withdrawing the Game's Ad measurement choice overrides it, but does not disable Apple's separate aggregate SKAdNetwork path.
Core game data is retained while the account remains active and until it is deleted. Chat, reports, and guild activity may be kept in limited rolling histories or for as long as reasonably needed for the feature, moderation, security, or support. Purchase, fraud-prevention, and legal records may be retained for the period required by applicable law or a legitimate security need. The local Ad measurement choice remains until you change it or clear the Game's local data. If Tenjin has previously been initialized, its installation identifier is cached locally after opt-out only so a later deletion request can be routed; it is removed after verified account deletion or local-data reset. Tenjin's current Data Processing Addendum states that attribution data is retained for between 30 days and 24 months depending on customer and partner contractual requirements, after which it is deleted or anonymized unless law requires otherwise. Meta's Business Tools Terms permit Event Data to be retained for a maximum of two years, while Meta may preserve information longer where required for legal, security, or integrity purposes. An account-deletion request queues the identifiers needed for applicable provider-side deletion. AppLovin states that information collected through its advertising services is retained for limited periods, typically up to two years, subject to deletion requests and legal exceptions. Google Analytics data is retained according to the retention and deletion controls configured for the service and Google's applicable terms; Unity and other recipients apply their applicable privacy terms and legal obligations. We keep marketing measurement only for as long as needed for the stated purposes, applicable retention controls and legal requirements. The Google integration requests a local analytics-data and app-instance-identifier reset when measurement permission is withdrawn; this is a local reset request, not confirmation that previously sent provider data has been deleted. Contact us to request deletion or information about the retention settings that apply to your data.
Data sent between the Game and its online services is encrypted in transit using HTTPS/TLS. Access is limited to systems and people that need it for operation, support, security, or legal compliance. No online system can guarantee absolute security.
Depending on where you live, you may have rights to access, correct, delete, restrict, or object to processing of your personal data, receive a portable copy, and withdraw consent. You can object to first-party analytics under Settings → Gameplay data and withdraw marketing-attribution consent under Settings → Ad measurement. On iOS, you can separately change ATT permission in the device's Settings. Withdrawal stops future processing as described above but does not itself delete data already processed; use Delete Account or contact us for deletion. You may also complain to your local data-protection authority. We may need enough information to verify that the request concerns your account.
Eclipse Relics is intended for players aged 18 and over. It is not directed at children, and we do not knowingly collect personal data from children.
We may update this policy when the Game, providers, or legal requirements change. The current version and revision date will remain available on this page. Material changes will be communicated where required.
Questions, privacy requests, deletion requests, and requests concerning Tenjin, Meta, AppLovin, Unity Ads or Firebase/Google Ads measurement data can be sent to Klaam Games at darthluvjoy@hotmail.com. Include your in-game display name and player ID if available, but do not send passwords, StoreKit receipts, transaction identifiers, advertising identifiers, or payment-card details.