Privacy policy
In short. You can play Core Reactor without creating an account. Your base, Contracts progress, hardware samples (battery, charging state, temperature, connection type, battery saver, Do Not Disturb, headphones) and settings stay on your phone by default.
What leaves the phone: an anonymous technical identifier, purchase status, optional crash reports and usage statistics, and - if you watch ads - advertising data handled by Google AdMob. After the tutorial, the App may also create a silent anonymous Firebase Authentication session and, if you choose Settings → Sign in with Google, store a cloud copy of your progress in Firestore (and receive your Google account email from the sign-in). In the European Economic Area, the UK and Switzerland, ads and analytics run only after the Google consent message (or when consent is not required).
This page is hosted at playcorereactor.com. Visit statistics (Microsoft Clarity and Firebase Analytics) run only with your consent. Details in section 15.
1. Who we are
We are Smart Apps Factory (“we”, “us”), the maker of Core Reactor: Idle Strategy (the “App”) and this website. The full details of the data controller are in section 16.
For personal data: privacy-smartappsfactory@gmail.com. Anything else: smartappsfactorydevs@gmail.com. The rules for using the App are in the terms of use.
2. Data that stays on your device
The following is stored only in the App’s private storage on your phone. We cannot see it from our side.
- your game progress: resources (Power, Silicon, Code, Cores), base nodes, research, Eras, Reboot / Blueprints, quests, streak and related counters,
- Contract results (board seed, stars, moves) and tutorial progress,
- settings (notifications opt-in, sound, haptics, consent flags) and which in-app purchases have already been granted,
- hardware samples used only to drive the in-game Day Rhythm: battery level, whether the phone is charging, battery temperature, connection type (Wi‑Fi / mobile / none) and, when available without extra permission, whether the screen is on. Each sample also records three yes/no flags: whether battery saver is on, whether Do Not Disturb is on, and whether headphones are connected with the media volume at or below 50%. Samples are kept for a limited time on the device and then aggregated or removed,
- the ambient light level, read from the light sensor only while the base screen is open. It is used on the spot and not saved. The App remembers only the day you last used the Solar Collector,
- a random anonymous identifier created on first launch (see section 3).
Hardware samples are read with ordinary Android system APIs. The App does not use usage-access, location, contacts, camera, microphone or network traffic counters. It checks whether Do Not Disturb is on, but does not read your notifications, and it checks whether headphones are connected, but not what you play. Samples are not uploaded to our servers.
The App is excluded from Android automatic cloud backup. Uninstalling the App or using Settings → Delete progress (after the double confirmation) removes the game data listed above and, when the device is online, also deletes the optional cloud copy described in section 3a. The anonymous installation identifier may be kept so purchase restore can still work.
3. Anonymous technical identifier
When the App starts, it creates a random identifier on the device (a UUID). It is not a Google account. On its own it is not linked to your name, email address or phone number.
We use it to:
- attach crash reports and usage statistics to one installation (section 5),
- identify you to RevenueCat so purchases can be checked and restored (section 6).
3a. Optional cloud save (Firebase Authentication and Firestore)
After you finish the tutorial, the App may sign in silently with anonymous Firebase Authentication. That creates a Firebase user ID used only for cloud save. It is separate from the installation UUID in section 3. Without linking a Google account, that anonymous ID is lost if you uninstall the App, so the cloud copy cannot be restored on another device.
In Settings you can choose Sign in with Google (Credential Manager). Then:
- Google Sign-In may provide your email address and a Google account identifier to Firebase Authentication so the same Firebase user can be opened on another phone,
- we store a cloud copy of your game progress in Google Cloud Firestore under
users/{uid}/save/current(encoded progress, Contract results, a progress score and a server timestamp). Hardware samples from section 2 are not uploaded, - you can trigger a backup or restore from Settings. If local and cloud progress differ, the App may ask which copy to keep.
Cloud save can be turned off remotely for everyone with Firebase Remote Config (cloud_save_enabled). Delete progress also requests deletion of the Firestore document when the network is available.
4. Ads
The free App may show Google AdMob ads: voluntary rewarded ads (for example double Report reward, timer skip, Contract hint) and a limited interstitial after collecting a Report (not during a Contract, not in the first three days, and not right after a purchase). Operator Pro removes interstitials and grants rewarded benefits without watching an ad.
- Advertising ID: the App declares the Android advertising ID permission so AdMob can serve ads. In the European Economic Area, the UK and Switzerland, personalized ads and related ad storage follow your choice in the Google User Messaging Platform (UMP) consent message.
- Consent message (UMP): on first need the App asks Google whether consent is required in your country and, if so, shows the message. Google receives your IP address and basic technical device data for this. Your choice is stored on the device in the standard IAB TCF format.
- Change or withdraw: where Google requires a privacy options entry point, open Settings → Privacy and consent in the App.
Ad networks may process data outside the European Economic Area under the safeguards required by the GDPR. We do not sell your data.
5. Diagnostics and usage statistics
- Crash reports (Firebase Crashlytics): device model, Android version, App version, the anonymous identifier from section 3 and the technical trace of the error. We do not add hardware samples, Contract boards or resource balances to crash reports.
- Usage statistics (Google Analytics for Firebase): events such as screens opened, tutorial steps, Contract and shop actions, ad placements and purchases, tied to a random app-instance identifier and to the anonymous identifier from section 3. In the European Economic Area, the UK and Switzerland we collect them only with your consent (via UMP / Consent Mode). Outside those regions, collection may start without a separate prompt when consent is not required. Analytics storage and ad-related Consent Mode signals default to off until consent status is known.
- Remote configuration (Firebase Remote Config): the App downloads balance numbers and the cloud-save kill switch from Remote Config. That download is configuration only; it is not used to read your hardware samples or your cloud save document.
You can change ad and statistics consent where the privacy options form is available: Settings → Privacy and consent. You can also limit ad personalization in your Android Google settings.
6. Purchases
One-time purchases (Cores packs, Operator Pro, cosmetics and Contract packs) are handled by Google Play. We use RevenueCat to check whether a purchase is active and to restore it after reinstall.
- RevenueCat and we receive the product, the purchase status and dates, a purchase token, your country and currency.
- Your customer identifier at RevenueCat is your anonymous identifier from section 3.
- RevenueCat also receives your IP address and basic technical device data, such as the Android and App version and the language.
- When you restore a purchase after reinstalling, RevenueCat moves it to the current anonymous identifier.
We never receive your card number or other payment details. There is no subscription in the current App version.
7. Permissions the App asks for
| Permission | Why |
|---|---|
| Internet | To show ads, check purchases, send diagnostics, fetch Remote Config and (after the tutorial) run optional cloud save / Google Sign-In. |
| Network state | To know the connection type (Wi‑Fi / mobile / none) for the in-game Flux rhythm. No traffic volume is read. |
| Notifications | Optional. Only if you turn them on - for example when a build or research finishes. Max two per day, quiet hours 22:00–08:00 by default. |
| Advertising ID | So AdMob can serve ads (section 4). |
Battery level, charging state and battery temperature are read with the standard system battery broadcast. No special permission is required for that. The same goes for the battery saver, Do Not Disturb and headphone checks and for the light sensor.
8. What we do not collect
- your name or phone number for a mandatory App account (the game works without Sign in with Google),
- precise location, contacts, photos, camera or microphone,
- a history of other apps you use, or usage-access data,
- network traffic volume or packet contents,
- hardware samples uploaded to our servers.
If you use Sign in with Google, Firebase Authentication may receive your Google email address (section 3a). We do not use that email for marketing.
We do not sell your data. Power and Contract stars are not shop products - purchases are optional convenience and cosmetics only.
9. Legal bases
- Performance of a contract (Art. 6(1)(b) GDPR): running the game on your device, purchases and restore, and optional cloud save / Google Sign-In when you use those features.
- Consent (Art. 6(1)(a) GDPR, and for cookies / similar technologies the ePrivacy rules): personalized ads and usage statistics in the App where UMP requires consent; optional notifications; Microsoft Clarity, Firebase Analytics and statistics cookies on this website.
- Legitimate interest (Art. 6(1)(f) GDPR): security and abuse prevention, crash diagnostics, checking whether the consent message has to be shown, Remote Config delivery, and non-personalized ads where allowed.
10. Who processes the data
| Provider | What for |
|---|---|
| Google (Firebase Auth, Firestore, Remote Config, Crashlytics, Analytics, AdMob, Play, UMP, Hosting) | Hosting of this site, optional cloud save and Sign in with Google, Remote Config, crash reports, usage statistics, ads, consent message, payments |
| Microsoft (Clarity) | Session recordings and heatmaps of playcorereactor.com, only with consent |
| Google (Firebase Analytics / GA4 on this website) | Page views and Google Play CTA clicks on playcorereactor.com, only with consent |
| RevenueCat | Checking the status of purchases |
These providers may process data outside the European Economic Area, including in the United States, under the safeguards required by the GDPR, such as standard contractual clauses or an adequacy framework.
11. How long we keep data
- Data on your device: until you uninstall the App, clear its data or use Delete progress.
- Cloud save in Firestore: until you use Delete progress (online), unlink/delete the Firebase user, or ask us to delete it.
- Firebase Authentication profile (anonymous or Google-linked): for as long as the cloud-save account exists.
- Hardware samples on the device: raw samples for a limited window (on the order of days), then aggregated or removed.
- Crash reports: up to 90 days.
- Usage statistics: up to 14 months.
- Purchase records: for as long as tax and accounting law requires.
- Website server logs: as kept by Firebase Hosting for security and operation of the site.
- Microsoft Clarity: session recordings up to 30 days, aggregated site statistics up to 13 months.
- Firebase Analytics on this website: up to 14 months.
12. Your rights
Under the GDPR you can ask for access to your data, its correction, deletion or restriction, object to processing, and ask for a copy in a portable form. You can also lodge a complaint with your data protection authority; in Poland this is the President of the Personal Data Protection Office (UODO).
Most on-device data can be removed by clearing the App’s data, uninstalling it or using Delete progress (which also deletes the cloud copy when online). If you signed in with Google, you can also write to privacy-smartappsfactory@gmail.com and ask us to delete the Firebase Authentication / Firestore data tied to that account.
13. Age
The App is intended for people aged 16 and over. It is not directed at children. We do not knowingly collect data from children.
14. Changes
If this policy changes, we will publish the new version on this page and update the date at the top.
15. This website (playcorereactor.com)
- Server: the site is served by Google Firebase Hosting. For every visit the server may record technical request data, including the IP address and browser type, for security and to run the site (legitimate interest).
- Your cookie choice is stored in your browser (localStorage, keys
stcm.consent.*). This is essential, so we do not ask on every visit. - Microsoft Clarity starts only after you allow “Analytics”. It records how you use the site: clicks, scrolling, mouse movement and session recordings, plus device data and an approximate location derived from the IP address. Text typed into fields is masked. Clarity sets the cookies
_clck(up to a year),_clsk(one day) andCLID(up to a year), and Microsoft may also useMUID. The data is processed by Microsoft Corporation, including in the United States (EU-U.S. Data Privacy Framework). More: Microsoft privacy statement. - Firebase Analytics (Google Analytics 4, measurement ID
G-XQ1YS5XV4Q) also starts only after you allow “Analytics”. It records page views and clicks on Google Play buttons (placement and language), so we can see which parts of the site lead to installs. It may set cookies such as_gaand_ga_*. The data is processed by Google LLC, including in the United States (EU-U.S. Data Privacy Framework). More: Google privacy policy. - Changing your choice: “Cookie settings” in the site footer or the icon in the bottom-left corner. After you withdraw consent, Clarity and Firebase Analytics stop collecting data and their cookies are deleted.
- The site shows no ads and uses no advertising cookies.
- Language choice is only which page you open (
/privacyor/pl/privacy).
16. Data controller
The data controller is ASSERT SOLUTIONS IT PIOTR DOBRZYŃSKI, ul. Ludwika Waryńskiego 2b-11, 26-610 Radom, Poland, trading as Smart Apps Factory.