GAMESS
LAST HAVEN · GAMES-S

Last Haven Privacy Notice

Effective / updated: 2 November 2026

GAMES-S provides Last Haven for iOS. This notice covers this game's local storage, GameScope usage statistics, Google advertising services, and optional iOS push notifications. The separate privacy policy for the games-s.com website does not replace this game-specific notice.

Privacy and support contact: games.aistudio@gmail.com. You can play without registering an account or entering a name, phone number, or email address. If you contact support, we use your email address, message, and attachments to handle your request.

  1. Information stored on your device
  2. Information received by GameScope
  3. Google ads and privacy components
  4. Advertising and gameplay choices
  5. Purposes, recipients, and transmission
  6. Retention and outgoing events
  7. Removing local data and contacting us
  8. iOS push notifications
  9. Player feedback
  10. Updates to this notice

1. Information stored on your device

Campaign progress, points, turret and character progression, items, tutorial progress, language, and sound settings are saved locally. The app also caches advertising configuration, privacy choices, fullscreen-ad presentation times and counts, and pending reward records to restore settings, control ad frequency, and avoid duplicate rewards. These records are not server-based cloud saves. Core gameplay works offline; ads and analytics synchronization need a connection.

The device also stores a randomly generated analytics installation identifier, session state, and outgoing events. These identifiers do not directly contain a player's name, but can link actions from the same installation or session. They are not equivalent to unlinked aggregate statistics.

2. Information received by GameScope

Our GameScope service receives random installation, session, event, battle-attempt, and advertising-request identifiers; event time, game version, iOS platform, and language; foreground activity time, battle entries and exits, outcomes, waves, elapsed time, defeated-enemy counts, and tutorial steps and completion.

Advertising records include placements, configuration versions, requests, loading results, presentation, impressions, clicks, earned rewards, dismissals, error codes, and SDK-reported estimated ad revenue, currency, and precision. Revenue estimates are not player payments or final AdMob settlements.

Game analytics event fields do not include a name, email address, phone number, complete game save, full page URL, or raw IP address. Network communication still uses IP information. Connection rate limiting temporarily uses IP addresses, and service fault logs may contain connection information.

3. Google ads and privacy components

Google Mobile Ads (AdMob) supplies optional rewarded ads, interstitial ads that may appear on level-loading screens, and app-open ads that may appear on loading screens when the app starts or returns to the foreground. Google User Messaging Platform (UMP) handles applicable advertising privacy notices and choices. These components connect directly to Google. Where choices are required, that process determines whether an ad request can proceed.

Current requests specify non-personalized ads, and Google's publisher first-party ID feature is disabled. This version does not initiate an Apple App Tracking Transparency (ATT) prompt, request permission to use the IDFA, or request precise location permission. This does not mean that advertising components process no device or network information.

Google's iOS ad SDK may process connection IP and an approximate region inferred from it, app or device identifiers, ad activity, and diagnostics. Actual processing depends on features, settings, and applicable choices. Google's own processing and retention are explained in the official links below.

4. Advertising and gameplay choices

The tutorial and the entire first campaign battle, including its result screen, are ad-free. After this protection, revival, victory-point bonuses, recruitment refreshes, and airstrike supplies are optional rewarded offers.

After first-experience protection ends, a level-loading screen may automatically show an interstitial according to a configured probability. A suitable loading flow at app launch or return to the foreground may automatically show an app-open ad. These ads do not require a separate opt-in for each presentation, but do not appear directly over battle, pause, or result screens. An ad is skipped if it is not ready or its request fails.

You may decline rewarded offers and continue ordinary gameplay. Ad completion rewards depend on the SDK's earned-reward callback. The game settings link to this notice; when Google requires a privacy-options entry point, advertising privacy options let you revisit applicable choices.

Remote configuration can enable or disable placements, change ad units, and set the interstitial probability and presentation intervals. Interstitial and app-open ads share a fullscreen-ad cooldown. App-open ads also have a minimum time in the background before a return and a daily presentation limit. These settings cannot shorten first-experience protection. Disabling an ad placement does not disable GameScope usage statistics. The game currently has no separate analytics switch; queued offline events may upload after connectivity returns.

5. Purposes, recipients, and transmission

Local records support progress, settings, and reward delivery. GameScope information helps evaluate difficulty and feature usage, improve stability, investigate problems, and reconcile advertising, rewards, and estimated revenue. Authorized administrators can view and export these records. Google processes information received by its components for ad delivery, measurement, diagnostics, and abuse prevention.

GameScope APIs use HTTPS. Google and its service providers may process information outside your region under Google's privacy policy. We do not send support-email content as gameplay analytics events.

6. Retention and outgoing events

Unacknowledged analytics events are queued on the device for up to seven days, with a 2,000-event limit, and removed from the outgoing queue after server acknowledgment. Failed uploads retry; stable event identifiers prevent duplicate ingestion. Local saves, installation identifiers, settings, and necessary reward records generally remain until reset or app removal. iOS backup, restore, and offloading behavior also depends on system settings.

Last Haven server-side anonymous events currently have no fixed automatic deletion period and are retained for the analytics and maintenance purposes above. Automatic database backups retain the latest seven snapshots; separately retained manual backups or administrator exports may also exist. This is not a promise that every copy disappears on one fixed date. Google retention follows its policies and applicable settings.

7. Removing local data and contacting us

Removing the app can clear its local data, but does not automatically erase previously uploaded records, backups, or administrator exports. Reinstalling after local identifiers are removed generally creates a new installation identifier, and can remove the information needed to locate older records.

For questions or requests concerning linkable records, contact games.aistudio@gmail.com. We will verify the request and available identifiers and explain what can be handled. A random installation identifier cannot reliably be looked up from a name or email alone. There is currently no in-app account or automatic one-tap server deletion feature.

8. iOS push notifications

Push notifications are optional. At the first game launch, once resources are ready and the app is active, the game automatically asks for iOS notification permission (alerts, sounds, and badges) if permission has not been decided. You may allow or refuse. Refusal does not affect ordinary gameplay or the ad-free protection for the tutorial and first campaign battle. Once you have allowed or refused permission, the system prompt is not repeated. You can still manage notifications in game settings or change permission in iOS Settings; the game checks the system status again when you return.

To maintain subscriptions and send game notifications through Apple Push Notification service (APNs), GameScope receives a separate random push installation identifier, an installation registration credential, authorization status, app and version identifiers, language, and APNs environment. After permission, it also receives an APNs device token. A disabled status may be updated when permission is undecided or refused. The push installation identifier does not reuse the gameplay analytics identifier. Device tokens and registration credentials are not added to gameplay analytics events or supplied to advertising SDKs.

The registration credential is stored in the device iOS Keychain; the server stores only its verification digest. iOS may retain Keychain items after app removal, so uninstalling does not guarantee removal of every push credential. Registration updates and pending receipts may be queued locally and retried after connectivity returns.

We record received only when the app actually observes a notification in the foreground, and opened only when you tap a notification. Receipts contain the notification campaign identifier, push installation identifier, event type, and time, for delivery measurement and troubleshooting. We do not count system background delivery that the app has not observed as received. Tapping a notification does not automatically grant game rewards, start a battle, or trigger an ad; notification content does not reset an ongoing battle.

Apple processes the device token, notification content, and related network information needed for APNs delivery under its own privacy policy. When the game next detects that permission was disabled, it updates the server to deactivate that installation and clear its usable push token; a token Apple confirms is invalid is also deactivated. Disabling notifications does not automatically delete saved registration, campaign, receipt, backup, or export records. These Last Haven push records currently have no fixed automatic deletion period; the existing backup and contact-request explanations continue to apply.

9. Player feedback

In-game feedback on the home screen is optional. Only when you choose to submit does GameScope receive the message you enter, a random installation identifier, submission request identifier, game version, language, iOS platform, test or production environment, and submission time. You do not need to provide a name, email address, or phone number; please avoid including sensitive information in your message.

When you open the feedback panel, the game uses its installation identifier and native credential to check your remaining quota, without uploading an unsubmitted message. Feedback uses the same random installation identifier and native verification credential as push registration, and works when notification permission is refused. The credential is stored in the iOS Keychain and the server retains only its verification digest. Neither the credential nor an APNs device token is put in your feedback message. The identifier can link records from the same installation and is not unlinked aggregate data. Each anonymous installation player can submit up to 20 messages in total, counted across test and production environments. Retrying the same request does not consume another submission.

Authorized administrators can view feedback for game support, troubleshooting, and improvement. Message content is stored separately from gameplay analytics events, is not sent to advertising SDKs, and is not used for advertising targeting. The device may retain an unfinished submission and its request identifier so you can retry without duplicate submissions.

Feedback and quota records currently have no fixed automatic deletion period. The existing database backup and contact-request explanations also apply. Removing the app or disabling notifications does not automatically delete submitted feedback.

10. Updates to this notice

We update this notice and its date when game features, advertising services, or data practices change. The official Google resources below provide further information about its components.