Intentionally Creative — Privacy Policy

Last updated: October 25, 2026 · rev 15

Alden Morris Enterprises LLC, a New York limited liability company, trading as Intentionally Creative ("Intentionally Creative," "we," "our" or "us"), respects the privacy of the people who use our apps and visit our website, and is committed to protecting it through compliance with this Privacy Policy ("Privacy Policy"). This Privacy Policy does not address the privacy practices of any third party we do not own or control.

Please read this Privacy Policy together with the terms that govern your use of the apps. On Apple platforms those are Apple's Licensed Application End User License Agreement, available at https://www.apple.com/legal/internet-services/itunes/dev/stdeula/.

By downloading or using our apps, you agree that we will collect and process personal information in accordance with this Privacy Policy. If you are not comfortable with any part of it, please stop using the apps.

Our apps are not intended for children. If you are a minor — under 16 in the European Union and the United Kingdom, under 13 in the United States, or under the minimum age at which you can consent to data processing where you live — you must not download or use our games or provide any personal information to us. Milestone has a stricter rule, because it is a family planning app: the person who installs it and owns the plan must be an adult. See Section 9 and Annex D. Pose Guide's cloud recipe has one as well: Google, which writes those plans, requires the people using it to be 18 or older. See Section 9 and Annex F.

The short version

Everything below is the long form of seven sentences.

1. None of our apps asks you to sign up. There is no sign-in screen in front of anything, no password to choose and no profile to fill in. What each app has instead is an anonymous device account — a random identifier kept in your phone's keychain, created without asking you for anything — and its only job is to let the app store a copy of your own data for you and hand it back to the same phone. In Parcel Yard you may optionally attach an email address or your Apple ID to that same account, from Settings and never on the way in, so that your game can be opened on a different phone; if you do, that address is the one personal detail we hold, it is deleted with the account, and nothing about the game changes either way. In Pose Guide you may optionally sign in with Apple or Google, also from Settings and never on the way in, so that your purchases follow you to a new iPhone; Pose Guide's accounts are held for us by Google's Firebase, which then keeps the email address, and your name if you share it, that the sign-in gives (Annex F). Apart from a Pose Guide sign-in, we never learn your name.
2. The thing you make lives on your phone, and some of it is copied to a server we run ourselves. In the two games that copy is your game progress. In Before I Unpack it is your records and photographs, and only if you switch Backup on — it is off until you do. In Milestone it is the plan. In Pose Guide nothing is copied: your photos stay on your phone. The server is our own machine, operated by us; no third-party cloud service holds any of it. Section 2.4 and the annexes say exactly what is copied in each app, and what never is.
3. What does leave is a closed list of counted events — screens opened, levels finished, a purchase completed — with no free text, no names, no amounts and no photographs in them. Every app enforces that list in code before an event reaches any provider. The exceptions are Launch Lab and Pose Guide, where Google Analytics for Firebase also records its own automatic events, among them each in-app purchase with its price, read from the App Store, and crash reports go to Firebase Crashlytics (Annexes E and F). In Pose Guide both wait for your yes.
4. Our two games show ads. Our two utility apps show none, ask no tracking permission, and contain no advertising SDK at all.
5. You can turn analytics off in every app, and "Delete everything" in each app's settings deletes both what is on the phone and what your account owns on our server. It asks the server first and refuses to wipe the phone if the server delete fails, so it can never tell you something is gone while it is still here.
6. One app can send what you said and one photo to another company, and only after you agree. On an iPhone that cannot plan a shot on its own, Pose Guide asks once, on a screen that names Google, before it sends your words (with names taken out) and one small frame from the camera to Google's Gemini API to write the photo plan. We store none of it. Google keeps it for 55 days to check for misuse and does not use it to improve its products. Annex F has the detail.
7. Our website nomadarcade.com sets cookies, and its ad landing pages carry the Meta Pixel. The page for a game we advertise on Facebook and Instagram (today, nomadarcade.com/cannon-clash, /thunk, /sky-chase, /scoot, /cupshot, /tall-order, /swingaroo, /launch-lab and /parcel-yard) tells Meta it was opened and when an App Store button is tapped, and sets two Meta cookies, so Meta can report which of our ads worked. Our own analytics records how the site's pages are used, with anything typed hidden. A cookie notice lets you decline both. For a device set to a European time zone the pixel never loads, and our analytics stores nothing on the device unless you accept; a browser that sends Global Privacy Control gets neither. Section 2.5 has the detail.

Two promises we hold ourselves to by name, because they are the reason those two apps exist:

Before I Unpack: nothing leaves your phone until you switch Backup on, and Backup starts off. With it off there is no account, no session and no request of any kind. Switch it on and your records and photographs are copied to our own server — encrypted on the way there and encrypted at rest, but not end-to-end encrypted: we hold the keys, which is what the app itself says on the screen where you turn it on. Your key codes and the message you wrote to your landlord are never uploaded in either state. Anonymous usage analytics in that app is also off unless you turn it on.

Milestone: names, amounts, notes and photographs never appear in analytics. Not "we would not send them" — the app filters every event against an allowlist of permitted properties before any provider sees it, and anything not on that list is dropped. That is a promise about analytics, and only about analytics. The plan itself, names and photographs included, is stored on our own server so the owner's phone can get it back. Storing your plan for you and sending a counted event to an analytics provider are two different acts with two different rules, and Annex D keeps them apart.

Contents

1. Scope and Applicability
2. Personal Information That We Collect
3. Why We Collect Your Personal Information
4. How We Disclose Your Personal Information
5. Your Rights and Choices
6. Security
7. Transfers of Your Personal Information
8. Retention of Personal Information
9. Children
10. Changes to This Privacy Policy
11. Contact Us
12. Additional Notice to Individuals in the United States
13. Additional Notice for California Consumers: California Notice at Collection
14. Additional Notice to Individuals in the European Economic Area, United Kingdom, and Switzerland
15. Additional Notice to Individuals in Brazil

• Annex A — Parcel Yard
• Annex B — Pack Perfect
• Annex C — Before I Unpack
• Annex D — Milestone
• Annex E — Launch Lab
• Annex F — Pose Guide

1. Scope and Applicability

This Privacy Policy applies to personal information we collect when you:

• use our mobile applications that link to this Privacy Policy — Parcel Yard, Pack Perfect, Before I Unpack, Milestone, Launch Lab and Pose Guide (collectively, the "Apps");
• visit websites we own or operate that link to this Privacy Policy, including nomadarcade.com (the "Sites"); or
• contact us by email at support@get-creative.co.

The Apps and the Sites are together the "Services."

What the Sites collect, including their cookies and the Meta Pixel, is in Section 2.5. get-creative.co has its own privacy policy, at https://get-creative.co/privacy-policy. Some games we publish as Nomad Arcade, such as Cannon Clash: Tiny Worlds, have a privacy policy of their own, linked from their App Store page. That policy covers the game itself; this one covers the game's page on our website.

The per-app annexes are part of this policy. Our six apps do genuinely different things with data, and the annex for the app you are using is the specific, binding statement for that app. Where an annex is narrower than the common sections, the annex governs.

2. Personal Information That We Collect

The sections below list the categories of personal information that may be collected across the Services. Not every category applies to every app — which categories apply to which app is set out in the annexes, and an app that does not contain a provider collects nothing through it.

2.1 Information you voluntarily provide us

Almost nothing, because no app asks you to register. None of them has a sign-up form, and none of them has a field for who you are.

• Correspondence. If you email support@get-creative.co, we receive your email address and whatever you write to us, and we keep it long enough to answer you and to keep a record of the request.
• App settings and preferences. Your language, sound and gameplay preferences are stored on your device; in the two games they also travel with the cloud save, so a new phone plays the way the old one did. Your analytics choice is stored on the device only and is never uploaded.
• The content you put into Before I Unpack and Milestone, in the circumstances Section 2.4 sets out. You give it to the app, and the app copies some of it to our server.
• Your email address and name, if you sign in to Pose Guide with Apple or Google in Settings. The sign-in gives them to Google's Firebase, which holds Pose Guide's accounts for us. With Apple the email is often a private relay address, and the name is there only if you share it (Annex F).
• What you say to Pose Guide, and one frame from its camera, only if you allow cloud recipes. They pass through our server to Google, which writes the photo plan, and we store none of it (Annex F). Pose Guide's photos themselves stay on your phone.

Apart from that Pose Guide sign-in, we do not ask for, and the Apps have no field for, your name, postal address, phone number, date of birth, or a photograph of you. Names, phone numbers, addresses and photographs that you type or take inside an app — the people in a Milestone court, the address of the flat in Before I Unpack — are Section 2.4's subject rather than this one: we never ask for them, we never use them to identify you, and they are never sent to an analytics provider or an advertiser.

2.2 Information collected automatically

• Your anonymous account identifier. When an app creates its anonymous device account (Section 2.4), our server issues a random user id (in Pose Guide, Google's Firebase issues it for us) and the app keeps it on your phone. Every row and every file the app stores for you is owned by that id, and the database refuses to hand one account's rows to any other. It carries no name, no email address, no password and no profile, and there is nothing in it from which we could work out who you are.
• Pseudonymous provider identifiers. Each analytics or attribution provider in an app generates its own random, device-local identifier (a PostHog "distinct id," an AppsFlyer ID, a RevenueCat anonymous app user ID, in Launch Lab and Pose Guide a Google Analytics for Firebase app-instance ID and a Firebase Crashlytics installation ID, and in Pose Guide the Firebase installation ID that Remote Config fetches the app's settings with). In Pose Guide, RevenueCat's customer ID is your Pose Guide account ID, so our server can tell what you bought, and if you signed in, that account also holds your email address (Annex F). Apart from that, none of them is connected to a name, an email address or your account identifier.
• Device identifiers. On Apple devices, the vendor identifier (IDFV) and, in our two games only and only if you allow tracking when asked, the advertising identifier (IDFA). On Android devices, the equivalent is the Google Advertising ID (GAID), and again only in our two games. Our two utility apps disable advertising identifiers at the SDK level before the SDK starts and never read the IDFA — and on Android they go further: the advertising-ID permission is removed from the app entirely, so a utility app of ours cannot read the Google Advertising ID even if a component inside it tried to.
• Device and system information. Operating system and version, device model, time zone, language and country/region setting, app version.
• Coarse, country-level location. Advertising and attribution providers in our games derive an approximate country or region from your IP address, and in Launch Lab, and in Pose Guide after your yes to usage, Google Analytics for Firebase derives a coarse region from it, as fine as the city. No app receives precise or GPS location. Only Pose Guide asks for a location permission, when you first keep a photo, and that location never leaves your phone (Annex F). In Before I Unpack and Milestone we disable the analytics provider's own IP-based location lookup.
• Product interaction events. A closed, named list of events per app — screens viewed, a level finished, a record exported, a paywall seen, a purchase started or completed. The full list for each app is in that app's annex.
• Crash reports (Launch Lab, and Pose Guide after your yes). When one of them crashes, Firebase Crashlytics receives the stack trace and the state of the device and its operating system, under a random Crashlytics installation ID (Annexes E and F).
• Advertising events (games only). Ad requests, impressions, clicks and the revenue an impression produced.
• Purchase records. Product identifier, transaction identifier, whether the entitlement is active. Apple or Google — the store you bought from — and not us, processes the payment; we never see your card number, bank details or billing address. On Android the record we receive is the Google Play purchase token; on Apple devices it is the App Store receipt.

2.3 Information we receive from third parties

• Apple or Google, and RevenueCat tell us that a transaction occurred, which product it was for, and whether the resulting entitlement is active or refunded.
• AppsFlyer tells us, at the level of a marketing campaign and never at the level of a person, that installs came from a particular campaign. On Apple devices this runs through Apple's SKAdNetwork, which returns aggregated postbacks that contain no user identifier by design. On Android there is no SKAdNetwork; attribution uses the Google Play Install Referrer, which tells us which campaign a download came from and carries no identifier of you.

We do not buy personal information from data brokers, and we do not upload customer lists to advertising platforms to build custom or lookalike audiences.

2.4 Your account, our server, and what is stored on it

This is the most important section in this policy, and it is the one that changed in this revision. Read it before the annexes.

The account. Each app can create an anonymous device account for you. It is created silently, without a screen and without asking you for anything, because there is nothing to ask for: no email address, no password, no username, no profile, no phone number, no photograph of you. It is a random identifier that lives in your phone's keychain. When it is created differs by app, and the difference is deliberate:

Attaching an email address, if you want to (Parcel Yard). The account above belongs to this phone: it survives deleting and reinstalling the app, and it does not survive losing the phone. Parcel Yard therefore offers one optional upgrade, in Settings → Cloud save and nowhere else — never on the way in, never as a wall in front of the game, and never as a condition of anything. You may attach an email address (we email you a link; there is no password to choose) or your Apple ID (Sign in with Apple, where you may use Apple's own private relay address and we never see your real one). If you do:

• the account keeps the same identifier, so every board you have already cleared stays yours — nothing is copied to a new account;
• the address is the only personal detail we hold, we use it for exactly one thing, which is letting you open your own save on another phone, and we never send you marketing;
• it is deleted with everything else by Settings → Delete everything;
• if you never use it, nothing above changes and the app never asks again.

Signing in, if you want to (Pose Guide). Pose Guide's account belongs to this iPhone until you sign in. In Settings → Account you may sign in with Apple or Google, never on the way in, so that your purchases follow you to a new iPhone. The account keeps the same identifier. Google's Firebase then keeps the email address the sign-in gives (with Apple, often a private relay address), your name if you share it, and with Google, the link to your Google profile picture. Pose Guide shows the email in Settings and sends it nowhere else, and Delete my account deletes the account at Firebase (Annex F).

The server. It is our own server infrastructure, operated by us: our own machine, running the open-source Supabase software we host ourselves, in a data center in Ashburn, Virginia, United States. It is not a third-party "backend as a service", nothing is stored at supabase.com, and no other company holds your rows. Each app has its own database schema and its own private file bucket, and every table and bucket refuses to return anything to any account except the one that owns it.

What is stored on it, per app:

• Parcel Yard and Pack Perfect — your game progress, and your friends code. The friends program (Terms §8.6) also stores your share code, a private value that generates it, and a link between your account and each friend who entered it, with the date and what was granted. Boards cleared and their results, coins and stars, streaks, daily runs, album and postcard entries, unlocks and cosmetics, how you have arranged your yard or room, and which purchase is active. No photographs and no content of yours, because these games take none from you.
• Before I Unpack — nothing at all, unless you switch Backup on. With Backup on: your places and their addresses, your records, rooms, meter readings, key-set counts, inventory, the notes you wrote, and the original photographs and voice notes. Never uploaded in any state: your key codes, and the message you wrote to your landlord.
• Milestone — the owner's plan. The event, the people in it with their names and phone numbers, the court and the padrinos, the sequence, the decisions, rehearsals, day-of items, the thank-you list, and the photographs you add. Money — amounts, budget items, totals and vendor quotes — is stored in separate tables the honoree's side cannot reach; that is why it is a separate table rather than a column, because a fence around a column is not something a database can enforce.
• Pose Guide: no content of yours. A copy of your purchases, under your Pose Guide account ID; a count of today's cloud plans, kept under a one-way hash; and, once you have deleted your data, a one-way hash of the deleted account ID. The account itself is held by Google's Firebase. Your photos and what you say are never stored on our server.

What never reaches the server in any app: your analytics choice; Before I Unpack's key codes and landlord message; in Milestone, the settings that belong to that phone rather than to the event; and in Pose Guide, the photos you take. (The one small frame a Pose Guide cloud recipe sends passes through our server on its way to Google and is not stored.)

None of this is analytics. Analytics is Section 2.2's closed list of counted events, and no photograph, name, amount or note is ever in one. This policy never uses one of those two things to describe the other.

Consistent with that, in every app:

• Session replay is off. It would record the screen, and the screen contains your content.
• Autocapture and vendor lifecycle events are off. They would send text read off the interface, which is outside the app's declared event list. The exceptions are Launch Lab and Pose Guide, where Google Analytics for Firebase records its own automatic events, such as first open, session start, user engagement and in-app purchases (Annexes E and F); in Pose Guide, only after your yes.
• Event properties are limited to a declared allowlist. No event carries free text, a name, an amount, a note, a file path or a photograph. The exception is the in-app purchase event Google Analytics for Firebase reads from the App Store in Launch Lab and Pose Guide, which carries the product and its price.

2.5 Our websites: the Meta Pixel and cookies

This section covers the Sites, nomadarcade.com (Section 1). Nothing on them asks you to sign in or to type anything about yourself. The session-replay and autocapture rules in Section 2.4 are rules for the apps; this section sets out what the Sites do.

The Meta Pixel, on our ad landing pages. 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/) loads the Meta Pixel, a script from Meta Platforms, Inc. No other page on nomadarcade.com loads it. It sends Meta:

• that the page was opened, and which game it is about;
• each tap on a button that leads to the App Store, 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 address of the page, including the campaign tags and Meta's click identifier in the link you followed, and the address of the page that sent you;
• your IP address, what your browser and device report about themselves, and your screen size;
• the identifiers in the _fbp and _fbc cookies described below.

Meta uses this to tell us how many visits and App Store taps each of our ads produced, to show our ads to people more likely to want the game, and for its own purposes under its privacy policy (https://www.facebook.com/privacy/policy/). Meta can link these events to a Facebook or Instagram account you are signed in to. We receive counts and campaign results from Meta and never learn who you are. Meta's automatic matching of email addresses and phone numbers is off on our pixel, and our pages have no field to type one into.

What the Sites store on your device:

Meta can also read and set cookies on its own domains, such as facebook.com and instagram.com, under its cookies policy (https://www.facebook.com/privacy/policies/cookies/). Our pages set no other cookie. The Sites are delivered through Cloudflare, which handles each request, including your IP address, to serve the page and protect the site; it sets no cookie on our pages.

Our own analytics. Our pages on nomadarcade.com run Lens, an analytics service we operate ourselves: the home page, each game's page, our ad landing pages and the pages that hold our policies. It records how a page is used: which parts were on screen and for how long, which buttons you saw and tapped, scrolling, how fast the page loaded, errors, the page that sent you, the campaign tags in the link, and your device type and screen size. It also keeps a replay of the visit, a recording of the page as you saw it with your scrolling and taps, and anything typed into a field is hidden before the recording leaves your device. It reads your IP address to block abusive traffic and does not save it with your visit. It sends nothing to Meta or to any advertiser. Visit records are kept on our own server in the United States, and replays with our storage provider, Hetzner, in Germany.

The cookie notice. The first time you open a page that runs our analytics, a small notice says what the page records, with a link to this section.

• Outside Europe, our analytics, and the Meta Pixel on an ad landing page, are already running when the notice appears. OK keeps them on. Decline stops them: our analytics stops the replay, deletes its visitor number and current visit from your device, and from then on sends nothing; the Meta Pixel is told to stop sending anything to Meta, and it does not load on your later visits. What the pixel stored before you declined (its cookies and multiFbc) stays until it expires or you delete it, and our pages send Meta nothing more.
• For a device set to a time zone in the European Union, the EEA, the United Kingdom or Switzerland, the notice asks first. Our analytics keeps nothing on your device and no replay until you choose Accept, and the Meta Pixel does not load even then. Decline keeps it that way.

Your choice is kept in your browser's local storage as cookie-consent, and the notice does not come back while it is there. The notice sets no cookie. To change your choice, use Cookie settings at the foot of any page that has the notice.

Europe and Global Privacy Control. If your device is set to a time zone in the European Union, the EEA, the United Kingdom or Switzerland, the Meta Pixel does not load and sets no cookie, and our analytics stores nothing on your device and keeps no replay unless you choose Accept on the notice. If your browser sends the Global Privacy Control signal (https://globalprivacycontrol.org/), the Meta Pixel does not load and our analytics stores nothing and keeps no replay, whatever you chose; the notice and Cookie settings do not appear, because there is nothing left to choose. Under Global Privacy Control, and after a Decline, our analytics sends nothing. On a device set to a European time zone, before you answer the notice, our analytics counts the visit anonymously, with no identifier kept on your device.

How long. The _fbp and _fbc cookies last 90 days. Meta keeps what the pixel sent under its own policy. Our analytics deletes replays after 90 days and visit records after 400 days, and keeps only totals with no visitor in them, such as how many visits reached a section.

Your choices:

1. Choose Decline on the cookie notice, or later under Cookie settings at the foot of any page that has the notice. It stops the Meta Pixel and our analytics as described above.
2. Turn on Global Privacy Control in your browser, where it is offered. Our Sites honor it as described above.
3. Block or delete cookies and site data for nomadarcade.com in your browser's settings, or use a private window.
4. Change how Meta uses activity from other websites for the ads it shows you, in your Meta ad settings: https://www.facebook.com/adpreferences/ad_settings.
5. Email us at support@get-creative.co.

3. Why We Collect Your Personal Information

• Operate and administer the Apps. Run the app, keep your progress, deliver what you purchased and restore it on a new device.
• Hold your copy for you, so the app can give it back. Keep on our server what Section 2.4 describes, and return it to your phone after a reinstall. In Before I Unpack this happens only because you switched Backup on; in Milestone and the games it is how the app keeps what you made.
• Plan your photo (Pose Guide). When your iPhone cannot plan a shot on its own and you have agreed, send what you said and one frame to Google to write the plan.
• Provide customer support. Answer the email you send us.
• Send you service-related communications. If we have your email address because you wrote to us, we may reply and may tell you about a material change to these documents. We do not run a marketing mailing list from app data, and an email address an app holds for sign-in (Parcel Yard, Pose Guide) is used only to sign you in.
• Understand and improve the Apps. Count how many people finished a level, exported a document or reached a screen, so we know what to fix and what to build. This is aggregate, pseudonymous and property-limited.
• Measure our advertising. Learn, at campaign level, which marketing produced installs, so we do not spend money on advertising that does not work.
• Run and measure our Sites. See how our pages are used so we can make them faster and clearer, and learn which of our ads bring visitors and App Store taps (Section 2.5).
• Show advertising (games only). Fill the ad placements in Parcel Yard and Pack Perfect, and — only if you allowed tracking — make those ads more relevant.
• Keep the Apps and our business secure. Detect fraud, abuse and technical failure.
• Comply with law. Meet our tax, accounting and legal obligations and respond to lawful requests.
• Corporate transactions. Handle a merger, acquisition or sale of the business (Section 4).
• With your consent, for any other purpose we describe to you at the time.

We do not use your personal information to make automated decisions that produce legal or similarly significant effects about you.

4. How We Disclose Your Personal Information

• Nobody, for the content in Section 2.4 — with one ordinary exception, stated here so it is not a surprise. What an app stores on our server stays on our server. It is not sent to an analytics provider, an advertising network, another company's cloud or anyone else, and we do not read it to build products, train models or sell anything. The exception is infrastructure: our machine sits in a rented data center, and the nightly backups described in Section 8 are held by two object-storage providers. Those companies hold encrypted copies under contract, act only on our instructions, and are not permitted to use them for anything of their own.
• Service providers. The analytics, crash-reporting, attribution, advertising-mediation and purchase providers named in Section 2 and in the annexes (in Launch Lab, Google, for Google Analytics for Firebase and Firebase Crashlytics; in Pose Guide, Google, for Firebase Authentication, Google Analytics for Firebase, Firebase Crashlytics and Remote Config), plus ordinary business vendors (email, accounting, legal). They may use the information only to provide the service to us. The full list, with the data each one receives and a link to its own privacy policy, is at https://legal.alc.fyi/legal/partners.html.
• Google, for Pose Guide's cloud recipes, and only after you agree. Your words, with names taken out, and one small frame go from our server to Google's Gemini API, which writes the photo plan. Google processes them as our processor under its data processing terms for the paid service (https://business.safety.google/processorterms/), does not use them to improve its products, and keeps them for 55 days only to detect misuse (Annex F).
• xAI, for Pose Guide's example photos, and only after you agree. For a place not on Pose Guide's list, our server sends xAI's Grok the place's name inside a description of the photo to make, and Grok makes three example photos. Nothing about you goes with it (Annex F).
• Advertising partners — in our two games only. AppLovin MAX mediates our ad placements and passes an ad request to the advertising networks bidding on it. Those networks receive device and ad-event information and, if you allowed tracking, your advertising identifier. Under the broad definitions in some United States state privacy laws, this may be a "sale" or "sharing" of personal information. See Sections 12 and 13 for how to opt out. Our two utility apps contain no advertising SDK, so nothing of this kind happens in them.
• Meta, from our ad landing pages. The Meta Pixel sends Meta what Section 2.5 lists. Meta uses it to measure and deliver our ads and for its own purposes under its own policy. Under the broad definitions in some United States state privacy laws, this may be "sharing" of personal information. Section 12.3 says how to opt out.
• Merger, acquisition, or other business transaction. If we are acquired or sell substantially all of our assets, information may transfer to the acquirer. We will require the acquirer to remain subject to this Privacy Policy, or to obtain your consent.
• Professional advisors. Lawyers, accountants, auditors and insurers, where necessary for them to advise us.
• Legal obligations and safety. Where reasonably necessary to comply with valid legal process or a request from a public authority; to comply with law; to enforce our Terms; to protect our legal interests; or to protect the rights, property or safety of you, our users or others. Where we are legally permitted to do so, we will give you notice before disclosing your information in response to a demand.
• With your consent, to anyone else you direct.

We do not disclose personal information to co-sponsors, promotion partners or social platforms for their own marketing. The Meta Pixel on our ad landing pages is our one flow to a social platform, and it is there to measure and deliver our own ads (Section 2.5). We run no promotions, sweepstakes or contests. The one social sign-in, Sign in with Google in Pose Guide, is optional and used only to sign you in (Annex F).

5. Your Rights and Choices

5.1 Your privacy rights

Depending on where you live, you may have the right to:

• Know / access — obtain a copy, or a list of categories, of personal information we hold about you.
• Correct / rectify — have inaccurate personal information corrected.
• Delete / erase — have personal information we hold about you deleted.
• Portability — receive personal information in a structured, commonly used, machine-readable format.
• Restrict or object — limit or object to certain processing.
• Opt out of "sale," "sharing" or processing for targeted advertising.
• Non-discrimination — not be treated worse for exercising a right.
• Appeal a refusal, where your state or country provides that right.

5.2 The honest limit on access and deletion requests

We want to be exact about this rather than promise a process we cannot run.

We still hold no record we can look you up in. Your account has no email address, no password and no profile, so nothing on our side maps a row to a person. If you write to us from an email address, we cannot tell which account — if any — is yours, and we will not guess: matching a stranger's email address to somebody's photographs would be the worse of the two failures available to us.

If you signed in to Pose Guide with Apple or Google, Google's Firebase holds that account's email address for us. Write from that address (with Apple's private relay, the address Pose Guide shows in Settings) and we can find the account.

Your phone can do what we cannot, and that is the design rather than an excuse. The account identifier lives in your phone's keychain, so the app is authenticated as you and as nobody else:

1. Use the delete in the app — Section 5.4. It removes what is on the phone and the rows and files your account owns on our server, because the app is signed in as that account at the moment it asks.
2. Take a copy without involving us. Before I Unpack exports the whole record as a PDF and Milestone's Export everything / Exportar todo hands you the whole plan as a file, both on the device.
3. Give us the pseudonymous identifier if you want analytics events already sent to be removed. Every app can show you its analytics identifier on request via support@get-creative.co, and with it we will ask our analytics provider to delete the associated event stream. Without it there is nothing for either of us to point at.

If you want us to act on one of the rights in Section 5.1 and the routes above do not cover it, email us anyway and we will tell you honestly what we can and cannot do from our side.

To make any request, email support@get-creative.co with the subject line "Privacy Rights Request." We will respond within the period the applicable law allows. Where the law requires us to verify your identity before acting, we will ask for what we need and no more; where there is nothing to verify against, we will tell you so instead of asking for a copy of your ID.

Your rights are not absolute. We may decline a request where the law requires or permits us to, where granting it would harm another person's privacy, or where it has no legal basis.

5.3 The switches in the apps

5.4 Deletion

Every app has a destructive delete in its own settings, and it does what it says: it erases the app's saved content, its settings and the analytics bookkeeping stored on the device, and it deletes what your account owns on our server — the rows, and the files in that app's bucket — by calling a server-side delete_account routine that runs as your own account.

The order is server first, then phone. If the server delete fails, nothing on the phone is touched and the app tells you so, because an app that reported a deletion it had not performed is exactly the failure this path exists to prevent. Milestone goes one step further and reads the plan back afterwards, refusing to call it deleted while a row is still there.

One thing survives, and it holds nothing about you. The anonymous identity row itself — the empty account record, with no email address, no name and no profile in it — remains in the authentication system. Everything it owned is gone; the row is left because removing it is a separate operation and it contains no personal information to remove. Launch Lab deletes the account itself from our sign-in system (Annex E). In Pose Guide the account itself is deleted at Google's Firebase as well, with any email address and name a sign-in gave it (Annex F).

It cannot be undone and we cannot recover anything for you afterwards. If something matters to you, export it first.

It does not cancel or refund a purchase. An App Store purchase belongs to your Apple ID and a Google Play purchase belongs to your Google account; "Restore purchases" will bring it back on any device signed in to the same one. Refunds are handled by the store you bought from and not by us — Apple at https://reportaproblem.apple.com, Google at https://play.google.com/store/account.

Full per-app instructions: https://legal.alc.fyi/legal/deletion.html.

6. Security

We use commercially reasonable administrative, technical and physical safeguards to protect personal information against unauthorized access, alteration, disclosure or destruction. Concretely:

• Everything is encrypted in transit between an app and our server.
• Every table and every file bucket is fenced to one account. The database refuses to return a row, or a file, to any account but the one that owns it, and that is enforced by the database itself rather than by the app asking politely. We test it on the live server with two accounts that try to read each other's rows.
• No key with administrative power is ever inside an app. The only key an app ships with is a public one that grants nothing on its own.
• Files are encrypted at rest on our server, and the private buckets are not readable without an authenticated request from the owning account.

What we do not claim: this is not end-to-end encryption. We hold the keys. That means we could in principle be compelled to hand over what is stored, and it means a breach of our server would be a breach of the content on it. Before I Unpack says exactly this, in its own words, on the screen where you switch Backup on, and this policy will not say anything softer than the app does. If that is not acceptable to you, leave Backup off — that app works completely without it.

No system is perfectly secure, and we cannot guarantee absolute security. We are not responsible for the security of information transmitted over networks we do not control. If you believe an interaction with us is no longer secure, tell us at support@get-creative.co.

7. Transfers of Your Personal Information

The limited data described in Section 2 is processed by providers that operate internationally, and it may be processed in the United States, the European Union and other countries where our providers maintain facilities. Those countries may have data protection laws that differ from those where you live.

Our own server is in the United States. The content Section 2.4 describes — your game progress, a Before I Unpack backup, a Milestone plan — is stored on our machine in a data center in Ashburn, Virginia. Wherever you are, that is where it is, and it is not moved anywhere else. We are a United States company and our apps are not offered in the EEA, the United Kingdom, Switzerland or Brazil. That is why no transfer mechanism for those regions is named here: there is no transfer to describe. Before any release in one of them we will state the mechanism that applies, name a representative under Section 14.1, and publish both in this policy first.

Pose Guide's cloud recipes go from our server to Google, which may store them transiently or cache them in any country where Google or its agents keep facilities, and keeps them for 55 days to check for misuse (Annex F).

Our Sites. The Meta Pixel sends its data to Meta, which processes it in the United States and other countries. Our own analytics keeps visit records on our server in the United States and replays with our storage provider in Germany (Section 2.5).

Specifically, at the date of this policy: our product analytics for Parcel Yard, Pack Perfect and Before I Unpack is hosted in the European Union (PostHog EU Cloud), and for Milestone in the United States (PostHog US Cloud). Our attribution, advertising-mediation and purchase providers operate across multiple regions, and so does Google, which runs Launch Lab's Google Analytics for Firebase and Firebase Crashlytics, and Pose Guide's accounts, Analytics, Crashlytics and Remote Config on Firebase.

If you are in the EEA, the UK or Switzerland, see Section 14 for the transfer mechanisms we rely on. If you do not want your information transferred outside your country, stop using the Services and turn off analytics in the app.

8. Retention of Personal Information

We retain personal information only as long as needed for the purposes in this policy, or as required to meet legal obligations, resolve disputes and enforce our agreements.

In practice:

• Content you create in an app is retained on your device for exactly as long as you keep it, and is destroyed the moment you use "Delete everything."
• The copy on our server (Section 2.4) is kept for as long as your account holds it. There is no expiry timer and no periodic purge — it is there until you delete it, either with the in-app delete or, in Before I Unpack, with Delete the backup, which removes the server copy and leaves the phone untouched.
• Backups of our database. We back the database up every night, keep copies with two independent storage providers so that one failure cannot take both, and restore them into a scratch database on a schedule to prove they actually work. The copies are encrypted in transit and at rest and are used for disaster recovery and nothing else. A backup taken before you deleted something still contains it until that backup ages out, which is true of every system that has backups at all.

Backups. Our nightly database backup is kept for 30 days and then deleted automatically. A record you delete is gone from the live database at once and gone from every backup within 30 days. Backups are encrypted at rest, held in the United States in the same region as the live database plus one replica, and are read only to restore the whole database after a failure — never to look up one person.

• Pseudonymous analytics events are retained by our analytics provider for the provider's standard retention period for our plan and then deleted or aggregated; in Launch Lab and Pose Guide that provider is Google Analytics for Firebase. Events that test versions of Pose Guide sent to our own server, before its events moved to Google Analytics for Firebase, stay there under a random install number that nothing links to you.
• Crash reports (Launch Lab and Pose Guide) are retained by Firebase Crashlytics for 90 days and then deleted.
• Pose Guide's account is kept by Google's Firebase Authentication until you delete it with Delete my account; Firebase then removes it from its systems within 180 days, and keeps the network addresses of sign-ins for a few weeks. Our copy of your purchases is deleted at the same time, and we keep only a one-way hash of the deleted account ID, so that a late message about it from RevenueCat makes no new copy.
• Pose Guide's cloud recipes are not stored by us at all. Google keeps them for 55 days to detect misuse and then deletes them. Pose Guide's count of daily cloud plans is deleted after about two days.
• Attribution postbacks are aggregated by design and are retained by our attribution provider under our contract with it.
• Purchase records are retained as long as we must keep them for tax, accounting and refund-dispute purposes.
• Our Sites. The _fbp and _fbc cookies last 90 days, and Meta keeps what the pixel sent under its own policy. Our analytics deletes replays after 90 days and visit records after 400 days, and keeps only totals with no visitor in them after that.
• Support email is retained for as long as needed to resolve your request and to keep a record of it.

9. Children

Our Services are not directed to children and we do not knowingly collect personal information from a child below the minimum age in their jurisdiction.

Our games (Parcel Yard, Pack Perfect). You must not use them if you are under 16 in the European Union or the United Kingdom, under 13 in the United States, or under the minimum age of consent for data processing where you live. The games show advertising and, where allowed, use an advertising identifier; we do not operate them as child-directed services and they are not designed or rated for children.

Our utility apps (Before I Unpack, Milestone). These are adult tools. Milestone in particular:

The person who installs Milestone and owns the plan must be an adult — a parent, godparent or other adult organizer. The celebration's honoree is typically a teenager, and Milestone is built for her to take part on the account owner's device, under the account owner's supervision. Her side of the app is a view of the same plan, and her lane contains no money and no purchases: the budget does not exist in it, no amount, quota or vendor quote is ever shown to her, and she is never shown a paywall or a purchase prompt. This is enforced in the app, not by a policy sentence. There is no separate account for her and no login of her own. Her name, and the photographs in the plan, are stored on our server as part of the account owner's plan (Section 2.4) — that is the owner's own copy of her own celebration, held so that a lost phone does not lose it, and Borrar mi cuenta deletes all of it. Nothing about the honoree is ever sent to an analytics provider or an advertiser.

Pose Guide is a camera coach for adults and is not directed to children. Its cloud recipe runs on Google's Gemini API, and Google's terms require the people using it to be 18 or older. If you are under 18, choose Not now when Pose Guide asks about Google, or leave Settings → Cloud recipes off, and every plan stays on your phone.

If you are a parent or guardian and believe a child has provided personal information to us, contact us at support@get-creative.co with the subject line "Request for Child Data Deletion – Parental Verification", and include:

• the app concerned;
• the app's analytics identifier from the child's device, if you can get it (Settings will show it on request to support);
• your contact details; and
• a clear request to delete all data relating to the child.

We will take reasonable steps to confirm you are the parent or guardian before acting, and we may reply to your email address for confirmation. We will not ask you for more identification than the request needs.

In almost every case the complete remedy is immediate and in your hands, and it reaches our server as well as the phone: open the app, use "Delete everything" (Delete my account / Borrar mi cuenta in Milestone), and then delete the app. That one action deletes the rows and files the account owns on our side, not only the ones on the device. We will confirm it in writing and will delete any pseudonymous event stream you can identify to us.

10. Changes to This Privacy Policy

We may change this Privacy Policy from time to time. The "Last updated" date at the top will change, and the change takes effect on that date. If a change materially affects your privacy rights — for example, if an app begins collecting a category it did not collect before — we will give additional notice in the app itself before the change takes effect. Continuing to use the Services after a change means you accept it.

11. Contact Us

Questions about this Privacy Policy or our privacy practices:

• Email: support@get-creative.co
• Post: Alden Morris Enterprises LLC, 4465 E. Genesee St, Dewitt, NY 13214, United States

12. Additional Notice to Individuals in the United States

12.1 Your rights

Depending on your state, you may have the rights listed in Section 5.1, including the right to know/access, correct, delete, port, opt out of sale or sharing for targeted advertising, opt out of profiling with legal or similarly significant effects, appeal a refusal, obtain a list of third parties to whom we have disclosed personal information, and not be discriminated against for exercising any of them. Where a right is not provided to you by law, we may still honor it at our discretion.

We do not engage in profiling that produces legal or similarly significant effects.

12.2 Submitting a request

Email support@get-creative.co, tell us which right you want to exercise and which app it concerns. See Section 5.2 for what we can and cannot look up. State law may limit how often you may make certain requests in a 12-month period.

12.3 Sale and sharing, and how to opt out

• We do not sell or share, for targeted advertising or for anything else, the content stored on our own server (Section 2.4). It is disclosed to nobody, in any app, including the two games.
• In Before I Unpack, Milestone, Launch Lab and Pose Guide we do not sell or share personal information for targeted advertising. There is no advertising SDK in any of them. Pose Guide's cloud recipes go to Google as our processor, for that one purpose, which is neither a sale nor sharing. Launch Lab's and Pose Guide's usage analytics and crash reports go to Google (Google Analytics for Firebase and Firebase Crashlytics) with no advertising identifier and with ad personalization signals off, so we can measure and fix the app; in Pose Guide, only after your yes. Pose Guide's account is held by Google's Firebase as our processor.
• In Parcel Yard and Pack Perfect, personal information (device and advertising identifiers, device and app information, ad events) is disclosed to advertising partners to serve and measure ads. Under some states' broad definitions this may be a "sale" or "sharing."
• On our ad landing pages, the Meta Pixel (Section 2.5) discloses page events, cookie identifiers, your IP address and device information to Meta, which uses them to measure and deliver ads. Under some states' broad definitions this may be "sharing."

You can opt out at any time. In the games, each of these works:

1. In the game: Settings → Ad & data choices, and turn off Share usage analytics.
2. On an Apple device: iOS Settings → Privacy & Security → Tracking, and turn off tracking for the app. With tracking off, the advertising identifier is unavailable and the ads you see are non-personalized.
3. On an Android device: Settings → Google → Ads → Delete advertising ID (or Opt out of Ads personalization on older versions). 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. With the ID deleted, our games receive a string of zeros and the ads you see are non-personalized.
4. Email us at support@get-creative.co with "Do Not Sell or Share My Personal Information" in the subject line.

On our Sites, choose Decline on the cookie notice or under Cookie settings at the foot of any page that has the notice, turn on Global Privacy Control in your browser, block or delete cookies for nomadarcade.com, or email us as in item 4.

Opt-out preference signals. Our apps are not browsers and do not receive a browser signal. Our Sites honor the Global Privacy Control signal: when your browser sends it, the Meta Pixel does not load, and our analytics stores nothing on your device and keeps no replay (Section 2.5).

12.4 Authorized agents

You may use an authorized agent where your state allows it. The agent must give us your written, signed permission, and we may ask you to confirm the authorization directly.

13. Additional Notice for California Consumers: California Notice at Collection

If you are a California resident, this section applies in addition to the rest of this Privacy Policy. The California Consumer Privacy Act as amended by the California Privacy Rights Act ("CCPA") requires the disclosures below.

13.1 Categories collected, used and disclosed

In the preceding 12 months, depending on which app you used, we may have collected these categories of personal information (Cal. Civ. Code §1798.140(v)(1)):

Categories we do not collect: (C) protected classification characteristics; (E) biometric information; (I) professional or employment information; education information; and sensitive personal information as defined by the CCPA. We do not use or disclose sensitive personal information for purposes requiring a right to limit. In particular, the contents of your communications are never uploaded: the message Before I Unpack helps you write to your landlord, and your key codes, stay on the phone and are excluded from the backup by the code that builds it.

Sale and sharing: see Section 12.3. We do not knowingly sell or share the personal information of consumers under 16 years of age.

Retention: see Section 8.

13.2 Shine the Light

California Civil Code §1798.83 permits California residents with an established business relationship with us to request information about disclosures of certain personal information to third parties for those third parties' own direct marketing purposes in the preceding calendar year. We make no such disclosures. If you would like that confirmed in writing, email support@get-creative.co, say you are a California resident making a "Shine the Light" inquiry, and we will respond. This request may be made once per calendar year.

14. Additional Notice to Individuals in the European Economic Area, United Kingdom, and Switzerland

14.1 Our relationship to you

We are the data controller for personal information collected through the Services. Our providers act as processors on our instructions, except for the advertising networks in our games, which act as independent controllers for their own advertising purposes and to which you consent through the consent form shown in the game.

The content stored on our own server (Section 2.4) has no third-party processor holding it at all — we run the machine ourselves. The only other companies involved are the data-center operator and the two backup-storage providers named in Section 4, which act as processors on our instructions and on nothing else. Pose Guide's cloud recipes, which we do not store, are processed by Google as our processor, and so are Pose Guide's account, usage events, crash reports and settings, on Google's Firebase (Annex F).

• Controller: Alden Morris Enterprises LLC, a New York limited liability company, 4465 E. Genesee St, Dewitt, NY 13214, United States — support@get-creative.co
• EU / UK representative under Article 27: none is appointed, and our apps are therefore not offered in the European Union or the United Kingdom. We will name a representative here before any release in either, in the same change that makes the release.
• Data protection officer: we have not appointed one, and on our assessment we are not required to — we carry out no large-scale processing of special category data and no systematic monitoring of a publicly accessible area. Should that change, this section will name the officer before the processing begins.

14.2 Legal bases for processing

You may withdraw consent at any time. In the app: Settings → Ad & data choices, which reopens the consent form. On an Apple device you may also withdraw it in iOS Settings → Privacy & Security → Tracking; on an Android device the equivalent device-level control is Settings → Google → Ads → Delete advertising ID. On our Sites: Cookie settings, at the foot of any page that has the cookie notice. Withdrawal does not affect processing carried out before you withdrew.

14.3 Your rights

You have the rights of access, rectification, erasure, restriction, objection and portability, and the right not to be subject to a decision based solely on automated processing with legal or similarly significant effects — we make no such decisions. Please read Section 5.2 first: because we hold no identifier that maps to you, the fastest complete route for erasure is the in-app delete.

You have the right to lodge a complaint with your supervisory authority. In the UK it is the Information Commissioner's Office (ico.org.uk); in Switzerland the Federal Data Protection and Information Commissioner (edoeb.admin.ch); in the EEA, your national data protection authority.

14.4 Marketing

We do not run an email marketing program from app data, and we never use an email address an app holds for sign-in to market to you. If we ever contact you electronically for marketing, it will be with your prior consent or as otherwise permitted by law, and every message will carry a one-click unsubscribe.

14.5 International transfers

Where we transfer personal information out of the EEA, the UK or Switzerland, we rely on the European Commission's Standard Contractual Clauses (with the UK International Data Transfer Addendum where applicable), on an adequacy decision covering the recipient country, or on the EU-U.S. Data Privacy Framework where the recipient is certified. Our product analytics for the three apps named in Section 7 is hosted in the EU precisely to reduce the number of such transfers. Our own server, which holds the content in Section 2.4, is in the United States, and the mechanism that applies to it is the open item flagged in Section 7. You may request a copy of the relevant safeguards at support@get-creative.co.

15. Additional Notice to Individuals in Brazil

If you are in Brazil, the Lei Geral de Proteção de Dados (Law 13.709/2018, "LGPD") applies to our processing of your personal data, and we are the controlador.

Milestone is offered in Brazilian Portuguese with a Brazilian celebration pack, so this section is not boilerplate for us.

• Legal bases (Art. 7 LGPD): performance of a contract with you; compliance with a legal obligation; our legitimate interests; and your consent for product analytics and attribution, which is the switch in Settings.
• Your rights (Art. 18 LGPD): confirmation of processing; access; correction of incomplete, inaccurate or outdated data; anonymization, blocking or deletion of unnecessary or excessive data; portability; information about with whom we have shared your data; information about the consequences of refusing consent; and withdrawal of consent. Section 5.2 applies equally here: the in-app delete is immediate and complete, and it is the remedy we can always deliver.
• How to exercise them: support@get-creative.co.
• International transfer: your personal data may be processed outside Brazil. Milestone's plan — including names and photographs — is stored on our own server in the United States (Section 2.4), and Milestone's product analytics is hosted in the United States as well. We rely on contractual clauses that provide the level of protection the LGPD requires; the open item flagged in Section 7 applies here too.
• Encarregado (DPO) / national contact: none is appointed, and our apps are not offered in Brazil. We will name one here before any release there. Until then, write to support@get-creative.co and a person answers.
• You may also lodge a complaint with the Autoridade Nacional de Proteção de Dados (ANPD).

Annex A — Parcel Yard

A puzzle game. Shows ads. Asks for tracking permission once.

Bundle identifier: co.getcreative.parcelrush

Annex B — Pack Perfect

A packing puzzle game. Shows one kind of ad — a rewarded video you ask for.

Bundle identifier: co.getcreative.packperfect

Annex C — Before I Unpack

A move-in condition record. No ads. No tracking prompt. Backup off unless you turn it on, and analytics off unless you turn it on.

Bundle identifier: co.getcreative.beforeiunpack

Nothing leaves your phone until you switch Backup on, and Backup starts off. With it off there is no account, no session and no request of any kind — not one. Switch it on and your records and the original photographs and voice notes are copied to our own server, as a second copy: they stay on the phone as well. Your key codes and the message you wrote to your landlord are never uploaded, in either state. The PDF you export is created on your device and goes where you send it.

What Backup is not: it is not end-to-end encrypted. Files are encrypted on our server and on the way there, but we hold the keys — so in principle we could be made to hand them over. If that matters to you, leave it off; every part of this app works without it.

One honest consequence, stated because it is ours to carry, not yours: because analytics starts off, every number this app produces describes the people who opted in, and they are not a random sample of its users. The same is true of Backup: most people who use this app will never have a copy on our server, and that is the outcome the default was chosen for.

Annex D — Milestone

A celebration planner (quinceañera, festa de 15 anos, debut, sweet sixteen). No ads. No tracking prompt.

Bundle identifier: co.getcreative.milestone

Names, amounts, notes and photographs never appear in analytics. Not as a promise of restraint — the app filters every event against an allowlist of permitted properties before any provider sees it, and anything not on that list is dropped and logged as an error. Every event in the app's taxonomy is tested against that refusal.

Never appears in analytics, in any event, ever: the honoree's name and everyone else's; any amount, budget, quota or vendor quote; every note anyone typed; every photograph and every file path to one; phone numbers; the venue, the address, the church and the date; which app a card was shared to; and any row identifier — screen names are normalized so that an id can never ride along in one.

That is a statement about analytics. The plan itself is stored on our own server so the owner's phone can get it back, and the row below says exactly what that includes. The two lists are different on purpose, and this annex will never let one stand in for the other.

Annex E — Launch Lab

A merge puzzle with a story (Launch Lab: Merge & Story). Optional purchases. No ad network in this version. No tracking prompt.

Store name: Launch Lab: Merge & Story

Bundle identifier: app.rork.45m76l6npj5ml7jyhvh87

Launch Lab sends its gameplay events to two places. One is a table on our own server, written by a function that refuses an event carrying more than a small, bounded object of properties. The other is Google Analytics for Firebase, which counts the screens you open and the steps of the game's funnel: the tutorial, your first merge, the levels you reach, the shop or a paywall opening, and a purchase started and how it ended. Crash reports go to Firebase Crashlytics. Neither Google service receives your account identifier, your name, your email address or anything you type, and no attribution company and no ad network receives anything from this app. Settings → Share usage analytics turns usage analytics off for both, at the app: with it off, nothing is counted, for our server or for Google.

Never leaves your device, in any event, ever: your name, your email address, your contacts, your photographs, your precise location, your device's advertising identifier, and any free text you type. The app has no field that asks for any of them.

Annex F — Pose Guide

A camera coach for iPhone. No ads. No tracking prompt. Your photos stay on your phone.

Bundle identifier: com.nomadarcade.angle

Your photos stay on your phone. Pose Guide holds the burst in memory and saves the one you keep to your photo library with permission to add photos and nothing more, so it cannot read your library. What you say is turned into text on the iPhone. Your words and one frame can leave in one case, and only after you agree. When your iPhone cannot plan a shot on its own, what you said (with names taken out) and one small frame from the camera go to Google's Gemini API, which writes the plan. We store none of it. Pose Guide's account is held for us by Google's Firebase, and usage counts and crash reports go to Google only after you say yes.

Never leaves your phone: the photos you take and keep, the sound of your voice, your photo library and your precise location. The share clip is made on the phone and goes only where you send it.

Change log

rev 15, 2026-10-25

Five more ad landing pages carry the Meta Pixel. Cupshot, Tall Order, Swingaroo, Launch Lab and Parcel Yard now have a page on nomadarcade.com for our Facebook and Instagram ads, and Sections 1 and 2.5 name them. Each one works like the four before it. Nothing else changes.

rev 14, 2026-10-25

Angle is now called Pose Guide. Annex F and every section that named Angle now say Pose Guide. What the app does with your data is unchanged, and so are the addresses of its pages. Its delete button is now called Delete my account, and does what Delete my data did.

Annex E is corrected: our server stores whether you have finished Launch Lab's opening tutorial, so that the game does not take you through it again. Section 5.4 also says that Launch Lab deletes the account itself, so no empty identity row is left.

rev 13, 2026-10-24

Angle moves its account, usage counts and settings to Google's Firebase, and gains an optional sign-in. From its Firebase version, Angle makes an account at Firebase Authentication the first time it opens, with no name, email address or password, in place of the guest account on our server that was made only when first needed. In Settings → Account you may sign in with Apple or Google, which links to the same account so your purchases follow you to a new iPhone; Firebase then keeps the email address, and your name if you share it, that the sign-in gives. Usage events go to Google Analytics for Firebase in place of our own server, crash reports go to Firebase Crashlytics, and the app's settings come from Firebase Remote Config. Both usage and crash reports still wait for your yes on Share anonymous usage?. No user ID is ever set in Analytics, and no advertising identifier is collected. Google works out the city you are in from the connection, so Annex F no longer says your location never reaches analytics; your precise location still never leaves the phone.

Delete my data now deletes the account at Firebase. Our server removes its copy of your purchases and keeps only a one-way hash of the deleted account ID, then the phone revokes Sign in with Apple, if you used it, deletes the Firebase account and clears the phone. Annex F is rewritten from Angle's code as built on 24 October 2026, and Sections 2.1, 2.2, 2.4, 3, 4, 5.2, 5.3, 5.4, 7, 8, 12.3, 13.1, 14.1, 14.2 and 14.4 and the short version's first and third points name Firebase's role and the sign-in. Section 2.2 also no longer says that no app asks for a location permission: Angle does, when you first keep a photo, and that location stays on the phone.

Annex F names the AI providers Angle may use: Anthropic (Claude), OpenAI (ChatGPT), Google (Gemini) and xAI (Grok). It says which of them each feature uses today and what it is sent: cloud recipes go to Google's Gemini API, and example photos to xAI's Grok, which Section 4 now lists beside Google.

rev 12, 2026-10-21

Launch Lab now sends usage analytics and crash reports to Google. From its next version, Launch Lab sends the screens you open and the steps of its funnel (the tutorial, your first merge, the levels you reach, the shop or a paywall opening, a purchase started and how it ended) to Google Analytics for Firebase, beside the events it already wrote to our own server, and crash reports to Firebase Crashlytics. Neither Google service receives the account identifier, a name, an email address or anything typed. No advertising identifier is collected, and there is still no ad network, no attribution SDK and no tracking prompt. Annex E's statement that Launch Lab sends no analytics to any other company is withdrawn and replaced with what it does, and the annex gains a Crash reports row.

A switch for it. Launch Lab gains Settings → Share usage analytics, on by default. Off, the app counts nothing, for our server or for Google; crash reports are separate. Section 5.3 names the switch, Section 14.2 rests Launch Lab's analytics on consent and its crash reports on our legitimate interest, and Sections 2.2, 2.4, 4, 7, 8, 12.3 and 13.1 and the short version's third point name Google's role.

Two smaller changes to Annex E. The one-time purchase called Remove Ads is now called Instant Top-Ups. It is the same product: it skips the short coffee break the game shows before the free energy top-up, and the annex now describes that break as what it is, a screen of the game's own that contacts nobody, since the app has no ads. And the annex states Launch Lab's bundle identifier, app.rork.45m76l6npj5ml7jyhvh87, as the other annexes do.

rev 11, 2026-10-13

Our analytics sends nothing after a Decline or under Global Privacy Control. Since October 12, 2026, a Decline on the cookie notice stops every send from our analytics, on that page and on later ones, and a browser that sends Global Privacy Control sends it nothing at all. Section 2.5 and the legal-basis row in Section 14.2 no longer say such a visit is still counted anonymously. The anonymous count now applies only to a device set to a European time zone before you answer the notice.

rev 10, 2026-10-11

A cookie notice on nomadarcade.com, and our analytics beyond the ad landing pages. Section 2.5 describes the notice. Outside Europe it says what the page records, with OK and Decline; for a device set to a European time zone it asks before our analytics keeps anything on the device or any replay. Decline stops the Meta Pixel and our analytics' recording, the choice is kept in local storage as cookie-consent (a new row in the storage table), and Cookie settings, at the foot of each page that has the notice, changes it. Our analytics, which ran only on the ad landing pages, now runs on the home page, the game pages and the policy pages on nomadarcade.com as well. The short version and Sections 12.3 and 14.2 gain the matching lines: Decline is an opt-out on the Sites, and an EEA device's recording rests on its consent.

rev 9, 2026-10-10

Our website is now described in full. nomadarcade.com is named as the Sites this policy covers, and get-creative.co, which has its own privacy policy, is pointed to it. The new Section 2.5 sets out what they do: the Meta Pixel on our ad landing pages (today, the Cannon Clash page), the two Meta cookies it sets, our own analytics with its session replay and its local-storage items, what Cloudflare sees, how long each is kept, and how to opt out. Sections 1, 3, 4, 7, 8, 12.3, 13.1 and 14.2 gain the matching lines, and the short version a seventh point.

Global Privacy Control is honored on the Sites. Rev 8 promised it for the day we ran advertising technology on our website. The pixel went live on 9 October 2026 without it; from 10 October the page loads no pixel for a browser that sends the signal, and our analytics already stored nothing for one.

Section 2.5 was checked against the live page on 10 October 2026 in two browser engines: the cookies and storage it leaves, the events the pixel sends on load and on a tap, the pixel's settings at Meta, and that a European time zone gets neither the pixel nor any stored item.

rev 8, 2026-09-29

Angle is added as Annex F, and the scope section, the contents and the short version name six apps. Angle is the first app in this policy that can send what a person said, and one photo, to another company. It does so only after a screen that names Google, only when the iPhone cannot plan the shot on its own, and we store none of it. The short version gains a sixth point saying exactly that, and Sections 2, 3, 4, 5.3, 7, 8, 9, 12.3, 13.1 and 14 name Google's role and the 55 days Google keeps a request to check for misuse.

The annex was written from Angle's backend as built on 29 September 2026: a guest account with no email address, anonymous usage events on our own server keyed by a random install number and sent only after a yes, a daily count of cloud plans under a one-way hash, and a delete that removes the guest account server first. Section 2.2 no longer says that no provider identifier is connected to your account identifier, because in Angle RevenueCat's customer ID is the guest account identifier.

Checked again against the merged app the same evening: the guest account is made the first time something needs the server (a cloud recipe, shared usage or a purchase), never at first launch, and Settings is the gear at the top right of the camera.

Angle's server also keeps a copy of each purchase, sent by RevenueCat, under the guest identifier, for support and records. It never decides access. Delete my data removes it with the guest account, along with our record of RevenueCat's messages and the sign-in log lines that name the account.

rev 7 — 2026-09-17

The two blocking placeholders are closed and this document is publishable. The registered address of the controller is stated (Alden Morris Enterprises LLC, 4465 E. Genesee St, Dewitt, NY 13214), and the backup retention window is stated as 30 days — a number that is now enforced by a lifecycle rule on the backup store rather than asserted, because a retention promise nothing implements is the kind of sentence a regulator reads twice.

Launch Lab is added as Annex E, and the scope section and the annex list name five apps rather than four. Launch Lab is the first app in this policy with no third-party analytics, no attribution SDK and no ad network: its gameplay events go to one table on our own server and nowhere else. Its annex says so in those terms rather than claiming a general restraint.

Still open and named here rather than hidden: no EU or UK representative under Article 27 has been appointed. Any release in the United Kingdom or the European Union needs one. The Terms of Service is unchanged and still carries its counsel placeholders, so it is not published alongside this document.

• September 3, 2026 · rev 5 — Parcel Yard gained one optional sign-in, and this policy now describes it. From Settings → Cloud save — never on the way in, never as a condition of playing — a player may attach an email address or an Apple ID to the anonymous account they already have, so that the same game can be opened on another phone. Section 2.4 gains the paragraph that sets out what that address is used for (one thing: reaching your own save), that it is deleted with the account, and that it is never sent to any analytics, attribution or advertising provider; Annex A's Account and Never collected rows say the same in the app's own table; the short version's first point no longer says there is no email address anywhere, because for one app that would now be untrue. Nothing else changed: no new provider, no new category, no new purpose, and three of the four apps still have no sign-in of any kind.

• September 1, 2026 · rev 4 — Hosting move only, no change to any data practice. The hosted copies of these documents now live at https://legal.alc.fyi/legal/, which is live today with a valid certificate, and every URL printed in this suite points there. The move is a hosting decision and nothing more: the studio is still Intentionally Creative, get-creative.co is still the Sites this policy covers, contact is still support@get-creative.co, and no data, processor, retention period or right changed.
• September 1, 2026 · rev 3 — Publisher rename only, no change to any data practice. The studio behind the four apps is Intentionally Creative (get-creative.co); every reference to the former name and to its domain is gone, contact is now support@get-creative.co, and the hosted copies of these documents were given a home under the studio's own domain (superseded at rev 4). The entity placeholder is renamed to match and stays a placeholder — the contracting entity is still counsel's and the founder's call. The four annexes print the reissued bundle identifiers, co.getcreative.*, which is what all four apps now carry; none of them has shipped under the old prefix, so nothing of the old name survives in a binary. Nothing else moved: the same data, the same server in Ashburn, the same processors, the same allowlists, the same rights.
• September 1, 2026 · rev 2 — The backend now exists. Replaced the claims that there is no account, no server, no sync and no backup with what is actually running: an anonymous device account per app, our own self-hosted server in Ashburn, Virginia, game-progress cloud save in both games, opt-in and off-by-default Backup in Before I Unpack (explicitly not end-to-end encrypted), and plan sync in Milestone with money in access-fenced tables. Section 2.4 rewritten, Sections 5.2/5.4/6/7/8 and the CCPA and GDPR disclosures updated, all four annexes updated. Unchanged and re-affirmed: the analytics allowlists, no advertising SDK in either utility app, no precise location anywhere, and Milestone's promise that names, amounts, notes and photographs never appear in analytics.
• September 1, 2026 · rev 1 — First draft of the suite.