Intentionally Creative — Analytics and Advertising Partners

Last updated: October 25, 2026 · rev 15

This page names every third-party service that receives any data from our apps or from the advertising tools on nomadarcade.com, what each one receives, and how to stop it. It is referenced by, and forms part of, our Privacy Policy.

In our apps there are ten named on this page. We do not use a push-notification service, a customer-messaging SDK, a tag manager or an ad-network SDK other than the one named below. The fifth, Google's Gemini API, is used by one app, Pose Guide, and only after you agree (Section 6). The sixth and seventh, Google Analytics for Firebase and Firebase Crashlytics, are used by Launch Lab and Pose Guide (Sections 8 and 9). The eighth and ninth, Firebase Authentication with Google Sign-In, and Firebase Remote Config, are used by Pose Guide (Sections 10 and 11). The tenth, xAI, makes Pose Guide's example photos of a place from the place's name, and only after you agree (Section 12). Google Sign-In is the one social-login SDK in our apps, and it runs only when you choose Sign in with Google.

On nomadarcade.com there is one more: the Meta Pixel, on the page for each game we advertise on Facebook and Instagram (Section 7). The site's analytics is our own and runs across the site, the home page, the game pages and the policy pages included; Section 2.5 of the Privacy Policy describes it, with the cookie notice that lets you decline both.

Our own server is not on this list, because it is not a third party. Each app stores some of your data on our own server infrastructure, which we operate ourselves — see Section 2.4 of the Privacy Policy. None of it is sent to any of the services below, and none of them can reach it.

Milestone can schedule reminders, and that is not a fifth partner: those are local notifications the phone gives itself, with no push service, no push token and no server involved — the build strips the push entitlement it does not use. There is nobody to name because nobody receives anything.

The split that matters: games vs. utility apps

In our games — Parcel Yard and Pack Perfect

1. AppLovin MAX — advertising and mediation

• Company: AppLovin Corporation
• Privacy policy: https://www.applovin.com/privacy/
• Opt out: https://www.applovin.com/optout/
• GDPR information: https://www.applovin.com/gdpr/

What it is. AppLovin MAX is an advertising mediation layer. When one of our games has an ad to show, MAX runs an auction and hands the placement to whichever advertising network bids highest.

What it receives:

• Device identifiers — on an Apple device the vendor identifier (IDFV) always, and the advertising identifier (IDFA) only if you allowed tracking when the app asked; on Android the Google Advertising ID (GAID), unless you have deleted it in Android Settings → Google → Ads
• Device and system information — model, operating system and version, language, country/region, time zone
• IP address, from which a coarse country or region is derived
• App information — app version and bundle identifier
• Ad events — requests, impressions, clicks, and the revenue an impression produced
• Consent and privacy signals — your tracking answer and your consent-form answer, so that networks can honor them

The mediated networks. This is the part of the page most companies get vague about, so here is our position stated exactly:

When MAX fills a placement, it passes the ad request to the advertising networks we have enabled in the MAX dashboard, and each of those networks is an independent controller of the data it receives for its own advertising purposes. As of the date at the top of this page we have enabled no mediated networks, because our games have not launched. Before any mediated network serves a single ad in our games, this page will list it by name, with the data it receives and a link to its own privacy policy — the same table shape used above. AppLovin publishes its own list of MAX mediation partners at https://www.applovin.com/max-partners/.

How to stop it:

1. Buy "Remove ads" in Parcel Yard — it permanently removes interstitial advertising. (Rewarded videos remain available if you choose to watch one.) Parcel Yard's interstitials are capped at four a day, never appear on your first day or in your first session, never appear before board 15, and never appear within a minute of a rewarded video. Neither game shows banner, MREC or app-open ads at all.
2. Settings → Ad & data choices in the game reopens the consent form and shows your tracking status.
3. On an Apple device: iOS Settings → Privacy & Security → Tracking — turn tracking off for the app. The advertising identifier becomes unavailable and the ads you see are non-personalized.
4. On an Android device: Settings → Google → Ads → Delete advertising ID (older versions call it Opt out of Ads personalization). Android has no per-app tracking prompt; this is the system's own control and it applies to every app on the phone at once. Our games then receive a string of zeros and the ads you see are non-personalized.
5. AppLovin's own opt-out, at the link above.
6. Simply never tap a rewarded video. In Pack Perfect that is the only ad there is.

2. Apple App Tracking Transparency (ATT)

• Whose it is: Apple Inc. — part of iOS, not an SDK we add
• Apple's explanation: https://support.apple.com/en-us/102420
• Apple's developer rules: https://developer.apple.com/app-store/user-privacy-and-data-use/

What it is. ATT is the iOS permission that decides whether an app may use your advertising identifier or otherwise link your activity to other companies' data. When you tap "Ask App Not to Track," the advertising identifier returns all zeros and our advertising and attribution partners cannot use it.

How our games ask. Once, at the first moment an ad is actually on offer — never at launch, never during onboarding, and never behind a "pre-permission" screen designed to pressure a yes. In Pack Perfect, that moment is your tap on "Watch a short video for one hint."

Saying no costs you nothing. The video still plays, the hint still arrives, the reward is the same, nothing is hidden, and the app does not ask again. Ads simply become non-personalized.

Our utility apps never show this prompt, because they contain nothing that would need it.

2a. Google's User Messaging Platform (UMP) consent form — Android

• Whose it is: Google LLC — presented for us by AppLovin MAX, which integrates it; we do not build our own consent screen
• Google's explanation: https://support.google.com/admob/answer/10113004
• AppLovin's description of the flow: https://support.applovin.com/en/max/android/overview/privacy

What it is, and why this section exists. Android has no App Tracking Transparency. There is no system prompt that asks, per app, whether you may be tracked. So on Android the consent form our games show you before the first ad is the whole mechanism: it is Google's UMP form, it is what asks for your consent to personalized advertising in the European Economic Area, the United Kingdom and Switzerland, and your answer is passed on as a standard consent signal to every advertising network in the chain.

How our games ask. The form is shown before an ad is served, in the regions where consent is required, and never as a wall in front of the game. You can reopen it at any time from Settings → Ad & data choices and change your answer.

Saying no costs you nothing. The video still plays, the hint still arrives, the reward is the same, and nothing is hidden. Ads simply become non-personalized.

The device-level control is separate and is yours regardless: Android Settings → Google → Ads → Delete advertising ID. It applies to every app on the phone, ours included, and it does not depend on any answer you gave us.

Our utility apps never show this form either, because they contain no ad SDK — and on Android they go further: the advertising-ID permission is removed from those apps entirely, so there is no advertising identifier on either platform, not one we choose not to read.

In all four apps

3. AppsFlyer — install attribution and measurement

• Company: AppsFlyer Ltd.
• Privacy policy for end users of apps using AppsFlyer: https://www.appsflyer.com/legal/services-privacy-policy/
• AppsFlyer's own privacy policy: https://www.appsflyer.com/legal/privacy-policy/
• Opt out: https://www.appsflyer.com/legal/opt-out/

What it is. A mobile measurement partner. It tells us, at the level of a marketing campaign, that installs came from a particular ad — so we do not spend money on advertising that does not work. It is required in order to run advertising campaigns on AppLovin at all.

What it receives — and this differs by app:

In our games (Parcel Yard, Pack Perfect):

• Device identifiers — the AppsFlyer ID always; on an Apple device the IDFV, and the IDFA only if you allowed tracking; on Android the Google Advertising ID, unless you have deleted it in Android Settings → Google → Ads
• Device and system information, IP address (coarse country), app information
• A short, named list of in-app events, and ad-revenue events
• The SDK starts only after the tracking prompt has been answered, either way

In Before I Unpack:

• No advertising identifier, ever, on either platform. The SDK is started with advertising identifier collection explicitly disabled, and device-name collection disabled with it — "Sam's phone" is a person's own words. On Android we go one step further than a setting: the advertising-ID permission is removed from the app, so this app cannot read the Google Advertising ID at all, even though the attribution component inside it would otherwise ask for it.
• It does not start at all until you turn on Share anonymous usage, which is off by default.
• The events it may receive are exactly: activated, record_completed, pdf_exported, landlord_sent, compare_reviewed, purchase_completed. Nothing else, ever — the app's own code refuses anything outside that list.
• Attribution runs through Apple's SKAdNetwork on Apple devices, and the Google Play Install Referrer on Android — the latter tells us which campaign a download came from and carries no identifier of you. Both return aggregated postbacks containing no user identifier by design.

In Milestone:

• No advertising identifier, ever, on either platform — the same explicit disabling, the same reason, and on Android the same removal of the advertising-ID permission from the app. A note on one thing that is not protection: this app sets AppsFlyer's "strict mode" flag, and that flag is implemented for Apple devices only. On Android what carries the promise is the removed permission and the event allowlist, not the flag.
• A short list of allowlisted events with allowlisted properties, and the app's locale. No name, amount, note, photograph, phone number, venue, date or row identifier can be in any of them.

How to stop it:

1. The switch in the app's Settings — Share usage analytics / Share anonymous usage / Ayudar a mejorar la app. In Before I Unpack and Milestone this stops attribution as well as analytics, at the app, not just at the provider.
2. On an Apple device: iOS Settings → Privacy & Security → Tracking (games).
3. On an Android device: Settings → Google → Ads → Delete advertising ID (games; our utility apps cannot read it in any case).
4. AppsFlyer's own opt-out, at the link above.

4. PostHog — product analytics

• Company: PostHog, Inc.
• Privacy policy: https://posthog.com/privacy
• Data processing agreement: https://posthog.com/dpa
• EU hosting: https://posthog.com/eu

What it is. First-party product analytics: it counts how many people finished a level, exported a document, or reached a screen. It is not an advertising product, joins nothing to another company's data, and reaches no data broker.

What it receives: a random, device-local identifier it generates itself; the event names on that app's declared list with their allowlisted properties; app version; device and OS information; and locale.

What is switched off in every one of our apps, deliberately:

Where it is hosted: PostHog EU Cloud for Parcel Yard, Pack Perfect and Before I Unpack. PostHog US Cloud for Milestone.

How to stop it: the switch in each app's Settings. Turning it off stops collection at the app and opts the provider out; it does not merely mute the sending. In Before I Unpack it is off until you turn it on.

5. RevenueCat — purchases and entitlements

• Company: RevenueCat, Inc.
• Privacy policy: https://www.revenuecat.com/privacy
• Data processing agreement: https://www.revenuecat.com/dpa/

What it is. The service that knows whether you bought the one-time unlock, and that makes Restore purchases work on a new device. It is not an advertising or analytics product.

What it receives: an anonymous app user ID it generates itself; the product identifier, transaction identifier and store receipt; and entitlement status. We never send it a name, an email address or any subscriber attribute. In Pose Guide the app user ID is your Pose Guide account ID instead of one RevenueCat makes, so our server can match a purchase to the account. It is a random value with no name or email address in it.

It is the one provider that runs before the analytics question in Before I Unpack, and that is deliberate: somebody who paid must get what they paid for on a fresh install, and holding an unlock hostage to an unrelated second "yes" would be the dark pattern, not the fix.

How to stop it: you cannot switch it off and still receive what you bought. If you have made no purchase, it holds nothing but an anonymous identifier.

In Pose Guide only

6. Google's Gemini API: the cloud recipe

• Company: Google LLC
• Terms for this service: https://ai.google.dev/gemini-api/terms
• How long it keeps a request, and why: https://ai.google.dev/gemini-api/docs/usage-policies
• Its processor terms: https://business.safety.google/processorterms/
• Privacy policy: https://policies.google.com/privacy

What it is. When an iPhone cannot plan a shot on its own, Pose Guide can ask Google's Gemini API to write the plan: the lens, where to stand, how high to hold the phone and a pose cue. Pose Guide asks you first, on a screen titled Plan this shot with Google?, and sends nothing to Google until you choose Allow.

What it receives, through our server, for each plan: what you said or typed, with names replaced by the word [name] on the phone; one frame from the camera, 512 pixels on its long side, redrawn so it carries no location or other metadata; the scene words the phone read from that frame; how many people are in view; the phone's lenses; and the names of five recipes from Pose Guide's library. It receives no identifier of you: the request comes from our server, and your account ID is not in it.

What Google does with it. Pose Guide uses Google's paid Gemini API service. Under Google's terms for it, Google processes the request as our processor and does not use it to improve its products. It keeps prompts and answers for 55 days only to detect and prevent violations of its Prohibited Use Policy. Authorized Google staff may read content its systems flag, and it trains no model with it except those that enforce that policy. Google may store it transiently or cache it in any country where Google or its agents keep facilities. We store none of it.

Who may use it. Google requires the people using this service to be 18 or older. If you are under 18, leave it off.

How to stop it:

1. Choose Not now when Pose Guide asks. Every plan is then made on the phone.
2. Settings → Cloud recipes in Pose Guide, behind the gear at the top right of the camera, turns it off at any time.

On nomadarcade.com

7. Meta Pixel: measuring our ads on our landing pages

• Company: Meta Platforms, Inc.
• Privacy policy: https://www.facebook.com/privacy/policy/
• Cookies policy: https://www.facebook.com/privacy/policies/cookies/
• Your Meta ad settings: https://www.facebook.com/adpreferences/ad_settings

What it is. A script from Meta on the page for each game we advertise on Facebook and Instagram (today, https://nomadarcade.com/cannon-clash/, https://nomadarcade.com/thunk/, https://nomadarcade.com/sky-chase/, https://nomadarcade.com/scoot/, https://nomadarcade.com/cupshot/, https://nomadarcade.com/tall-order/, https://nomadarcade.com/swingaroo/, https://nomadarcade.com/launch-lab/ and https://nomadarcade.com/parcel-yard/). It tells Meta which of our ads brought a visit and an App Store tap, so we can keep the ads that work. It is in none of our apps, and no other page on nomadarcade.com loads it.

What it receives:

• that the page was opened, and which game it is about
• each tap on an App Store button, and which button it was; Meta's script also reports taps on its own, with the button's text and destination and the page's title
• the page address, with its campaign tags and Meta's click identifier, and the page that sent you
• your IP address, what your browser and device report about themselves, and your screen size
• the _fbp and _fbc cookie identifiers, which last 90 days

Automatic matching of email addresses and phone numbers is off, and our pages have no field to type one into.

When it does not run: for a device set to a time zone in the EU, the EEA, the UK or Switzerland, even after you accept the cookie notice; for a browser that sends Global Privacy Control; and once you choose Decline on the cookie notice. It then does not load and sets no cookie. If it was already running when you declined, the page tells it to stop sending anything to Meta at once.

How to stop it:

1. Choose Decline on the cookie notice, or later under Cookie settings at the foot of any page on nomadarcade.com that has the notice. The choice is kept in your browser's local storage as cookie-consent.
2. Turn on Global Privacy Control in your browser.
3. Block or delete cookies for nomadarcade.com in your browser.
4. In your Meta ad settings, change how Meta uses activity from other websites for the ads it shows you.

In Launch Lab and Pose Guide

8. Google Analytics for Firebase — product analytics

• Company: Google LLC
• Privacy and security in Firebase: https://firebase.google.com/support/privacy
• How Google uses information from apps that use its services: https://policies.google.com/technologies/partner-sites
• Privacy policy: https://policies.google.com/privacy

What it is. Google's product analytics for apps. Launch Lab uses it to count how many people open each screen, finish the tutorial, make a first merge, reach each level, open the shop and complete a purchase, so we know where the game loses people. It runs beside the game's own events on our own server, not instead of them.

What it receives:

• the screens you open, how long each was on screen, and when the app goes to the background and comes back
• the tutorial steps, your first merge, the levels you reach, the shop or a paywall opening, and a purchase started and how it ended
• Firebase's own automatic events: first open, session start, user engagement, and each in-app purchase, which it reads from the App Store with its product and price
• a random app-instance identifier, which we do not connect to your account
• device and operating system information, app version and language, and a coarse region Google derives from your IP address

What it never receives: your account identifier, your name, your email address or anything you type. No advertising identifier is collected: the build carries the version of Google Analytics that has no code to read one, its collection is switched off as well, and ad personalization signals are off. There is no ad network and no attribution SDK in Launch Lab, and no tracking prompt.

How to stop it: Settings → Share usage analytics in Launch Lab. It is on by default. Turning it off stops collection at the app, for Google Analytics and for the events on our own server alike; it does not merely mute the sending. Crash reports are separate (Section 9).

In Pose Guide it receives nothing until you say yes on Share anonymous usage?, which Pose Guide asks once, on your first result. Then it receives the events on Pose Guide's declared list (Annex F of the Privacy Policy), Firebase's own automatic events, among them each in-app purchase with its product and price, the same device information and a region from your IP address, as fine as the city. No user ID is set, so nothing ties the events to your account, and the same advertising settings are off. Settings → Share anonymous usage in Pose Guide turns it off, together with crash reports.

9. Firebase Crashlytics — crash reports

• Company: Google LLC
• Privacy and security in Firebase: https://firebase.google.com/support/privacy
• Privacy policy: https://policies.google.com/privacy

What it is. Google's crash reporter. When Launch Lab crashes, it tells us where in the code the crash happened, so we can fix it.

What it receives: the stack trace of the crash, the state of the device and its operating system, and a random Crashlytics installation identifier. A crash report is not linked to your name or your email address, and it carries neither.

How to stop it: in Launch Lab, crash reports are separate from Share usage analytics, and the app has no setting that turns them off. In Pose Guide, crash reports are sent only after you say yes on Share anonymous usage?, and turning it off stops them and deletes any report not yet sent.

In Pose Guide: accounts and settings

10. Firebase Authentication, with Sign in with Apple and Google Sign-In: accounts

• Company: Google LLC (Firebase Authentication and Google Sign-In); Apple Inc. (Sign in with Apple, part of iOS)
• Privacy and security in Firebase: https://firebase.google.com/support/privacy
• Privacy policy: https://policies.google.com/privacy
• Sign in with Apple: https://support.apple.com/en-us/102609

What it is. The Google service that holds Pose Guide's accounts for us. Pose Guide's account lets the app use its server functions and keeps your purchases with you.

What it receives: the first time Pose Guide opens, a request to make an account, with no name, email address or password. It issues a random account ID and records when the account was made and last used. Like any server, it sees the network address a request comes from, and Firebase keeps those for a few weeks. Only if you choose to sign in, in Settings → Account: with Apple, the email address Apple gives (often a private relay address) and your name if you share it; with Google, your Google account's email address, name and the link to its profile picture. Google Sign-In shows Google's own sign-in page, so Google knows you signed in to Pose Guide.

What it never receives: your photos, your words, your location or your usage. Pose Guide sends the email address nowhere else and shows it only in Settings.

How long: until you delete the account with Delete my account; Firebase then removes it from its systems within 180 days.

How to stop it: the account is how the app reaches its server functions, so it cannot be switched off. Signing in is optional. Sign out starts a new, empty account on the iPhone and leaves the signed-in one at Firebase; Delete my account deletes the account you are using at Firebase and revokes Sign in with Apple.

11. Firebase Remote Config: the app's settings

• Company: Google LLC
• Privacy and security in Firebase: https://firebase.google.com/support/privacy

What it is. The Google service that delivers the settings Pose Guide runs with, so we can change them without a new version of the app.

What it receives, at each launch: a random Firebase installation ID, the app's version, and the iPhone's language, region and time zone. Nothing about you or your account.

How long: Google keeps the installation ID until we ask it to delete it. Delete my account does not remove it, and nothing links it to you.

How to stop it: it is part of how the app runs and carries nothing about you. Without it, Pose Guide uses the settings built into the app.

In Pose Guide: example photos

12. xAI: example photos of a place

• Company: SpaceXAI LLC, which makes xAI's Grok
• Terms for the service we use: https://x.ai/legal/terms-of-service
• Privacy policy: https://x.ai/legal/privacy-policy

What it is. When you allow Example photos for where you are?, Pose Guide shows example photos for the place you are at. For a well-known place they were made ahead. For a place not on Pose Guide's list, our server asks xAI's Grok to make three.

What it receives, for each photo: a description of the photo to make, with the place's name and the kind of place in it, and the photo's shape. Nothing about you: not your location, your account ID, your words or a frame from the camera. The request comes from our server.

What xAI does with it is set by xAI's terms above. The photos come back to our server, which keeps them with the place's name and country and shows them to anyone at that place.

How to stop it:

1. Choose Not now when Pose Guide asks. Ideas then shows only the ideas that come with Pose Guide.
2. Settings → Example photos in Pose Guide, behind the gear at the top of the camera, turns it off at any time.

Payment data

We never receive it. Apple or Google — the store you bought from — processes every payment, and we do not see and cannot store your card number, bank details or billing address. Refunds are handled by the store you bought from — Apple at https://reportaproblem.apple.com, Google at https://play.google.com/store/account.

Keeping this page true

If we add a provider, enable a mediated ad network, change where analytics is hosted, or change what any provider receives, this page changes in the same release and the "Last updated" date moves. A partners page that lags the binary is the failure this page exists to prevent.

Questions: [email protected]

← Back to the Privacy Policy

Change log

• October 25, 2026 · rev 15: The Meta Pixel is on five more ad landing pages, for Cupshot, Tall Order, Swingaroo, Launch Lab and Parcel Yard. What it receives is unchanged.
• October 25, 2026 · rev 14: Angle is now called Pose Guide. Its partners and what they receive are unchanged. Its delete button is now called Delete my account.
• October 24, 2026 · rev 13: Angle moves to Google's Firebase. Its usage events go to Google Analytics for Firebase in place of our own server, and crash reports go to Firebase Crashlytics, both only after you say yes on Share anonymous usage?. Its account is held by Firebase Authentication, made at first launch with no name or email, and you may sign in with Apple or Google in Settings (Section 10). Its settings come from Firebase Remote Config (Section 11). The table's Angle column changes to match and gains two rows. xAI is added (Section 12, and a row in the table): it makes Angle's example photos of a place from the place's name, and was named only in Annex F of the Privacy Policy before. The opening paragraph names ten services. Google Sign-In is the one social-login SDK in our apps. RevenueCat's customer ID in Angle is now the Angle account ID. No other app's partners changed.

• October 21, 2026 · rev 12: Google Analytics for Firebase and Firebase Crashlytics are added, for one app, Launch Lab. Sections 8 and 9 say what each receives and how to stop it: Settings → Share usage analytics, on by default, turns off Google Analytics at the app, and crash reports are separate. Neither receives the account identifier, a name, an email address or anything typed, and no advertising identifier is collected. The table gains a Launch Lab column: no PostHog, no AppsFlyer, no ad SDK, RevenueCat for purchases, and Google for analytics and crash reports. No other app's partners changed.

• October 11, 2026 · rev 10: A cookie notice on nomadarcade.com. Its Decline stops the Meta Pixel at once and keeps it from loading on later visits, and Cookie settings, at the foot of each page that has the notice, changes the choice. Section 7 adds both to when the pixel does not run and how to stop it. No partner changed, in the apps or on the site.

• October 10, 2026 · rev 9: The Meta Pixel is added, for nomadarcade.com only. It runs on the page for each game we advertise on Facebook and Instagram, today the Cannon Clash page. Section 7 says what it receives, when it does not run and how to stop it. No app's partners changed.

• September 29, 2026 · rev 8: Google's Gemini API is added, for one app, Angle, and only after you agree. It writes Angle's photo plan when an iPhone cannot plan a shot on its own, from what you said (names taken out) and one small frame. Section 6 says what it receives, that Google keeps a request for 55 days only to check for misuse, and how to turn it off. The table gains an Angle column: no PostHog, no AppsFlyer, no ad SDK, RevenueCat for purchases, and a RevenueCat customer ID that is the guest account's random identifier. No other app's partners changed.

• September 3, 2026 · rev 5 — Revised with the suite, which carries one date across all four documents. No partner, no data category, no purpose and no opt-out route changed on this page. The change that prompted the revision is Parcel Yard's optional email / Apple ID sign-in (Privacy Policy §2.4), and an address attached that way is never sent to any partner named here.

• September 1, 2026 · rev 4 — Hosting move only. This page is now published at https://legal.alc.fyi/legal/partners.html, and every URL on it points at that host. No partner, no data flow and no opt-out route on this page changed, and the contact is still [email protected].
• September 1, 2026 · rev 3 — Publisher rename only. Intentionally Creative (get-creative.co), contact [email protected], page hosted under the studio's own domain (superseded at rev 4). No partner, no data flow and no opt-out route on this page changed.
• September 1, 2026 · rev 2 — Added one clarification only: our own server is not on this page because it is ours, not a third party's, and nothing it holds reaches any of the four services named here. No partner, no data flow and no opt-out route on this page changed.
• September 1, 2026 · rev 1 — First draft of the suite.