Privacy Policy

This policy explains what personal data Grand Pike AB collects and uses when you play Factory 73 (the "Game"), why, on what legal basis, how long we keep it, and what rights you have. We have tried to write it in plain language. If something is unclear, write to us at support@grandpike.com.

1. Who is responsible

The controller of your personal data is Grand Pike AB, a company registered in Sweden, organisation number 559066-4131 ("Grand Pike", "we", "us").

Contact for all questions and data requests: support@grandpike.com. Please put "Privacy" in the subject line.

2. What this policy covers

The Factory 73 mobile app (Android now, iOS planned) and the website at survivor-robot-factory.web.app, including the campaign links under /go/. Stores such as Google Play and the Apple App Store, and Google as the provider of your Google account, have their own privacy policies for what they do with your data.

3. What we collect and why

We collect only what the Game needs to work. On Android the Game uses internet access and, if you allow it, notifications (Android 13 and later). The app also carries the permission to read the Android advertising id, which Google Play shows as "Ads" (it is used for install measurement and for advertising only if you agree, see 3.5, 3.12 and 3.15), and the standard permissions for network state, billing and the Google Play install referrer. It does not use your location (a rough country is worked out from your IP address and your phone's time zone and language), contacts, camera, microphone or files, and it does not see your payment card details.

When you first open the Game it asks for your birth year and then shows two choices: crash reports (on, with an off switch) and analytics (which also covers install measurement for adults). Neither starts before you have answered. See 3.5, 3.13 and section 9.

3.1 Your account

To keep your progress safe we use Firebase Authentication (a Google service). You can play as a guest, which creates a guest account that is identified only by a random player id and holds nothing else. Or you can sign in with Google Play Games (on Android) or with Google, or with an email address and a password. When you sign in with Google or Google Play Games, we receive from Google your Google account id and, as Google provides them, your name, email address and profile picture link. Firebase also records when the account was created and when you last signed in. We use your name for the leaderboards (see 3.3) and show your email address to you on the account screen. We do not use your profile picture. When the iOS version is released you will also be able to sign in with Apple, and we will then receive the id, and the name and email address (or Apple's private relay address) that you choose to share. If you choose email and password, we receive your email address and the password you pick. The password is stored only by Firebase Authentication (Google), in hashed form; we never see it or store it ourselves, and it is not in our database or logs. We use your email address to let you sign in, to send you a verification email when you create the account, and to send you a password reset email when you ask for one. Verifying the email address is not required to play. We send no other email to this address.

Playing on CrazyGames. If you play Factory 73 on the CrazyGames website and choose "Login with CrazyGames", we store your CrazyGames user id, linked to your game account. We use it only to recognise you, so that your progress follows you across devices and browsers. If you do not log in, you play as a guest with a guest account, as described above.

Legal basis: contract (Article 6(1)(b) GDPR), to give you an account and your save. Kept: until you delete your account.

3.2 Cloud save and wallet

The Game saves your progress on your device and, when you are online, a copy in the cloud (Cloud Firestore, Google, in the European region europe-west1, Belgium). The cloud save holds your game progress: parts and items, materials, factory and tier progress, and tutorial flags. A separate record, which only our servers can change, holds your Cogs balance, your Factory Membership and Remove Ads status, purchases waiting to be delivered, and the limits of the daily shop. Both are tied to your player id. This lets you keep your game when you change phone and lets us deliver what you bought.

Legal basis: contract (6(1)(b)). Kept: until you delete your account, see section 7.

3.3 Leaderboards and your player name

When you finish a run, the Game sends its result (tier, kills, time, whether it was cleared, score) to our servers, which check that it is plausible and update the leaderboards. Other players can see on a leaderboard your leaderboard name, your result, and a technical player id.

By default the leaderboard name is a generated name such as "Rusty Bolt 482", the same every time for your account and not related to your real name. If you are 18 or older you can choose in Settings, Privacy choices, Leaderboard name, to show the name of your account (the name Google or Apple gives us, if it is a plain name and not an email address or a link) or a custom name of 3 to 16 letters, digits, spaces, "_" or "-". Names pass a profanity filter, in the Game and again on our servers; a name that does not pass is replaced by the generated name. Players under 18, and players whose age we do not know, always use a generated name. We never show your email address or picture. When you change your choice, your name on the boards is updated the next time you finish a run. We also keep a small counter per player to limit how often results can be sent, which protects the boards against abuse.

We may remove or replace names that break the rules of our EULA.

Legal basis: contract (6(1)(b)) as leaderboards are part of the Game; consent (6(1)(a)) for showing your account name or a custom name, which you give by choosing it and withdraw by switching back; and our legitimate interest in fair play and preventing abuse (6(1)(f)). Kept: all-time boards until you delete your account; weekly boards are removed about four weeks after the week ends.

3.4 Purchases

Purchases are made through Google Play (and, on iOS, the App Store), which handle your payment. We do not receive your card or bank details. To buy anything with real money in the Game you must first link an account (Google, Google Play Games, Apple or email) instead of playing as a guest, so that what you buy stays with you if you change phone. A payment that was made earlier, for example as a guest, is always honoured and delivered. When you buy something, the Game sends the store's purchase token to our servers, which check it with Google Play and then add what you bought to your account. We store a purchase record: the product, the store's order and purchase token, the time, the status (for example refunded or, for the Membership, active, cancelled or expired) and your player id. We learn about renewals and refunds from notifications from the store.

Legal basis: contract (6(1)(b)) to deliver what you bought and to restore it; legal obligation (6(1)(c)) for bookkeeping records; legitimate interest (6(1)(f)) in preventing fraud. Kept: purchase records for seven years, as Swedish bookkeeping law requires, see section 7.

3.5 Analytics

If analytics is on, we use Google Analytics for Firebase to learn how the Game is played and where it can be improved. It collects a random app instance id on your device, the device model and operating system version, the app version, language, approximate location (country or region, worked out from your IP address; the IP address itself is not stored by Google Analytics), and when and how often you use the Game. It also collects game events such as starting and ending a run (with tier, length, result and how strong your gear was against the gate), tutorial and progress milestones, opening screens and shop pages, spending and earning Cogs, offers shown, purchases (product, price, store order id), whether an ad was available and watched, and changes to settings.

The events carry no name or email address. To recognise the same player after a reinstall or on a new phone, and to tie analytics to the right account for deletion requests, we also set a pseudonymous player id in Analytics: it is computed on our server from your player id with a secret key (a keyed hash), so Google and AppsFlyer cannot work back to your account from it and we can no longer compute it once your account is deleted. It is sent only while analytics is allowed. We do not send your Firebase player id, name or email. Pseudonymous data is still personal data, and this policy treats it that way.

We have switched off Google signals and the use of the Android advertising id by Analytics in the app. If you came to the Game through a campaign link, the Google Play install referrer tells Analytics which campaign (source, medium, campaign name) the install came from, so that we can see which of our posts and ads work.

You choose. In the EEA, the UK and Switzerland, and wherever we cannot tell where you are, analytics is off until you allow it: the first screen asks with "Allow analytics" and "No thanks", and if you are 13 to 15 in those regions it is off and cannot be turned on. Everywhere else, if you are 13 or older (teenagers too), the first screen shows analytics already on, with a notice and an off switch. For teenagers analytics never includes advertising identifiers, personalised ads or, unless you switch analytics on yourself, install measurement (3.15). You can change it at any time: open the menu, then Settings, then Privacy choices (analytics and crash reports are two separate switches). When you switch analytics off nothing more is sent from the analytics group, the analytics identifiers on your device are reset, and events waiting on the device are deleted. Data already collected stays until its retention period ends (below) unless you ask us to delete it. Uninstalling the Game also stops it.

If you say no in the EEA, the UK or Switzerland (and you are 16 or older), the Game still starts Google's Analytics SDK in consent mode with analytics_storage, ad_storage, ad_user_data and ad_personalization all denied. Then only cookieless pings are sent: a handful of counts without any identifier, namely that a run started or ended, that a gate was cleared or a tier unlocked, plus what the SDK itself adds to every ping (the time, the app version, the device's operating system and language, and the IP address of the connection, which Google uses to work out a country and does not store in Analytics). They carry no app instance id, no advertising id, no player id or pseudonymous id and no user property, nothing is written to your device for them, and Google uses them to estimate totals. Nothing is sent when you are 13 to 15 in these regions, and outside these regions a "no" stops everything in this group.

We also count how many players choose what on the first screen (analytics yes or no, ads yes or no, a region class of EEA/UK/CH or other, an age group of 13 to 17 or 18 and over). This counter is sent without any identifier and holds no personal data. We count in the same way how many times that first screen was shown, so that we can see how many players leave without answering.

Anonymous statistics from your progress. The data we keep to run the Game (your account, when you were last here, your save and progress, and purchases) is also used for anonymous, aggregate statistics: how many players are new or active each day, how far new players get, how many come back, and sales totals. Only totals are produced, they hold no player or purchase identifier and are not combined with analytics or install-measurement data, and they are counted whatever you chose on the first screen.

Legal basis: in the EEA, the UK and Switzerland consent (6(1)(a)), given on the data screen or in Settings and withdrawn there; elsewhere the analytics default is on with a notice and an off switch, and we treat the choice the same way (consent, withdrawn at any time). The cookieless pings after a "no" and the anonymous counter of choices rest on our legitimate interest (6(1)(f)) in counting how many players play, because they identify nobody; you may object (section 8). The anonymous statistics from your progress rest on our legitimate interest (6(1)(f)) in understanding and improving the Game and its sales; they are made from data we already keep to run the Game and identify nobody. Kept: no longer than 14 months; the anonymous statistics hold no personal data.

3.6 Game settings from the server (Remote Config)

The Game fetches settings such as balance values and event details from Firebase Remote Config, so we can tune the Game without an update. For this Google receives the request from your device, which includes a Firebase installation id, the app and OS version and your IP address. The settings are cached on your device.

Legal basis: contract (6(1)(b)) and legitimate interest (6(1)(f)) in running the Game. Kept: the installation id for as long as the app stays installed; Google deletes it after the app has been inactive for a long period.

3.7 Server logs and security

Our servers (Cloud Functions, europe-west1) write logs when they handle purchases, notifications and errors. They can contain your player id, product ids, store purchase ids and error messages, and Google's infrastructure records IP addresses and request times. We use them to find and fix faults and to investigate fraud and abuse.

Legal basis: legitimate interest (6(1)(f)) in security and reliability. Kept: about 30 days (Google Cloud's default for logs).

To keep out copies of the Game that are not the genuine app, and scripts that imitate it, the Game uses Firebase App Check. On Android it works with Google Play Integrity: Google checks that the app is the genuine Game, installed from Google Play and running on a genuine device, and sends our servers a token that says so. For this your device sends device and app integrity signals to Google. We use the result only to protect our servers from fraud and abuse.

3.8 Internal alerts

When a purchase, a refund or a Membership change happens, our servers post a short message to a private Slack channel that only Grand Pike staff can read. It contains the product, the store, the time, and a short pseudonymous tag derived from your player id (it is not the player id itself), with a link to the record in our admin console. We use it to follow sales and to spot problems quickly.

Legal basis: legitimate interest (6(1)(f)) in running and monitoring the service. Kept: following the retention settings of our Slack workspace, no longer than 12 months.

3.9 When you contact us

If you email us we process your email address, the content of your message and our reply to answer you and to document how we handled your request. For a request about your data we may ask for your player id or other information to check that the data is yours.

Legal basis: legitimate interest (6(1)(f)) in answering you and, for data requests, legal obligation (6(1)(c)). Kept: up to 24 months after the matter is closed.

3.10 The website

The website is a simple static page hosted by Google (Firebase Hosting). Google's servers log your IP address and request details when you load a page. We set no cookies and run no analytics or advertising scripts on the website. The campaign links (/go/) only redirect you to the right store page and pass the campaign name on to Google Play.

3.11 On your device

The Game stores your save, settings, your birth year and privacy choices (analytics and crash reports, ad choices, your leaderboard name choice) and cached data in your device's app storage. The birth year stays on your device and is not sent to us. This stays on your device and is removed when you uninstall the Game. The Android backup of app data is switched off, so none of this is copied to your Google account backup.

3.12 Advertising

The Game shows advertisements. You can choose to watch a rewarded video ad to get a reward (rewarded ads are always optional), and the Game may also show an ad between runs. Ads are served by Unity LevelPlay (ironSource), an ad mediation service, together with Google AdMob and the other ad networks listed in section 5, which bid to show you an ad.

To show an ad and give you the reward, we pass LevelPlay your player id as the user id, and LevelPlay and the ad networks process your IP address, device and advertising identifiers (such as the Android advertising id), device and app information, and how you interact with ads. Our servers receive a signed callback from LevelPlay with the player id and the reward when you finish an ad. We also receive ad revenue figures per impression.

Consent for ads. In the EEA, the UK and Switzerland Google's consent message (a certified consent tool) asks you before any ad is requested; ads are personalised only if you agree to the purposes that need it. Elsewhere ads are personalised unless you opt out with Do not sell or share in Settings, Privacy choices (section 10). If you are under 18, or we do not know your age, ads are never personalised and child-directed treatment flags are set on the ad SDK. You can change your choices at any time in Settings, Privacy choices, and on Android in your device's Google settings (Ads). On iOS the system asks you to allow tracking only when ads or install measurement start, never at launch. Remove Ads (where offered), the Factory Membership and the season pass reduce the ads you see; rewarded ads stay optional.

Legal basis: consent (6(1)(a)) for personalised advertising and for reading or storing identifiers on your device; contract (6(1)(b)) for delivering the reward; legitimate interest (6(1)(f)) in showing non-personalised ads that fund the Game, where the law allows it.

3.13 Crash reports

We use Firebase Crashlytics to find out when and why the Game crashes or hits an error, so that we can fix it. When the Game crashes, or the code of the Game reports an error, Crashlytics collects the crash stack trace (which parts of the program were running), the device model and operating system version, the app version, and a random installation id that Firebase makes for the app on your device. We add a few technical notes: the build, the graphics level, which screen the Game was on, the tier of the run you were in and a short list of recent steps (such as opening a screen or starting a run). Reports contain no name, email address, player id or saved game, and we do not link them to your account or to the pseudonymous analytics id.

You choose. Crash reports are on by default for everyone aged 13 or older, in every region, and they are not part of analytics: they have their own switch, shown on the first screen and in the menu, then Settings, then Privacy choices. When you switch it off, collection stops and reports waiting on your device are deleted. We only use crash reports to find and fix bugs, never for advertising or marketing. Uninstalling the Game also stops it. Crash reports are only collected in the mobile app, not on the website.

Legal basis: legitimate interest (6(1)(f)) in keeping the Game stable and fixing bugs; the data is pseudonymous and limited to what is listed above. You may object at any time with the Crash reports switch (section 8). Kept: Crashlytics keeps crash data for 90 days, then deletes it automatically.

3.14 Push notifications

In the mobile app, if you allow notifications (the phone asks once, after you have claimed your first daily chest), the Game can remind you of things on the phone itself (a finished research decode, the daily chest) and, if you have not opened the Game for a few days, our server can send you a short message through Firebase Cloud Messaging (Google). For this we store a push token (a random identifier Google makes for the Game on your phone; the Game asks Google for it only after you allow notifications, and we store it only then), your player id, the platform and app version, your time zone offset (so we do not send anything between 22:00 and 08:00 your time), the time the Game was last opened, and whether you have the scavenger bot and the Dispatch mast (to pick the message). We send at most one message every two days and stop after three messages in one absence.

You can turn this off. Open the menu, then Settings, then switch Notifications to Off: we mark you as opted out and delete the token, and signing out does the same on that phone. You can also withdraw the permission in the phone's settings. Deleting your account deletes this data. Push messages are only sent in the mobile app, not on the website.

Legal basis: consent, 6(1)(a), given by allowing notifications and withdrawn by switching them off. Kept: until you switch notifications off, sign out or delete your account; a token that Google reports as no longer valid is deleted at once.

3.15 Install measurement (AppsFlyer)

If you are 18 or older and analytics is on, or you are 13 to 17 and switched analytics on yourself (3.5), the Game also uses AppsFlyer (a mobile attribution service) to learn which advertisement or link brought you to the Game, so that we can measure and improve our marketing. AppsFlyer receives a random AppsFlyer id, the install time, your IP address, device and app information (model, operating system, language, app version), the Android advertising id (on iOS the advertising identifier only if you allow tracking; for players under 18 advertising identifiers are switched off), the same pseudonymous player id as in 3.5, and a few game events: finishing the tutorial, reaching a new tier, linking an account, purchases (product, amount, currency and store order id, sent only after our server has confirmed the purchase), the revenue of ads you watch (only if you have agreed to personalised ads), and whether you came back on day 1, 3 and 7. The ad partner whose ad brought you may receive the fact of the install and a few of these events; with "Do not sell or share" switched on (section 10) no partner receives anything. AppsFlyer does not start before you have answered the first screen, does not start for a teenager who only left the default alone, and stops when you switch analytics off.

Legal basis: consent (6(1)(a)), the Analytics switch. Kept: see section 7.

4. Legal bases at a glance

Where we rely on legitimate interests we have weighed them against your interests and rights. You may object at any time, see section 8.

5. Who receives your data

We do not sell your personal data. We share it only with:

• Google (Google Ireland Limited and Google LLC), as our processor for Firebase Authentication, Cloud Firestore, Cloud Functions, Remote Config, Google Analytics for Firebase, Firebase Crashlytics and Firebase Hosting, and as the operator of Google Play (billing, install referrer, Play Games), which acts as an independent controller for its own purposes.
• Slack (Slack Technologies, a Salesforce company), as our processor for the internal alerts in 3.8.
• AppsFlyer, as our processor for install measurement (3.15), only while analytics is on for you and, if you are under 18, you switched it on yourself. The ad partner that brought you to the Game can receive install and event information through AppsFlyer, unless you use "Do not sell or share".
• Unity LevelPlay (ironSource), the ad mediation service that requests and delivers ads (3.12) (privacy policy), and the ad networks in its mediation that can show you an ad, each an independent controller for its own purposes: Google AdMob (policy), AppLovin (policy), Meta Audience Network (policy), Unity Ads (policy) and Vungle (Liftoff) (policy). They receive your IP address, device and advertising identifiers, device and app information and your ad interactions. Which of them serves an ad is decided at the moment of the request, and ads from other networks added to the LevelPlay mediation later may also appear; we list the networks here and update this list when it changes. Each network's privacy policy explains what it does with the data.
• Other players, who see your display name and results on the leaderboards.
• Apple, as the operator of the App Store and Sign in with Apple, once the iOS version is released.
• Authorities, courts and advisers when the law requires it or when we need to establish, exercise or defend legal claims, and our accountants and auditors for bookkeeping.
• A buyer, if Grand Pike or the Game is sold or merged. The buyer must follow this policy or tell you of changes.

6. Transfers outside the EEA

Your cloud save, wallet and our server functions are located in the EU (Belgium). Some Google services, for example Firebase Authentication, Analytics, Crashlytics, Remote Config and the logs of Google's infrastructure, are run on Google's global systems, so data can be processed in the United States and other countries outside the EEA. Slack's servers may also be outside the EEA.

Where this happens we rely on the European Commission's adequacy decision for the EU-US Data Privacy Framework (Google LLC and Salesforce, Inc. are certified under it), and otherwise on the Commission's Standard Contractual Clauses, which are part of Google's and Slack's data processing terms, together with their security measures. AppsFlyer processes data in the EU, the United States and Israel (the Commission has found Israel adequate) under its data processing agreement with AppsFlyer Ltd. (Israel), which forms part of AppsFlyer's terms with us. You can ask us for a copy of the safeguards (see section 1).

7. How long we keep your data

Backups and deletion queues may keep data for a short time after deletion, normally no more than 30 days.

8. Your rights

Under the GDPR you have the right to:

• get access to your data and a copy of it, free of charge;
• have wrong data corrected;
• have your data erased;
• restrict how we use your data in some cases;
• receive the data you gave us in a commonly used, machine-readable format (portability);
• object to processing that is based on legitimate interests (for crash reports, switch off Crash reports in Menu, Settings, Privacy choices; for the rest email us);
• withdraw a consent you have given, at any time, without affecting what was done before. In the Game: Menu, Settings, Privacy choices (analytics, which includes install measurement, and, separately, crash reports; Ad choices and Do not sell or share when ads exist; your leaderboard name).

To use these rights email support@grandpike.com. Because guests have no email address, include the Player ID shown in the Game (Menu, then Account), and for a Google or email account write from the email address of that account, so that we can find your data and make sure it is yours. We may ask for more information to confirm who you are. We answer within one month; if your request is complex we may extend this by up to two further months and will tell you why.

Deleting your account: you can delete your account and data yourself in the Game or by email. See how to delete your account.

Complaints: you have the right to complain to the supervisory authority. In Sweden this is the Integritetsskyddsmyndigheten (IMY), Box 8114, 104 20 Stockholm, www.imy.se, imy@imy.se. You can also complain to the authority in the EU country where you live or work. We would be glad if you contact us first so that we can try to fix the problem.

You do not have to give us any personal data, but without an account (guest, Google, Play Games, Apple or email) the Game cannot save your progress in the cloud, and without the purchase data we cannot deliver or restore purchases.

9. Children and teenagers

Factory 73 is for players 13 and older, and we do not knowingly collect personal data from children under 13. When you first open the Game it asks for your birth year, with no explanation, and does not let you in if it shows you are under 13: nothing is started on that device (no account, save, analytics or purchases) until the app data is cleared. In some countries the age at which a person can consent to the processing of their data online is higher (up to 16 in the EU); in the EEA, the UK and Switzerland analytics is therefore locked off for 13 to 15 year olds (crash reports, which rest on our legitimate interest in fixing bugs and are never used for advertising, stay on with an off switch).

For players aged 13 to 17 we keep the data to a minimum: crash reports are on (with an off switch); analytics is on by default outside the EEA, UK and Switzerland with a notice and an off switch, and opt-in inside them from 16 (locked off for 13 to 15); install measurement starts only if you switch analytics on yourself; ads are never personalised; your leaderboard name is always a generated name; and no advertising identifier goes to AppsFlyer or Analytics. We use the birth year only to apply these rules; it stays on your device.

If you are a parent or guardian and believe that your child has given us personal data, email support@grandpike.com and we will delete it. In the Game, purchases by someone under 18 need the permission of a parent or guardian, see the EULA.

10. US state privacy rights (California and others)

If you live in California, Colorado, Connecticut, Virginia, Texas or another US state with a privacy law, you have the rights to know what personal information we collect and use, to access and correct it, to delete it, to opt out of its "sale" or "sharing", and not to be treated worse for using these rights. We do not sell personal information for money.

Categories we collect, as in section 3: identifiers (player id, device and advertising ids), commercial information (purchases), internet or app activity (events), approximate location (from IP address), device information, and, only if you choose to show it, your account name. We collect them to run the Game, for security, and, while the switches are on, analytics, crash reports and install measurement. We keep them as described in section 7. We do not collect sensitive personal information to infer characteristics about you.

Sale or sharing. The Game shows ads. Where ad networks receive your advertising identifier and ad interactions, or an ad partner receives install or event information through AppsFlyer, this can count as "sharing" for cross-context behavioural advertising or a "sale" under some state laws. You can opt out at any time with the Do not sell or share switch in Settings, Privacy choices (it appears where it applies): with it on, no ad partner receives install or event information through AppsFlyer, ads are not personalised. We do not knowingly sell or share the personal information of anyone under 16, and players under 18 never get personalised ads.

How to use your rights: use the switch above, delete your account in the Game (how), or email support@grandpike.com with "Privacy" in the subject. We answer within 45 days (extendable once by 45 days). An authorised agent may write for you; we may ask for your player id to verify the request. If we deny a request you can appeal by replying to our answer.

11. Security

Data is encrypted in transit (HTTPS). The cloud save can be read and changed only by the signed-in owner; the wallet, purchase records and leaderboards can be changed only by our servers. Access to our admin consoles is limited to staff. No system is perfectly secure, and we cannot guarantee that data sent over the internet cannot be intercepted. If a personal data breach is likely to put you at risk we will tell you and the authority as the law requires.

We do not make decisions about you that have legal or similarly significant effects by automated means. Our servers check automatically that submitted results and purchases are valid, and reject those that are not.

12. Changes to this policy

We may update this policy, for example when the Game gets new features such as an iOS version. The date at the top shows the latest version. For important changes we will tell you in the Game or on this page before they take effect, and ask for your consent where the law requires it.

13. Contact

Grand Pike AB, organisation number 559066-4131, Sweden
Email: support@grandpike.com