Privacy Policy
1. Scope
This policy describes how CORE SHIFT handles information on your device and which third-party software development kits (SDKs) are integrated in the current app. It is specific to CORE SHIFT and is based on the project’s current privacy data inventory.
2. No first-party game account
CORE SHIFT does not require a user account or sign-in to play. First-party game code does not operate a dedicated game backend that receives your gameplay profile.
3. Data stored by the app on your device (first-party)
The app may store the following locally (for example in device storage / localStorage) to run the game:
- Gameplay resume data (board, sector, score, and related attempt flags).
- Settings such as language and sound preference.
- Retention data such as daily claim day, streak, free power credits, best sector / score, and counters used for rewards and ad pacing.
- A timestamp related to the last rewarded-ad interaction.
- A write-only entitlement cache timestamp used for audit purposes. This cache is not used by itself to grant CORE SHIFT PRO.
Local analytics events (allowlisted event names and limited numeric gameplay fields) are kept in memory only (recent events) and are not sent by first-party game code to an external analytics endpoint.
4. Data not collected by first-party game code
First-party CORE SHIFT game code does not collect: name, email address, phone number, contacts, precise location, photos, microphone audio, payment card numbers, or an analytics user ID.
5. Purpose of processing
- Local game progress, preferences, daily rewards, and ad pacing.
- Optional rewarded ads and policy-gated interstitial ads (Google AdMob).
- In-app purchase and restore of CORE SHIFT PRO (RevenueCat + Google Play / App Store).
- Responding to support requests when you email us.
6. Third-party SDKs currently integrated
The app integrates the following SDKs. When those SDKs run, they may process data according to their own technologies and policies, including over the network. This is not a claim that CORE SHIFT collects no data.
6.1 Google AdMob (ads & consent)
Used for optional rewarded ads and policy-gated interstitial ads via the Capacitor AdMob plugin and Google Mobile Ads / User Messaging Platform components.
- May process ad availability, show / dismiss / reward callbacks, and consent-form status.
- When ads are requested, ad and consent traffic may be sent to Google advertising / consent endpoints.
- The app requests non-personalized ads configuration in code (
npa: true). Advertising-ID related permissions are removed from the Android app manifest where configured; if an advertising identifier cannot be accessed, that path fails closed. - Transitive Google ads libraries may still ship measurement / transport components. Exact processing by Google depends on device, region, consent state, and Google’s policies.
6.2 RevenueCat (in-app purchases)
Used for lifetime CORE SHIFT PRO purchases and restore via RevenueCat together with Google Play Billing and/or Apple StoreKit.
- May process a public RevenueCat SDK key (build-injected), product metadata / localized price strings, and verified entitlement state.
- Purchase and restore flows are handled through RevenueCat and the platform store.
- In the current app configuration, RevenueCat diagnostics are disabled and automatic device-identifier collection is disabled in the SDK configure call.
- PRO entitlement is accepted only when RevenueCat verification succeeds under enforced verification for the configured lifetime product.
Platform stores process payment details under their own terms. CORE SHIFT first-party code does not receive your full payment card number.
7. Device identifiers, diagnostics, and network
- Network access is used so ads and purchase / restore features can reach Google / Apple / RevenueCat services when those features run.
- The app does not implement a separate first-party crash-reporting or remote diagnostics product beyond what the integrated SDKs may do under their configurations.
- Device or advertising identifiers may be involved by advertising or store SDKs depending on OS permissions, consent, and vendor behavior.
8. Sharing with third parties
First-party game code does not sell your personal information. Data may be processed by third parties only as needed to provide ads, billing, and purchase verification — currently Google (AdMob / Play), Apple (App Store / StoreKit where applicable), and RevenueCat — under their respective policies and your platform account terms.
9. Retention and deletion
- Local first-party data remains on your device until you clear app data, uninstall the app, or otherwise remove local storage.
- Ad and purchase providers retain data according to their own retention policies and store account records.
- Support emails you send to us are retained as needed to respond to your request.
10. Children
CORE SHIFT is a general-audience puzzle game. Do not provide personal information through support channels if you are not permitted to do so.
11. Your choices
- You can play without watching optional rewarded ads.
- CORE SHIFT PRO (lifetime) removes interstitial ads; rewarded ads remain optional.
- You can use platform consent / privacy options where shown, and Ad privacy options in Settings when available.
- You can clear local app data through your device settings.
12. Contact / questions
Privacy or support questions for CORE SHIFT: INFO@TANGLEON.NET
Also see Terms of Use and Support.
13. Changes
We may update this page when the app’s SDKs, store configuration, or data practices change. The “Last updated” date above will change when this page is revised.