Castaway Life
Privacy notice.

This notice covers Castaway Life from LazyShoreGames, available for iOS and Android. It explains game data, advertising, usage statistics, crash reporting and support. Visiting this page is covered by our website privacy notice.

Who is responsible?

For game support, contact support@lazyshoregames.com.

The startup agreement

The startup prompt in version 2.0.0 links the Terms of Use & EULA and this notice and explicitly names gameplay analytics and crash reporting. Choosing “Accept & continue” accepts the EULA and the described data collection together. Firebase Analytics and Firebase Crashlytics are then enabled, subject to technical availability. Choosing “Do not accept” blocks the game from starting; you can return to the agreement or close the app.

Version 2.0.0 does not offer separate analytics or crash-reporting switches. Both services remain enabled while the shared acceptance is in place. To withdraw it, use the control described below; withdrawal ends access to gameplay until you accept again. An older acceptance covering only the EULA is not reused to enable the expanded data collection. The shared acceptance does not grant personalised-advertising consent: the advertising choices described below remain separate. Simply opening this notice does not record acceptance.

Playing the game and purchases

The game stores progress and settings on your device so you can continue playing. This storage serves the game functions you request. Where it involves personal data, Article 6(1)(b) GDPR applies; necessary device storage is covered by Section 25(2) TDDDG. Device backups may also contain app data, depending on your operating-system settings.

If you make an in-app purchase, Apple or Google handles the store transaction. The game uses purchase status and transaction or receipt information to unlock or restore the purchased content. We do not receive your full payment-card details through the store purchase. The basis for fulfilling purchases is Article 6(1)(b) GDPR; legally required records fall under Article 6(1)(c).

Store providers also process account and payment information under their own policies: Apple privacy policy and Google privacy policy.

Advertising: Google AdMob

We use Google AdMob to display advertisements and help fund the game. Depending on device permissions, consent and advertising settings, Google’s advertising SDK can process IP addresses, approximate location inferred from an IP address, device or advertising identifiers, ad views and interactions, and diagnostic or performance information.

This information is used to deliver and measure advertisements and detect fraud. Personalised advertising can involve using activity to infer interests. Non-personalised advertising can still involve technical data and device storage. Google and the advertising partners involved in an ad request may receive data. The partner selection needs to match the list shown in the app’s consent information.

Further information: How Google uses data from apps using its services and Google Mobile Ads data disclosure.

Usage statistics: Firebase Analytics

We use Google Analytics for Firebase to understand how Castaway Life is used and improve it. The SDK can process an app-instance identifier, app launches and other usage events, session information, app version, device and operating-system details, language and approximate location. Advertising identifiers depend on the platform, permissions and configuration; purchase events may also be included.

In version 2.0.0, gameplay events include mission progress, completed buildings, upgrades, character deaths, in-game item choices and summaries of active play. Collection is enabled after the shared startup acceptance; it is not offered as a separate optional switch. Analytics identifiers can distinguish installations, so this processing is not described as anonymous. Google documents its collection in Analytics data collection.

Crash reporting: Firebase Crashlytics

We use Firebase Crashlytics to find and fix crashes. Reports can include crash traces, installation identifiers, app and operating-system versions, device information and the state of the app around a crash. These reports help us identify faults and assess their impact. In version 2.0.0, crash-report collection is enabled after the same startup acceptance as analytics. Reports from an accepted session can be sent on a later launch. See Firebase privacy and security information.

Withdrawal and legal basis

In version 2.0.0, open Main menu → Settings → Withdraw EULA acceptance. A confirmation explains that withdrawing the shared acceptance disables analytics and crash-report collection and closes the game. Confirm with “Withdraw & quit”. If the operating system does not close the app, a blocking screen remains. Saved progress and purchase entitlements are kept. You must accept the agreement again before playing.

The app stops its own analytics events, requests that Firebase collection be disabled and requests deletion of locally stored, unsent crash reports. Some native Crashlytics settings take effect on the next launch. Withdrawal does not automatically erase reports already sent to a provider. You can contact us to exercise your data rights.

Advertising choices are separate from this shared acceptance and can be reopened through the advertising privacy control where available. Declining advertising consent does not by itself withdraw the startup agreement or disable Firebase gameplay analytics and crash reporting. Device advertising controls do not switch off all Firebase processing.

Processing based on consent requires valid consent under Article 6(1)(a) GDPR and, where applicable to device access or storage, Section 25(1) TDDDG. Consent can be withdrawn with future effect. Accepting an EULA or making data collection a condition of access does not by itself establish a valid legal basis. Contractual necessity applies only to processing actually necessary for the requested contractual service, not automatically to every SDK included in the game.

Older published versions may not offer these withdrawal controls or may handle collection differently. For help with your version, a data request or a child’s information, email info@lazyshoregames.com. Withdrawal does not affect the lawfulness of processing carried out on a valid basis before withdrawal.

Contact and support

When you email us, we process your email address, name if supplied, message, attachments and correspondence. For game support, this can include device details, game version, screenshots and purchase references you choose to send. Please exclude passwords, complete payment-card details and unrelated personal information.

Our mailboxes are hosted by SiteGround. We use correspondence to answer requests and resolve problems. The basis is Article 6(1)(b) GDPR for contractual enquiries and support, or Article 6(1)(f) for our interest in responding to general enquiries. Messages are kept while needed to resolve the matter; records needed to meet statutory duties or establish, exercise or defend claims may be kept longer.

Recipients and international processing

The providers described in this notice receive data needed for their services. Google services can involve Google LLC and processing in the United States or other countries. The applicable safeguards may include an adequacy decision or the European Commission’s standard contractual clauses, depending on the recipient and service. See Google’s transfer safeguards. Information about the safeguards applicable to your data can also be requested from us.

How long data is kept

• Game progress and settings: stored while retained in the app’s local storage or a device backup. Removing local data may remove progress and does not automatically delete data already sent to service providers.
• Analytics: the linked Analytics property currently keeps event-level data for 2 months and user-level data for 14 months. Its setting to reset the user-data period on new activity is enabled, so an active user’s period may extend. These settings do not set a single deletion date for all aggregated reports or other Google services. See Google’s retention explanation.
• Crash reports: Google states that Crashlytics keeps crash traces and associated identifiers for 90 days before beginning removal from live and backup systems.
• Advertising: retention varies with the data and purpose, including fraud prevention and legal requirements. Google explains its criteria in its data-retention information.
• Support and purchase records: kept for the relevant request or entitlement, and longer only where a statutory duty or the handling of legal claims requires it.

Your privacy rights

Under the GDPR, where its conditions apply, you can request access, correction, erasure, restriction and data portability. You may object to processing based on legitimate interests, and withdraw consent with future effect. Withdrawal does not affect earlier lawful processing.

Send requests to info@lazyshoregames.com. Please provide enough information to locate the relevant data; we may need proportionate proof of identity. You may complain to a supervisory authority, including the data protection authority for North Rhine-Westphalia (LDI NRW).

Changes to this notice

We update this notice when our services or data practices change. The version date appears above.