Privacy
Privacy policy
Needs Justin's review. Do not paste these URLs into App Store Connect until Justin Ackermann has read this draft. It is not legal advice.
The app sections were read from TimeLapse Tool branch cursor/restore-att-personalized-ads-d6cc and Card Counting Coach branch v5. Items the source still does not state are listed under Review notes.
Effective November 16, 2026.
This is the privacy policy URL for Card Counting Coach. The page also covers the company website and TimeLapse Tool.
This policy covers the website at https://nomadcodingllc.com and two apps from NOMAD CODING & DEVELOPMENT LLC: Card Counting Coach and TimeLapse Tool. It does not describe the studio's other software.
Who we are
NOMAD CODING & DEVELOPMENT LLC publishes the website and these apps. The studio was founded by Justin Ackermann. The only contact published here is [email protected]. This policy does not publish a phone number or a postal address.
The website
nomadcodingllc.com is a set of static pages. It has no accounts, no forms, no comments, and no payments. It does not set cookies. It does not use analytics, advertising, or other trackers.
If you write to [email protected], that message is ordinary email. This website does not store it.
A web host delivers the files, and a network provider may sit in front of the host. Those providers can process connection data, such as an IP address, the time, and the page requested, in order to serve the site. This website does not add its own tracking to that.
The apps
Card Counting Coach and TimeLapse Tool both use Google Mobile Ads (AdMob). Google's description of how its ads partners use data is at policies.google.com/technologies/partner-sites. Google's privacy policy is at policies.google.com/privacy.
Both apps collect a device identifier and advertising data for third-party advertising, and both privacy manifests mark those two types as used for tracking. Google Mobile Ads can also receive ad interactions and diagnostic data when it serves an ad. This draft does not list every field inside an ad request.
Tracking, consent, and how to opt out
On each launch, both apps run the same order: Google's User Messaging Platform (UMP) updates consent and shows its form when a form is required, then Apple's App Tracking Transparency prompt if the tracking choice is still undecided, then the Mobile Ads SDK. Ad loads stay blocked until UMP's canRequestAds is true. Denying the tracking prompt does not by itself block ads. The shipping comments say a denied prompt still allows non-personalized ads, and that the Mobile Ads SDK reads the advertising identifier only after tracking is authorized.
The system prompt is controlled in Settings > Privacy & Security > Tracking. Older iOS versions label that screen Settings > Privacy > Tracking. You can turn off Allow Apps to Request to Track, or turn tracking off for one app.
When Google says an in-app privacy-options entry is required, each app shows a control labeled Privacy & ad choices. That control opens Google's privacy-options form. It is hidden until Google marks privacy options as required.
The app code does not name GDPR or US states. UMP is the consent form both apps present. Which regions see that form is not written in the source that was read.
Card Counting Coach
App Store privacy policy URL: https://nomadcodingllc.com/privacy/card-counting-coach/
The tracking prompt says: "Your data will be used to show you more relevant ads."
The privacy manifest sets tracking to true. Device ID and advertising data are not linked to identity in that manifest, are used for tracking, and are used for third-party advertising. The manifest does not list other data types.
Banners, interstitials, and rewarded interstitials load only when canRequestAds is true and the account has not removed ads. Edit Profile shows Privacy & ad choices on that same condition. Edit Profile also has Delete Account. The delete confirmation says the profile and personal data will be deleted, and that team membership ends.
The v5 screens that were read use Firebase Authentication, Cloud Firestore, Cloud Storage, and Crashlytics for the account, profile, and menu. The permission text says the camera is used for profile photos and team-invite QR codes, the photo library is used for a profile photo, location is used to find nearby casinos for session tracking, and notifications are used for practice reminders and app updates. Info.plist still contains a Facebook app id. This draft does not confirm that a Facebook login button is shown.
TimeLapse Tool
App Store privacy policy URL: https://nomadcodingllc.com/privacy/timelapse-tool/
The tracking prompt says: "This identifier is used to show you more relevant ads. Remove Ads is available in Settings."
The privacy manifest sets tracking to true. Device ID and advertising data are linked to the person, are used for tracking, and are used for third-party advertising, analytics, and the developer's own advertising. The same manifest also declares, as collected and not used for tracking: email address and user ID for app functionality, user ID for analytics, photos or videos for app functionality, product interaction, crash data, coarse location, performance data, and other diagnostic data. Performance data and other diagnostic data are not linked to identity. Product interaction, crash data, and coarse location are linked.
Banners and an interstitial load only when canRequestAds is true. Firebase Analytics collection is turned on only in that same case, and the Mobile Ads SDK starts only then. A one-time Remove Ads purchase hides the ads. Settings shows Privacy & ad choices when privacy options are required. Settings can also sign out, clear on-device history while signed out, and delete the account. Delete account is written to permanently delete the account, saved setups, and photos from the cloud and from the device. Google Sign-In is handled when the app is opened from a Google link.
Data retention
No company retention period was found in the shipping source, so this draft does not state one. Google describes how long it keeps advertising and account data in the policies linked above and at firebase.google.com/support/privacy. Data stored only on the phone stays there until the app is deleted or until a control in the app deletes it. TimeLapse Tool can clear on-device history while signed out, and its delete-account action removes the cloud account, setups, and photos. Card Counting Coach's Edit Profile delete-account action says the profile and personal data will be deleted.
Children
The website is a company brochure. It is not directed at children, and it does not ask visitors for personal information. This draft does not set an age rating for the apps.
Changes
If this policy changes, the effective date on this page will change with it.
Review notes for Justin
These are the points the shipping source still does not settle. Contact: [email protected].
- Neither branch names GDPR or US states. Both use Google's User Messaging Platform and show its form when a form is required. The region list lives outside the app source that was read.
- No company retention period is in either branch. The draft does not invent one.
- Card Counting Coach's Info.plist still has a Facebook app id. The v5 files that were read do not show whether a Facebook login button is offered.
- TimeLapse Tool sign-in with Apple was not in the files read for this pass. Google Sign-In is.