Retro Ski Jumping Privacy Policy
INFINITY MOUNTAINS · RETRO SKI JUMPING
Update for iOS 1.0 (12). The iOS release numbered 12 uses one form for optional consent, Google Analytics for Firebase and a separate Apple tracking permission. Section 12 explains this release. The existing descriptions of Android and iOS 1.0 (9), including non-personalised ads only and the absence of Firebase or an ATT request, remain descriptions of those releases. Section 12 applies to the changed features in release 12. This update does not change game saves, purchases or Android rules.
1. Controller and contact
The controller of data processed by the publisher in connection with Retro Ski Jumping is TAXI HALNY WOJCIECH STACHOŃ TUTOŃ, ul. Stachonie 16a, 34-500 Zakopane, Poland, trading as Infinity Mountains. For privacy and data rights, contact infinitymountains25@gmail.com or the postal address above.
This policy covers only Retro Ski Jumping. The separate Odkrywaj Zakopane policy is unchanged. Google, Apple and Unity also determine the processing rules for the services they provide; their scope and the applicable platform are described below.
2. How saving works
The game uses Google Play Games profile sign-in. It does not create an additional Firebase account or an account in a separate publisher database. Progress is saved on the phone and, when signed in and connected, through Google’s Saved Games service. Saves include the chosen virtual athlete name, country and appearance, RC, purchase-processing history, equipment, XP, level, crates and reward counters, competitions, records and settings.
Offline progress waits for synchronisation. Conflicting device saves require reconciliation of available copies; their balances must not simply be added together. Choosing one version may omit changes from the other. Saved Games is not an independent server coin ledger or a safeguard against every modification of device data.
3. Data and purposes
| Area | Data | Purpose |
|---|---|---|
| Google Play Games | Player identifier, profile name and public profile data provided by the service, sign-in status, game save and its metadata such as update time. | Restoring the correct player’s progress and managing saves across devices. |
| Leaderboards | Player identifier, Play Games profile name, hill, score and position. PGS leaderboard data do not provide the player’s country to the game. | Competition on 13 hills; only competition records without falls, excluding training, are submitted. |
| Purchases | Product identifier, Google Play receipt and purchase token used for in-app checks, status and RC granted. Saved history contains a hashed transaction identifier instead of the full token. A hashed PGS profile identifier is also associated with the purchase. | Delivering packs, linking them to the correct player and limiting duplicate grants. This is not publisher-operated server-side transaction verification. |
| Unity IAP | Purchase initiation, completion, failure and fulfilment events, product and transaction identifiers, installation and session identifiers, game and engine version, technical device information, store country and diagnostics where available to the SDK. | Purchase operation and technical analytics of the payment system. Unity IAP 5.4.4 sends this information to Unity even when Google Play processes the payment. |
| AdMob | IP and its approximate area, permitted app or device identifiers, advertising events and diagnostics. | Non-personalised ad delivery, measurement and abuse prevention by Google’s service. |
| Ad rewards | SDK reward confirmation and the local pending crate state. | Opening a crate after in-app reward confirmation. No publisher-operated server-side verification (SSV) is used. |
| Choices and settings | Language, sound and graphics settings, accepted Terms version and acknowledgement of eligibility, privacy form choices. | Interface operation and respecting choices. The game does not collect dates of birth. |
| Publisher contact | Sender address, message contents and a player or order identifier provided voluntarily. | Support, complaints and data rights requests. |
The publisher does not receive Google passwords, card numbers or card security codes. The game does not request access to contacts, microphone, camera or precise GPS location. Google services may process technical connection data including IP; absence of location permission does not prevent deriving an approximate area from it.
4. Record visibility
Public leaderboards show the Play Games profile, distance and position. Your Google name may differ from your in-game name. Visibility also depends on Google profile privacy settings. We do not publish card data, email addresses or private save contents. Avoid including information you do not want public in your nickname.
The game checks jump eligibility locally. PGS accepting a result does not independently verify flight physics against the phone. Release 1.0 has no publisher-operated record verification server.
5. Legal bases
- Contract — GDPR Article 6(1)(b): selected game features, saves, leaderboards and delivery of purchases and rewards.
- Legal obligation — GDPR Article 6(1)(c): required accounting, complaints and data rights requests.
- Legitimate interests — GDPR Article 6(1)(f): answering enquiries, troubleshooting and protecting legal claims to the extent necessary.
- Consent — GDPR Article 6(1)(a) and applicable device-access law: optional advertising purposes and mechanisms where consent is required.
Accepting the Terms and acknowledging this policy do not replace separate consent for optional purposes. Missing information necessary for a selected service may prevent that service from working. This does not permit unrelated processing without a valid basis.
6. Advertising and privacy choices
Earlier advertising configuration. The following description of non-personalised ads only applies to the existing Android release and iOS 1.0 (9). Section 12 explains optional personalisation and the combined consent form in iOS 1.0 (12).
Release 1.0 uses non-personalised advertising only for all players, with restrictions suitable for teenage users as well. We do not collect dates of birth to enable personalisation. Advertising configuration includes Teen/PG restrictions, disabled personalisation and disabled publisher first-party identifiers.
Once privacy settings permit ad requests, the game may download an ad in advance so it is ready to display later. Advertising data may therefore be processed before you press the watch-ad button. Google User Messaging Platform (UMP) provides required privacy forms and settings to change choices when the form is available for the relevant profile and region. Refusing optional purposes does not block ordinary gameplay but may affect rewarded ad availability. Non-personalised ads can still process technical data and require consent for certain mechanisms. They do not mean no data are collected.
There is no third-party ad mediation or sending of events to a publisher SSV server. Crate opening uses the SDK’s in-app notification. The game does not build advertising interest profiles; Google may still analyse events for measurement and fraud prevention.
7. Recipients, transfers and security
Services include Google Play Games, Google Play Billing, AdMob, UMP and Unity IAP. Relevant disclosures include Google Privacy Policy, Unity Privacy Policy, Google Mobile Ads data, Play Games data and Unity IAP data. The following two sentences describe the existing Android release and iOS 1.0 (9): This release does not use Firebase, Crashlytics or a separate publisher account database. Having no separate publisher analytics module does not mean that SDKs collect no technical or analytics information. iOS 1.0 (12) additionally uses Google Analytics for Firebase as explained in section 12. It does not add a Firebase Authentication account or a publisher-operated career-save database.
Unity may act as a processor or a separate controller depending on the purpose and applicable service terms. The game disables optional Unity advertising and analytics purposes. This does not stop the baseline purchase events sent by this Unity IAP version. We do not use Unity direct-to-consumer payments, Unity Webshop or a Unity email form.
Recipients may also include website hosting and email providers, authorised complaint or accounting personnel and legally entitled authorities. Other players can view public leaderboard information. The publisher does not sell personal data.
Google and Unity may process data outside the EEA using safeguards described in their documents, including relevant adequacy decisions or standard contractual clauses. The publisher does not select a separate Saved Games database region. Contact us for details about safeguards for data held by the publisher.
Service connections should be encrypted and access to progress associated with the correct player profile. Do not share passwords or sign-in codes. We do not guarantee that local saves resist every modification or that data loss can never occur.
8. Retention and deletion
Local data remain on the phone until deleted or replaced. Saved Games progress and PGS scores remain linked to the Google profile until removed through the appropriate game feature or Google’s tools. Deleting a save alone does not remove leaderboard scores. Uninstalling does not delete cloud data, and another device retaining a save may upload progress again when launched.
The feature in game settings clears the career associated with the current profile: first the Google save and, after confirmation, the local save and supporting copies for that profile. It does not automatically delete PGS leaderboard scores or other accounts on the device. Recovery copies with an unidentifiable owner and damaged copies are not deleted automatically; they remain until the whole application data are cleared in Android settings. Clearing application data also removes local data for other profiles. To remove other PGS data for this game, use Play Games profile settings and select Retro Ski Jumping under individual-game data deletion. See Google instructions and our data deletion page.
This does not delete your whole Google account, payment history or any Google Web & App Activity. Google determines its own service retention and deletion periods; the publisher does not promise an unverified deadline for removal of Google’s technical copies.
Correspondence is kept while a case is handled, and afterwards only where necessary for a legal obligation or establishing, exercising or defending claims, until the relevant periods expire. Accounting documents held by the publisher are retained for the period required by applicable tax and accounting rules. We do not retain additional copies merely because they could be kept. You may request erasure by email; we will explain any applicable exceptions.
Clearing a career or Play Games data does not automatically erase separate Google advertising and technical data or Unity purchase data. Those providers apply their retention and rights procedures. Contact us about data processed on our behalf, or the provider through its privacy policy for separate processing.
9. Rights and complaints
Subject to GDPR conditions, you may access, correct or erase data, restrict processing, request portability, object and withdraw consent. Withdrawal applies prospectively. Exercise rights against the publisher through our contact details and manage Google profile data through Google’s services as well.
If identity is reasonably in doubt, we may request proportionate verification. Do not send passwords, sign-in codes or identity document scans. We normally respond within one month; any legally permitted extension requires an explanation. You may complain to Poland’s Personal Data Protection Office, uodo.gov.pl, or the relevant authority in your country.
10. Age, website and updates
The intended audience is aged 16 and over, subject to higher local requirements and the actual store rating. The game is not directed at children under 16. A guardian who believes a person below the required age supplied data may contact the publisher.
Opening the website in a browser provides it with information needed to deliver the page, including IP and request details. Any analytics or cookies on the hosted site need appropriate disclosure. The prepared HTML files themselves contain no tracking tools or external scripts.
Changes to features or providers may require policy updates and notice of material changes. Introducing a publisher-operated server in the future would require separate review of its data scope; this document does not describe one as currently operational.
11. iOS — Game Center, iCloud and App Store
Player identity and career saves
The game identifies the online profile using Game Center. It does not ask for your Apple Account password. A local career can be used offline; cloud saving requires a connection, an available Game Center profile and iCloud. To use the same career on another Apple device, use the same Game Center profile and iCloud account. Check which Apple service accounts are in use before making purchases.
The career contains the virtual athlete’s name, country and appearance, XP, equipment, Retro Coins, competitions, crates, records, settings and reward/purchase delivery history. It is saved on the device and, once services are enabled and synchronization is confirmed, in iCloud through GameKit. The save includes a career profile identifier, a pseudonymous owner identifier, dates and technical revision information. A hashed identifier still links data to a player; it is not anonymous.
If saves conflict, we retain local recovery copies of the available versions and ask you to select a complete career. Balances from different devices are not added together. A save that would omit known delivered purchases may require support before synchronization can continue. Being offline or seeing a pending synchronization message does not confirm that your data has reached iCloud.
Apple services and Unity IAP data
| Feature | Data and purpose |
|---|---|
| Game Center | Player identifier, profile name, authentication state and short-lived authentication proof. They identify the correct career and enable online features. |
| Game Center records | For enabled leaderboards: player identifier and public name, leaderboard/hill identifier, best distance and rank. The game submits your personal best and retrieves leaderboard pages containing other players’ public scores to display the records hall. Record submission and retrieval are separate from career saving. Private career contents and RC balances are not published in the table. |
| App Store | Product and transaction identifiers, Apple’s purchase confirmation, delivery state and a pseudonymous token associating the purchase with the career. The full transaction identifier is used to check a purchase; the durable career save contains its hash and the delivered pack. We do not receive your card number or Apple password. |
| Unity IAP | The SDK handles store connections and purchase events. Technical data includes installation/session identifiers, device and country information and an available player identifier. SDK behavior also determines the scope; disabling optional analytics does not mean Unity processes no data. Unity IAP privacy information. |
Your public Game Center nickname and score may be visible to other users. Your Game Center name may differ from the athlete name in the game. See Game Center & Privacy for Apple’s processing and sharing settings. The game does not retrieve your friends or contacts to operate its own social network.
We retain a device-side queue of pending and confirmed personal records associated with the correct profile. This allows uploads to retry after a connection interruption and preserves the best score. Retrieved leaderboard pages are temporarily cached in memory to limit requests, so the displayed table may need refreshing.
Retention, deletion and contact
Deleting the career in the game writes an empty revision marking deletion to iCloud, then clears the current device’s career after confirmation. This empty revision remains associated with the profile to prevent an old save automatically restoring deleted progress. This is not physical deletion of every technical copy held by Apple.
The button does not delete your Apple Account, Game Center scores, App Store purchase history, separate SDK data or other profiles’ data. Copies on other devices may remain; the game requires a conflict decision before knowingly restoring them. A single operation cannot remotely wipe every phone. Unidentified or damaged recovery copies may require separately removing the app’s local data.
Contact the publisher about data we handle. Never send passwords or sign-in codes. Requests concerning Apple’s service data can also be made through Apple’s Data and Privacy service. The rights, processing grounds and complaint procedures in the complete policy continue to apply; we do not promise a single physical deletion deadline for every provider’s copies.
Advertising on iOS
Historical scope: iOS 1.0 (9). The following description of disabled personalisation and no ATT request applies to release 9. Section 12 explains the changes in iOS 1.0 (12), including the separate ATT permission.
The iOS ad configuration disables personalization and the publisher first-party identifier, and applies content restrictions appropriate for teenagers (Teen/PG settings). This release does not display the system ATT request for access to the IDFA advertising identifier; ads are configured to work without it. This does not mean the SDK processes no other identifiers or technical data. UMP privacy choices are handled separately from the system ATT permission.
The iOS release’s ads are supplied by Google AdMob using configuration for that platform. The SDK may process IP addresses, approximate location, available device/app identifiers, advertising events and diagnostics. Non-personalized ads do not mean no data is processed. See Google Mobile Ads data on iOS.
Once ads are enabled, the privacy form is displayed according to the region and service configuration, and options to change choices are available in game settings when required by the consent service. Declining optional purposes does not prevent ordinary gameplay. Rewarded ad availability depends on proper handling of choices and available ad inventory. Banners appear in hill history; an ad is not guaranteed every time a panel opens.
A rewarded ad allows you to open an earned crate. The game records reward delivery in the correct career’s history to avoid granting the same reward repeatedly. Closing an ad or encountering an error without the ad service confirming the reward is not sufficient to grant it.
Providers, legal bases and platform scope
On iOS, Apple provides identity and save services (Game Center and iCloud), App Store processes payments, and the game also uses Unity IAP and — once ads are enabled in the particular release — AdMob and UMP. Apple describes its own processing, recipients, transfers and retention in the Apple Privacy Policy. Google Play Games and Google Play Billing rules above concern Android, not iOS saves or purchases. Game Center data and the career save are not sent to Google Play Games.
The common controller details, processing grounds in section 5, correspondence rules, rights and complaints in section 9, and age and website information also apply to iOS. iOS progress, equipment, purchases and Retro Coins remain separate from Android. The production edition described here does not use shared Android–iOS leaderboards through Unity Authentication and Leaderboards; Unity IAP is a separate purchase service.
12. Optional analytics, advertising and privacy choices in iOS 1.0 (12)
Scope
This section applies to Retro Ski Jumping 1.0 (12) on iOS. It supplements this policy’s shared information about the controller, contact details, recipients, rights and international transfers. It does not change Android rules or the historical description of iOS 1.0 (9). Game Center, private iCloud saves and App Store payments remain Apple services described in section 11. We do not create a Firebase Authentication account or move your career into a Firebase database.
One form for optional choices
After accepting the Terms and starting the game, the Google User Messaging Platform form lets you accept all optional purposes, reject them or review the available purposes in Google’s form settings. It covers analytics and choices about storing and using data for advertising, advertising measurement and personalisation. Accepting the Terms or simply opening the game does not consent to these purposes. You can play without optional analytics and without allowing tracking. Rewarded ad availability also depends on your choices, connectivity and available ads.
Game analytics
If you allow analytics, Google Analytics for Firebase receives events about sessions, screens and help pages used, jumps and competitions, the selected hill, progress, virtual currency, the shop and the success or failure of selected features. Events contain limited details such as distance, level, action type, duration, product identifier and result code. The SDK may process an app-instance identifier, device and session information and a general location derived from IP. We use this to understand how the game works, which features are used and technical problems.
Our custom Firebase events do not include your player name, email address, phone number, Game Center identity or full career save. We do not use advertising matching based on an email address or phone number you provide. Choosing an advertising-data purpose alone does not enable Firebase analytics.
Purchases and revenue
With analytics consent, we may measure confirmed App Store purchases, including the product, value, currency and transaction information, and advertising revenue through the AdMob–Analytics link. The game’s own measurement route reports confirmed production transactions; it does not count Sandbox tests or a restored Retro Coin balance as new revenue. We do not receive your payment-card number or Apple password. Necessary payment handling, purchase delivery and Unity IAP technical data are separate from optional analytics and are described earlier in this policy.
Advertising, measurement and Apple permission
Google AdMob may use the data described in this policy to deliver ads, measure their performance and prevent abuse. With separate consent to the relevant advertising purposes and Apple’s ATT permission, the game may allow personalised ads and use of the advertising identifier. Google may then link data with information from other companies’ apps and websites to select ads and measure results. Apple’s system ATT request is separate from the Google form. Consent in the form does not replace ATT; a previous Apple decision or system restriction may mean the system does not ask again.
Teen/PG content restrictions and disabling the publisher first-party identifier remain in place. Non-personalised ads can also process IP, permitted identifiers, advertising events and diagnostics. The privacy form needs its own technical data to function. Declining optional analytics does not disable data necessary for selected Apple services, purchases, the consent form or permitted ad delivery. An ad may be downloaded in advance only after privacy choices permit the relevant advertising route.
Google Analytics is currently used for reporting. We have disabled Google Signals, the “Google products & services” data-sharing setting and use of this property’s data for ads personalisation in all regions. AdMob’s ability to personalise ads after consent is separate from those Analytics restrictions. Including an on-device conversion measurement library in the app does not itself mean that an advertising campaign is active.
Changing your choices and connectivity errors
Open Settings → Account and save → Consent and privacy to reopen the form. You can change Apple’s permission in iOS privacy settings; the game also provides a button opening Apple settings. Opening the choice-management flow suspends the game’s use of previous optional permissions. If the form cannot load or an error occurs, you can retry or choose to play without optional consent. This refusal is saved for subsequent launches; regaining internet access does not turn consent back on.
Withdrawing analytics consent stops future optional analytics in the game, clears its pending events and resets its local identifier. It does not automatically erase information already received by providers, payment history or Apple saves. Refusal may limit or disable ads, including rewarded ads. Section 9 explains your data rights and how to contact us.
Retention and providers
Our Google Analytics property uses two-month retention for user and event data, with no extension through new activity. This is not a common deletion deadline for all aggregate reports, advertising or purchase data, or Apple and Unity data. Each service’s rules also apply. Consent is the basis for the additional optional purposes in this section; you can withdraw it without losing ordinary gameplay. Section 5 continues to describe the other bases for selected services, accounting and player rights.
Further information: Google Privacy Policy — https://policies.google.com/privacy?hl=en ; Privacy and Security in Firebase — https://firebase.google.com/support/privacy ; Google Mobile Ads data on iOS — https://developers.google.com/admob/ios/privacy/data-disclosure ; Apple Privacy Policy — https://www.apple.com/legal/privacy/en-ww/ ; Unity IAP data — https://docs.unity.com/en-us/iap/privacy-and-consent/overview .
Document address: https://infinitymountains.pl/index.php/retro-ski-jumping/privacy-policy/.