REEF
GUARDIAN

Studio Spark · Reef Guardian

Privacy Policy

Updated 16 November 2026. This notice explains how Studio Spark handles information in Reef Guardian and on this website. It describes the current Reef Guardian app. Here, iPhone also means iPad. To change tracking, advertising or activity choices, see Your privacy choices.

Who we are

We are Studio Spark, based in South Korea. Contact s.park.dxbb@gmail.com for privacy questions or requests.

Your game and account

Reef Guardian plays from the game save on your device. An internet connection is needed each time the app starts, to sign in your game account and check our game service; after that, play does not wait for the network. On first start, the app creates a guest game account with Firebase Authentication. This is an anonymous account identified by a random user ID. Sign in with Apple on iPhone and Sign in with Google on Android are optional. On iPhone, if you are already signed in to Game Center, Game Center may greet you when the game opens; the game does not ask you to sign in to Game Center and stores no Game Center information.

The app backs up your game save to our game service, linked to that user ID. The backup contains your progress, inventory, balances and the reward and purchase records kept in the save; a battle in progress stays on your device. Backups are made at natural moments, such as when the app goes to the background, and at most every few minutes while you play. TestFlight versions use our testing service and the App Store version uses our released-game service; their backups are kept separately. If an older version of Reef Guardian was installed on the same iPhone, the app imports that saved progress once on the device.

You can choose Sign in with Apple in Settings. Firebase Authentication verifies the sign-in and adds it to the same game account. If you allowed Apple to share an email address, Firebase may retain that address or an Apple private relay address in your sign-in record. We use it for account authentication, not marketing. We do not receive your Apple password.

On Android, choose Sign in with Google in Settings. Firebase Authentication verifies the sign-in and adds it to the same game account, and Firebase may retain your Google account's email address in your sign-in record. We use it for account authentication, not marketing. We do not receive your Google password. Recover with Google works like Recover with Apple below, using your Google account.

Recover with Apple opens the game backed up to your Apple account, for example on another iPhone or after reinstalling. If the device already has progress, the app asks before replacing it. If you confirm and the replaced game was an unconnected guest game, its purchase records and pending refund items move to the Apple-connected game, and the guest account, its backup and its activity events are then deleted where possible, because nobody can sign in to it again. If our service holds a different backup for the same account, the app keeps the more progressed save. A guest game that is not connected with Apple may not be recoverable if you remove the app or lose the device.

Why we keep these records

We use account, save, purchase and activity records to provide the game, back up and restore progress, verify purchases, apply Apple and Google Play refunds, investigate problems and, if you allow it, understand how the game is played. Purchase records include the product, Apple transaction identifiers, the store environment and the signed transaction Apple provides, which our service verifies. On Android they include the product, the Google Play purchase token and order ID and the store environment, which our service verifies with Google Play.

Connecting a game with Apple or Google gives a one-time gift of 100 Pearls. The gift is recorded in the game save.

Ads

Rewarded ads are optional; nothing in the game requires you to watch an ad. On iPhone and Android, Google AdMob provides the ads and Google's User Messaging Platform provides advertising privacy choices. Through AdMob mediation (bidding), an ad may also come from Unity Ads (Unity Technologies) or Meta Audience Network (Meta Platforms). When one of them bids for or provides an ad, it receives the same kinds of ad request information, under the choices described in Tracking and your choices.

Ad providers may process IP addresses, approximate location, app and device information, diagnostics, and ad views and interactions to deliver ads, limit how often an ad is shown, prevent fraud and count ad views and clicks. Advertising identifiers are used only as your choices allow; on iPhone, only if you allow tracking (see Tracking and your choices). Without that permission, the advertising identifier is not available and activity in this app is not linked with data from other companies' apps or websites. Reef Guardian does not ask for location permission and does not collect or pass the device's precise location to its ad providers; they may estimate an approximate location from the IP address. Google's consent message lists purposes that its ad partners may use in general, including precise geolocation. An ad or its reward may be unavailable if consent or ad inventory is unavailable. Game accounts and devices that Studio Spark registers for its own testing receive Google test ads.

Settings → Report an ad opens your email app with a prepared report. It includes the ad area you choose, where and when the last ad was shown, the time of the report, your app language and any note you add. Nothing is sent until you send the email. The app keeps the last ad only in memory while it is running.

See Google's privacy policy, Google Mobile Ads data disclosures, Unity's privacy policy and Meta's privacy policy.

Tracking and your choices

Apple calls it tracking when information from an app is linked with information from other companies' apps and websites for targeted advertising or advertising measurement. On iPhone, Reef Guardian asks for your permission with Apple's App Tracking Transparency prompt:

If you allow tracking, our ad partners (Google, Unity and Meta) may use your device's advertising identifier (IDFA) and ad interaction data to personalise ads and to measure them across apps and websites owned by other companies. Where consent choices apply to you, this use stays within them. Where Google's consent message does not apply, the app also starts Meta App Events and Tenjin to measure our own ads, except on an installation where Apple's tracking prompt was already answered in an earlier version of the app (see Measuring our own ads with Meta and Tenjin).

If you do not allow tracking, are not asked, or tracking is restricted on your device, iOS does not make the advertising identifier (IDFA) available. The app marks ad requests as non-personalised, turns off Google's publisher first-party identifier, tells Meta that tracking is not allowed and does not start Meta App Events. Tenjin does not initialize. In the EEA, the UK and Switzerland, ad requests are also non-personalised if you do not consent to personalised ads in Google's message. Eligible ads may still be shown, depending on your consent choices and available ads, but they are not personalised with data from other companies' apps or websites. Ad providers still process the limited information described in Ads to deliver ads in this app, limit how often an ad is shown, prevent fraud and count ad views and clicks.

On Android there is no tracking prompt. Where Google's consent or privacy options apply, ads are personalised only as your choices allow; elsewhere ad providers may personalise ads using your device's advertising ID, which you can reset or delete in Android Settings.

Changing your choices. On iPhone, open Settings → Apps → Reef Guardian → Allow Tracking, or Settings → Privacy & Security → Tracking and turn Reef Guardian on or off. In the game, Settings (the gear) → Privacy → Ad tracking shows the iOS setting: Allowed, Not allowed or Not asked. Tapping it opens iOS Settings, or asks for tracking permission if the app has not asked yet. Where Google requires them, in the EEA, the UK and Switzerland, Settings → Privacy → Privacy options on iPhone and Settings → Support → Privacy options on Android reopen Google's privacy options so you can review or withdraw your advertising consent. After a withdrawal, later ad requests are non-personalised; this does not change your tracking permission in iOS Settings. Step-by-step instructions are in Your privacy choices.

Measuring our own ads with Meta and Tenjin

We use Meta App Events on iPhone to measure installs from our ads on Facebook, Instagram and Meta's advertising network. It starts only after you allow Apple's tracking request and Google's consent check for that launch finishes with no consent message required. A saved result from an earlier launch is not enough. It does not start if a Google consent decision is stored, or if Apple's tracking request had already been answered when the app first recorded eligibility for Meta App Events.

Where Google's consent message applies, including the EEA, the UK and Switzerland, Meta App Events does not start, whatever you choose in that message.

When Meta App Events starts in an eligible app process, it attempts install reporting if it has not already recorded that report. A failed attempt can be retried later. It restores session timing and can log an app activation and details of the previous session, including its duration and interruptions. Returning to the app does not always send a new app open event, and closing it does not immediately send a close event.

Meta's SDK adds app and device information, including the app version, device model, operating system, language, time zone and screen size. It also adds its own random identifier, the IP address of the connection and your advertising identifier (IDFA). It downloads settings from Meta and may report the device's tracking status.

Meta uses this information to measure our ads. Meta may also use it to personalise ads and other parts of its services, depending on your location, your settings and Meta's privacy policy. Our game code does not send gameplay activity, purchases or your game account ID to Meta App Events.

In the app, we turn off automatic event logging, including automatic purchase logging and crash instrumentation. We also turn off screen title and app link metadata collection, product improvement sampling, automatic AEM setup and Meta's own SKAdNetwork reporting. The explicit install and session measurement described above still operates.

Codeless event setup, automatic advanced matching and suggested events are controlled through Meta's server settings. In our Meta Events Manager, automatic event logging and automatic advanced matching are off, and we have not set up codeless events. The app's settings do not independently block every server controlled feature. Turning off codeless debug logging only turns off that logging.

On Android. The question is Measure our ads with Meta and Tenjin? The setting is Meta and Tenjin ad measurement. We ask only on installations the app recognised as new when it first checked eligibility for measurement. If that check found an update from an older installation, we do not ask and do not measure. We save your answer. This update asks again because the question now names Tenjin. An earlier Allow answer to the question that named only Meta still allows Meta. Tenjin stays off until you choose Allow on the new question or turn on the new setting.

We offer this choice only after Google's consent check succeeds on that launch and says consent is not required. A result saved from an earlier launch is not used. We also check that no European consent record (TCF) is stored on the device. Google's result depends on your location and the privacy messages set up for our app. If the check fails, Meta and Tenjin ad measurement does not start. If it is slow, the question may come later in that launch or on the next one.

While measurement is allowed and these checks pass, the app asks Meta's SDK to report the installation if it has not been reported successfully yet. The app records an app open when measurement first starts during a launch. This can happen right after you choose Allow or turn it on in Settings. On later launches it records another app open if measurement is still allowed and the checks pass. Returning to the game while it is still running does not count as another app open. On Android we do not report how long the game was played. Meta receives information about the app and your device, such as app version, device model, operating system, language, time zone, screen size and carrier. It also receives a random identifier that its SDK keeps on the device, your advertising ID when Android provides one, and your IP address when the app connects to Meta. The SDK also downloads its settings from Meta. After you allow it, the app may read the install referral information from Google Play, and may try again on a later launch if that fails. If it contains a Meta marker, the app passes it to Meta to help match the install to our ad.

Meta uses this to measure our ads. Meta may also use this information to personalise ads and other content, including AI responses, and improve its services. This depends on where you are, your settings and Meta's privacy policy. Our game does not send your gameplay activity, purchases or game account ID to Meta. In the app we turn off Meta's automatic app event logging, automatic purchase logging and crash reporting. We also turn off the SDK settings that add extra event details and collect product improvement samples. In Meta's settings for our app, automatic in app purchase logging for Android is off.

When the setting is shown, you can turn measurement off in Settings (the gear), then Privacy. The setting may be missing if Google's check fails or takes too long. If you allowed measurement before, a late successful check can start it even though the setting is missing on that launch. After you turn it off, the app stops logging new installs and app opens and does not start Meta measurement on later launches while it stays off. Data the SDK had already queued in that session may still be sent. Turning it off does not delete data already sent to Meta. Meta's privacy policy explains how long Meta keeps it and what controls you have there. Resetting your advertising ID in Android Settings gives your device a new ID, and deleting it stops apps from reading one where Android supports that. Neither turns off Meta measurement in our game.

We also use Tenjin to see which of our ads bring people to Reef Guardian, including ads on Unity Ads. Tenjin receives install and app opening information, advertising and installation identifiers, IP address, and app and device information. This can include the device model, operating system, language, country, time zone and app version. It may receive ad attribution information, including the Google Play install referrer or Apple Ads attribution. Our game does not send gameplay events, purchases or game account IDs to Tenjin. Automatic purchase and subscription reporting is off.

On iPhone, Tenjin uses the same installation eligibility and consent conditions as Meta App Events. You must have allowed Apple's tracking request. Google's consent check for this launch must have finished and say consent is not required. There must be no stored European consent record. Tenjin does not initialize when these conditions are not met. If it started earlier, the app opts it out when it rechecks permission and these conditions are no longer met. Our game does not use Tenjin to change SKAdNetwork conversion values.

On Android, turning off Meta and Tenjin ad measurement stops the app from logging new installs and app opens to Meta and opts Tenjin out. Meta data already queued in that session may still be sent. Requests already sent cannot be recalled. Turning it off does not delete information either company already received.

Tenjin processes this information for advertising measurement. See Tenjin's privacy policy. To request access to or deletion of information processed for our app, contact s.park.dxbb@gmail.com. Turning off measurement and deleting a game account do not by themselves confirm that Tenjin has deleted previously received information.

Meta and Tenjin ad measurement is separate from Share gameplay activity?, which covers our own gameplay analytics.

Separately, the app registers the installation with Apple's SKAdNetwork and requests its initial conversion value. If iOS reports an error, it can try on a later launch, at most three launches in total. If an install is attributed to an ad, iOS may send the ad network an attribution report with limited ad and conversion information without your identity or device identifiers. This can happen whether or not you allow tracking. The game supplies no player data for this report.

To stop Meta App Events on iPhone, turn off tracking for Reef Guardian in Settings → Privacy & Security → Tracking. From the next launch, the app does not start Meta App Events. Apple's SKAdNetwork attribution can still operate. Meta's account settings manage some uses of information from other businesses; they do not turn off Meta App Events in Reef Guardian. See Meta's privacy policy.

Gameplay activity and diagnostics

The app sends activity events to our game service, linked to your game account's user ID. Some events are needed for the game to work and are always sent: purchase verification and refund matching, including the signed transaction Apple provides; save backup bookkeeping; account connection, recovery and deletion bookkeeping; and changes to your activity-sharing choice.

Gameplay usage and diagnostic events are sent only if you choose Share when the app first asks Share gameplay activity?. They can include screens and actions, stages played, choices made, results, run references, purchase attempts and their results (started, completed, cancelled or failed), loading times, the store country and currency used for prices, and the app build number. They are not used for ads or tracking. You can turn this off at any time in Settings → Privacy → Share gameplay activity. While it is off, these events are not stored on the device, and any not yet sent are discarded.

Events are sent in batches when the app starts, goes to the background or finishes a run. Testing activity is kept separate from released-game activity. Our service keeps activity events while your game account exists; they currently have no automatic expiry and are deleted when you delete your game account. We do not include account credentials, authentication tokens or email addresses in activity events.

On iPhone, the Firebase Analytics SDK is included with data collection turned off. On Android, Firebase Analytics starts turned off, is turned on only if you choose Share for Share gameplay activity?, and turns off again if you choose Don't share or turn sharing off later. While it is on, it sends Firebase Analytics' standard app-usage events to Google (such as first open, sessions, engagement time and screen views, with the app-instance identifier) and records how long rewarded ads take to open (placement, whether the ad was ready, milliseconds). It does not collect the advertising ID. These are not used for ads. Android versions released before 2 November 2026 sent these events, and where available the device's advertising ID, whatever you chose, until they are updated. Earlier versions of the game could send Google Analytics events when you allowed it. When you delete your game account, our service asks Google Analytics to delete data linked to this installation's analytics identifier and to guest IDs from those earlier versions found on the device. Google completes analytics data deletion within about two months. If our service cannot send the request right away, it keeps the request and retries. Google and other providers apply their own retention and deletion rules. See Firebase privacy information.

Payments, this website and email

Apple processes payments on iPhone. The app checks Apple's signed transaction on your device and adds the purchase to your game save. Our service verifies the transaction again and records it with your user ID so that Apple refund notifications can be matched to your game. Google Play processes payments on Android. The app sends the Google Play purchase token to our service, which verifies it with Google Play, records it with your user ID and matches Google Play refunds and cancellations to your game. We do not receive your full payment-card number. Apple manages its own store records under its privacy policy.

Cloudflare hosts our game services and this website and may process request and security information, including IP addresses. This website has no player login, checkout, third-party analytics script or embedded third-party video player, and it sets no cookies. The home page remembers the language you choose in your browser's local storage and, to suggest a language, asks Cloudflare for your approximate country.

If you email us, we receive your email address, message, attachments and any player or transaction reference you include. We use them to answer your request. Our mailbox uses Gmail. Please do not send passwords, verification codes or full payment details.

Service providers and locations

We use Firebase Authentication, Cloudflare, Google AdMob and consent services, Unity Ads and Meta Audience Network (ads through AdMob mediation on iPhone and Android), Meta App Events (measuring our own ads on iPhone and Android, as described above. Meta may also use this data for its own purposes under its privacy policy), Google Analytics (app-usage events and rewarded-ad opening times on Android as described above, and deletion requests about data sent by earlier versions), Google Sign-In and Google Play (Android), Gmail and Apple for the purposes above. We also use Tenjin to measure our own ads on iPhone and Android. Tenjin receives the information described above. Providers also explain their own processing in their privacy policies.

Information may be processed outside your country. Firebase Authentication uses US data centres; other services may process information in additional countries. See Firebase's processing locations and Cloudflare's privacy policy. Any additional notice, consent or safeguards required for your region apply.

Retention and deletion

We keep your save backup, activity events and purchase and refund records while your game account exists. To delete your game account, open Settings → Delete account and confirm. Reset progress in Settings runs the same full deletion and then starts a new game. If your game is connected with Apple, you confirm with Apple first and the app asks Apple to revoke its Sign in with Apple token. On Android, deleting the game account also removes its Google sign-in.

Our service then deletes your user ID's save backups, activity events, purchase records and refund records in both the testing and released-game services, together with records kept by earlier versions of the game; those older records are erased within about an hour. Your Firebase account is deleted, and the app then erases its game data on the device, including saves from older versions. Your language and other device settings stay on the device. If deletion cannot finish, for example without a connection, the app shows Retry. If you close the app first, open Settings → Delete account again.

What remains: Apple's own App Store purchase history; Apple refund notifications our service has received, which contain store transaction references and are no longer linked to your account; limited deletion-status records; for 30 days, a one-way hash of the deleted account's user ID so that another device still signed in to it cannot re-create its data; and, once a Google Analytics deletion request has been sent, a record of that request with only its reference and times. Until a deletion request has been sent, it keeps the identifiers needed to send it. Deleting the account does not delete your Apple account, request a refund or immediately erase provider-held ad, store, analytics or backup records. Provider retention rules apply to those records. We keep support messages while handling the request and remove information when it is no longer needed, except where a dispute or legal duty requires retention. See Account & data requests.

Your choices

Email us to request access, correction, deletion, restriction or information about your records, or to withdraw consent where it applies. We may need limited information, such as an Apple transaction reference, to find your records and verify ownership. You can contact us even if you cannot open the game. We respond within the period required by applicable law and explain any retention exception. You may complain to your local data protection authority.

Essential account processing provides the game service you request. Sharing gameplay activity is optional and can be changed in Settings → Privacy. Tracking permission and Google's privacy options can be changed as described in Tracking and your choices. Security and legally required records are used for their stated purposes. We cannot remotely remove a save held only on your device.

Younger players and updates

Reef Guardian is not directed at children. A store age rating is different from the age at which privacy consent is required. Contact us if a child has provided information without required permission. See Age & parental guidance for who the game is for and what it contains.

We limit access and use appropriate security measures, but no system can guarantee absolute security. We update this notice when our services or data handling change and provide additional notice where required.

Purchases when you delete an account

Deleting your account permanently removes your progress, purchased Pearls and items, and our account-linked purchase records. This cannot be undone and does not automatically refund purchases. Apple and Google retain their platform transaction records. Deletion does not cancel permanent store purchase rights; contact support if a purchase cannot be restored. Limited security and legally required records may remain.