Privacy Policy

Introduction

This Privacy Policy explains how apps published under the MrOldManDave Apps name handle information. It complements any in-app privacy notices and store listing disclosures.

For apps that are still in development, this policy describes currently planned information handling and will be updated again before or at launch.

1. Netball Scoreboard (local-only)

Netball Scoreboard runs entirely on your device. Match scoring, history, and settings stay on your device and are not sent to our servers.

• No cloud sync: we do not store your match data externally.
• No account required for core use: the app is designed for on-device scoring without sign-in.
• In-app purchase (Pro): if offered on your platform, it is processed by the app store provider (Apple App Store and/or Google Play). We do not receive your payment details.
• Sharing (Pro only): if you share scoreboards/history, it uses your device's system share options and you choose where it goes.

2. GoalCall (cloud-backed club/team communication)

GoalCall uses cloud services to provide login and team/club features. We use Firebase (a Google service) to help run those features.

Information GoalCall may collect or store (depending on what you do in the app):

• Account details: an account identifier, and (if you choose) your name and email from Sign in with Apple and/or Google sign-in.
• Club and team data: the clubs/teams you create or join, your role, and membership information.
• Messages and content: messages, check-ins, and other content you or your club/team members submit.
• Push notification token: if you enable notifications, a device token is used to deliver them.
• Support communications: if you email us, we use what you provide to respond.

How we use this information: to provide and secure the service (authentication, syncing, delivering features), respond to support, and improve reliability.

Deletion expectation for release: before any store release that allows account creation, GoalCall will need a clearly discoverable account-deletion path in-app and a public web-based deletion resource.

3. Tap4Shift (workforce attendance and shift management)

Tap4Shift helps employers manage staff, shifts, clock-in/clock-out records, workplace geofence rules, exports, employer roles, and subscriptions. Tap4Shift uses Firebase services so authorised employer users can authenticate and, when sync is enabled, access shared business records across devices.

Information Tap4Shift collects or stores depending on feature use:

• Employer account and role data: Firebase Auth user identifiers, email address, display name, employer role, owner/business identifier, sign-in state, and team membership permissions.
• Staff records: staff names, employee IDs, PINs, QR login tokens, staff access settings, and related employer-managed records.
• Roster and attendance data: shifts, clock-in/clock-out logs, timestamps, break records, early-leave reasons, incident notes, exceptions, payroll lock records, audit entries, and export-ready operational data.
• Location data: precise latitude and longitude recorded when a staff member clocks in or out. If geofence enforcement is enabled, location is also used to decide whether a clock-in is inside the workplace radius.
• Camera and biometric permissions: camera access is used to scan employee QR codes. Face ID or Touch ID is handled by iOS on the device to unlock a staff or employer session; we do not receive face or fingerprint data.
• Purchases, subscriptions, and entitlements: Apple StoreKit product and transaction information needed to provide employer plan access, restore purchases, reconcile active plans, and handle refunds or revoked transactions. We do not receive full payment card details.
• Local preferences and technical data: app settings such as appearance, sync mode, notification preferences, billing state, and operational diagnostics needed to provide and secure the app.
• Support communications: if you contact us, we use the information you provide to respond.

How we use this information: to authenticate employers, manage employer roles, let staff view shifts and clock in/out, enforce optional workplace geofence policies, maintain attendance and audit records, sync business data where enabled, provide exports and subscription entitlements, prevent unauthorised access, troubleshoot issues, and respond to support or deletion requests.

Staff access: staff users do not purchase subscriptions in Tap4Shift. Employer subscription status controls employer features and workplace plan limits.

Deletion and retention: Tap4Shift includes account and business deletion controls for employer owners. De-linked employer accounts may be retained for up to 30 days for cleanup. Some records may be retained where needed for audit history, security, fraud prevention, StoreKit reconciliation, legal compliance, dispute handling, or protection of other users.

3A. StreetTucker (iPhone app)

StreetTucker is an Australian food truck discovery app for customers and mobile food vendors. It uses cloud-backed account, listing, review, purchase, advertising, ABN trust-check, loyalty, and moderation features to operate the service.

Information StreetTucker collects or handles depending on how you use the app:

• Account and authentication data: Firebase Auth user identifiers, Sign in with Apple identifiers, Apple relay or Apple-provided email where supplied, display name, selected role, onboarding/profile completion state, sign-in state, and security/session information. If you enable Face ID or Touch ID unlock, the biometric check is handled by iOS on your device; we do not receive your face or fingerprint data.
• Customer profile data: display name, email, display-name style, home suburb, preferred cuisine tags, favourites, saved vendors, profile image/avatar media you choose to add, and related timestamps or settings.
• Vendor listing and profile data: owner account ID, business name, tagline, bio, cuisine tags, current trading location, regular spot notes, address, latitude/longitude, trading status, opening hours, phone, email, website, menu URL, Instagram, contact visibility choices, catering availability, menu items, uploaded logo/profile media, photos or image references, loyalty settings, and listing update timestamps.
• ABN trust-check data: vendor-submitted ABNs, ABN status, entity name, GST registration indicator, state, postcode, check time, trust status, and rate-limit/security metadata. ABN checks are optional vendor trust signals and do not verify food licences, council approvals, insurance, trading permission, or food-safety compliance.
• Reviews and moderation data: ratings, review text, reviewer display name/user ID, vendor ID, report-vendor actions, report-review actions, report reasons/details, moderation status, admin action metadata, and related timestamps used to protect users and service integrity.
• Location data: customers may grant location access for nearby discovery and map browsing. Vendors may use location access or manual map placement to pin a current trading spot. StreetTucker does not provide continuous live vendor GPS tracking, driver tracking, delivery tracking, or always-on vehicle movement tracking.
• Camera and loyalty data: camera access is used for loyalty QR scanning after ordering or reward redemption. Loyalty records may include vendor/customer IDs, stamp counts, reward-ready status, stamp/redemption timestamps, and QR payload identifiers.
• Purchases, subscriptions, and entitlements: Apple StoreKit product and transaction information needed to provide customer Remove Ads and vendor subscription entitlements, restore purchases, reconcile active plans, and handle refunds or revoked transactions. We do not receive your full payment card details.
• Ads and ad measurement data: if ads are shown, Google AdMob and related platform services may process ad requests, impressions, interactions, coarse location or IP-derived region, device/app identifiers where permitted, diagnostics, fraud-prevention signals, and SKAdNetwork attribution data. Personalized ads or tracking-linked identifiers are used only where permitted by platform rules, device settings, and applicable consent requirements.
• Technical and security data: app version, device/platform diagnostics, Firebase App Check/App Attest signals, crash or performance information, abuse-prevention data, and support communications if you contact us.

How we use this information: to authenticate users, provide customer and vendor features, sync profiles/listings/reviews across devices, show map and nearby results, run vendor ABN trust checks, operate loyalty features, provide StoreKit entitlements, display or remove ads, respond to reports, prevent fraud or abuse, troubleshoot issues, and comply with legal or platform obligations.

Deletion and reporting: StreetTucker includes in-app account deletion request controls and visible reporting controls for vendors and reviews. Some records may be retained after a deletion request where needed for moderation history, safety, fraud prevention, purchase/subscription reconciliation, legal compliance, dispute handling, or protection of other users.

3B. Yard2Road (in development)

Yard2Road is in development as a yard-to-road operations and workflow app for businesses, teams, and authorised staff managing jobs, checks, handovers, vehicle/equipment details, and related operational records.

Information Yard2Road is expected to collect or store (depending on feature use):

• Account and profile details: identifiers, names, contact details, roles, permissions, and sign-in status needed to provide access.
• Operational records: job details, yard or road status updates, checklists, task records, vehicle/equipment references, handover notes, and related timestamps.
• Submitted content: notes, photos, attachments, signatures, or forms you choose or are required to add for a workflow.
• Optional device permissions: camera, photos/files, notifications, and location may be used only where enabled by released features and permitted on your device.
• Technical diagnostics: app/device diagnostics needed to maintain reliability, troubleshoot faults, and secure the service.

Current plan: Yard2Road is expected to use cloud-backed services so authorised users can access shared workflow records across devices. If account features are included in a released build, the app will need a clearly discoverable account-deletion path and web-based deletion request support where platform rules require it.

4. Diamond Scoreboard (Apple App Store)

Diamond Scoreboard is live on the Apple App Store. It is a scoreboard-focused experience for baseball/softball game tracking (innings, runs, and game flow).

• Local-first operation: core game data is stored on your device for day-of-game operation.
• No account requirement: current core scoring use does not require sign-in.
• Possible future changes: if cloud sync, account features, or analytics are added, this policy will be updated before those features are released.

4A. Coach Me Netball (Apple App Store)

Coach Me Netball is live on the Apple App Store as a coaching toolkit for planning training sessions, line-ups, tactical notes, and game-day checklists.

Information Coach Me Netball currently handles or stores:

• Planning data: training plans, line-up notes, and coaching checklists you create in the app.
• Team setup details: player and role/position information used to prepare sessions and match-day plans.
• Technical diagnostics: device/app diagnostics needed to maintain stability and reliability.

Current design: Coach Me Netball currently operates primarily on-device for core planning workflows on iOS. If cloud sync, account login, or sharing features are introduced, this policy will be updated before those features are released.

4B. Coach Me Soccer (Apple App Store)

Coach Me Soccer is live on the Apple App Store as a coaching toolkit for planning sessions, organising squads, recording tactical notes, and managing game-day preparation.

Information Coach Me Soccer currently handles or stores:

• Planning data: session plans, line-up notes, checklists, and coaching reminders you create in the app.
• Team setup details: player, role, and squad information used to prepare training sessions and match-day plans.
• Technical diagnostics: device/app diagnostics needed to maintain stability and reliability.

Current design: Coach Me Soccer currently operates primarily on-device for core planning workflows on iOS. If cloud sync, account login, or sharing features are introduced, this policy will be updated before those features are released.

4C. Coach Me Hockey (Apple App Store)

Coach Me Hockey is live on the Apple App Store as a coaching toolkit for planning sessions, organising line-ups, recording tactical notes, and supporting game-day preparation.

Information Coach Me Hockey currently handles or stores:

• Planning data: session plans, line-up notes, checklists, and coaching reminders you create in the app.
• Team setup details: player, role, and squad information used to prepare training sessions and match-day plans.
• Technical diagnostics: device/app diagnostics needed to maintain stability and reliability.

Current design: Coach Me Hockey currently operates primarily on-device for core planning workflows on iOS. If cloud sync, account login, or sharing features are introduced, this policy will be updated before those features are released.

4D. Coach Me Baseball (Apple App Store)

Coach Me Baseball is live on the Apple App Store as a coaching toolkit for planning practices, organising lineups, managing batting orders, and supporting game-day decisions.

Information Coach Me Baseball currently handles or stores:

• Planning data: practice plans, batting order notes, defensive alignments, and game-day checklists you create in the app.
• Team setup details: player, position, lineup, and workload context used to prepare practices and games.
• Technical diagnostics: device/app diagnostics needed to maintain stability and reliability.

Current design: Coach Me Baseball currently operates primarily on-device for core planning workflows on iOS. If cloud sync, account login, or sharing features are introduced, this policy will be updated before those features are released.

4E. Coach Me Umpire Netball (Apple App Store)

Coach Me Umpire Netball is live on the Apple App Store as a local-first netball umpire companion for learning rules, practising signals, reviewing scenarios, completing quizzes, and following match-day routines.

Information Coach Me Umpire Netball currently handles or stores:

• Learning and reference data: bundled lessons, rule summaries, signal guides, glossary terms, bookmarks, and recent searches used for quicker review.
• Quiz and progress data: quiz attempts, scores, checklist progress, study history, and confidence or practice notes you choose to save.
• Match-day notes and checklists: before-match, during-match, and after-match checklist progress, note templates, and self-reflection notes you create in the app.
• Scenario references: curated scenario links, topic filters, and video-reference metadata used to organise decision review. If a scenario link opens a third-party website or video service, that service handles information under its own privacy policy.
• Support and suggestions: if you use the website's Suggestions or contact features for Coach Me Umpire Netball, the information you submit is handled under the contact sections of this policy.
• Technical diagnostics: device/app diagnostics needed to maintain stability and reliability.

Current design: Coach Me Umpire Netball currently operates as a local-first iOS experience for core learning, search, quiz, note, and match-day workflows. The current design does not require an account, cloud sync, location tracking, contact access, or photo access for core use. If ads, in-app purchases, cloud sync, account login, external sharing, or additional permissions are introduced, this policy will be updated before those features are released.

5. FadSherpa (Apple App Store)

FadSherpa is live on the Apple App Store. Based on current features (trend discovery, regional filters, and search), FadSherpa uses cloud content delivery and may include ads in the free experience.

• Content and usage signals: region selection, search terms, and in-app interactions may be processed to deliver relevant trend content.
• Ads: if ads are enabled, we may use Google AdMob (and, where configured, mediation partners). Ad requests may include technical information such as device identifiers, IP-derived region, app version, and coarse diagnostics for fraud prevention, delivery, and measurement.
• Check settings: ad personalization and tracking behavior can depend on your device/platform privacy settings and permissions.
• What this means: if personalized ads/tracking is turned off, you may still see ads, but they are expected to be less tailored (contextual or non-personalized).
• Consent: where required by law or platform rules, tracking-related identifiers or personalized advertising will only be used after the relevant consent or permission flow.

5A. CoachMe EqualPlay Lineup (Apple App Store)

CoachMe EqualPlay Lineup, formerly FairPlay LineUp, is live on the Apple App Store as a CoachMe group app for lineup planning, fair rotations, stats, reports, exports, and shareable match-day notes.

Information CoachMe EqualPlay Lineup stores or handles on your device:

• Lineup and rotation data: player names or identifiers, positions, availability, substitutions, bench/rotation plans, and game-day adjustments you enter.
• Team setup and match details: squads, roles, games, stats, notes, participation details, fairness/planning preferences, reports, and export outputs you create.
• Demo and app settings: sample-team/demo content, saved preferences, colour presets, and local app settings used to run the app.
• Sharing and exports: if you share notes, reports, or exports, the app uses your device's system share options and you choose where the information goes.
• Purchases and entitlements: Pro upgrade transactions are processed by Apple StoreKit. We do not receive your full payment card details.
• Support and suggestions: if you use the website's Suggestions or contact features for CoachMe EqualPlay Lineup, the information you submit is handled under the contact sections of this policy.

Current design: CoachMe EqualPlay Lineup is a local-first planning tool. Core team, lineup, stats, note, report, and export data remains on your device unless you choose to export or share it. The current design does not require an account, cloud sync, location tracking, contact access, or photo access for core use. If shared team syncing, account features, cloud backup, ads, or additional permissions are introduced, this policy will be updated before those features are released.

5B. CIF - Can I Fish (in development)

CIF - Can I Fish is in development as a planning app to help anglers assess whether current and upcoming conditions are suitable for a trip.

Information CIF - Can I Fish is currently expected to handle:

• Trip planning inputs: selected regions, saved spots, trip preferences, and condition checks you choose to save.
• Optional location information: if location-based features are released, the app may use device location or a manually entered location to provide relevant conditions. Optional permissions will only be used with your device-level consent.
• Forecast or condition data requests: query information needed to retrieve weather, marine, tide, or similar condition data from third-party data sources.
• Technical diagnostics: app/device diagnostics needed to maintain reliability and troubleshoot faults.

Current plan: CIF - Can I Fish is expected to minimize personal data collection and use external data providers only to deliver the requested condition view. If accounts, cloud sync, alerts, or additional permissions are added, this policy will be updated before release.

5C. theAngler (Apple App Store)

theAngler is live on the Apple App Store as an unofficial fan-made companion guide for Call of the Wild: The Angler players who want quick fish, hotspot, bait, lure, and setup reference help while they play.

Information theAngler currently handles or stores:

• Reference and preference data: fish guides, hotspot references, bait/lure/setup lookups, and saved filters or bookmarks used to make the guide easier to navigate.
• Optional local quick-reference data: favourites, recent lookups, and similar on-device convenience data if those features are included in the released app.
• Technical diagnostics: app/device diagnostics needed to maintain reliability and troubleshoot faults.

Current design: theAngler currently operates primarily on-device for core reference workflows on iOS. If accounts, cloud sync, community submissions, or other online features are introduced, this policy will be updated before those features are released.

5D. Element Flux (in development)

Element Flux is in development as a fully on-device factory-building progression game for iPhone and iPad where players discover materials, automate production chains, and work toward a Mars launch goal.

Information Element Flux is currently expected to handle:

• Gameplay and progression data: save progress, discovered materials, unlocked recipes, factory/build states, production milestones, and related game settings stored for ongoing play.
• On-device preferences: local display, accessibility, control, or convenience settings used to personalize the game experience.
• Technical diagnostics: app/device diagnostics needed to maintain reliability and troubleshoot faults.

Current plan: Element Flux is currently planned as a local-first game experience. If cloud save, accounts, leaderboards, analytics, or other online features are introduced, this policy will be updated before release.

5E. A Traders Journey (in development)

A Traders Journey is in development as an original iPhone and iPad strategy game about fictional station markets, cargo contracts, routes, crew-share ranks, and long-term company growth.

Information A Traders Journey is currently expected to handle:

• Gameplay and progression data: local game saves, player name, credits, crew-share rank, reputation, holdings, cargo lots, contracts, route state, station state, market quotes, fictional news events, transactions, unload reports, travel events, current objectives, ship upgrades, company progress, fleet growth, and related story/progression flags.
• On-device preferences: sound, reduced motion, text size, game difficulty, onboarding state, subscription status cache, and other local settings used to personalize play.
• Purchases and entitlements: Apple StoreKit transaction and entitlement information needed to provide optional ad-free subscriptions, restore purchases, reconcile active plans, and handle refunds or revoked transactions. We do not receive your full payment card details.
• Ads and ad measurement: the free tier can show Google AdMob full-screen ads after completed travel. Where ads are configured, ad requests, impressions, interactions, fraud-prevention signals, SKAdNetwork attribution data, diagnostics, IP-derived region, and device/app identifiers made available by the platform or SDK may be processed by Google and related platform services. Personalized ads or tracking-linked identifiers are used only where permitted by platform rules, device settings, and applicable consent requirements.
• Support and suggestions: if you use the website's Suggestions or contact features for A Traders Journey, the information you submit is handled under the contact sections of this policy.
• Technical diagnostics: app/device diagnostics needed to maintain reliability and troubleshoot faults.

Current design: A Traders Journey is local-first for core gameplay and uses local JSON saves rather than cloud sync. The current design does not require an account, location tracking, contacts access, camera access, photo access, real securities accounts, or real financial information. If cloud save, accounts, leaderboards, community features, or additional permissions are introduced, this policy will be updated before release.

5F. Beta Bridge / BetaBridge (iPhone app)

Beta Bridge is an iPhone app that helps developers and external testers discover beta opportunities for apps already distributed through Apple TestFlight. Beta Bridge does not host app binaries, distribute builds, bypass TestFlight, or replace App Store Connect. Joining a beta is handed off to the developer's official TestFlight public link.

Information Beta Bridge collects or handles, depending on how you use the app:

• Account and identity data: Firebase/Auth account identifiers, Sign in with Apple identifiers, Apple relay or Apple-provided email where supplied, onboarding and account-state fields, role flags, optional display name, Beta Bridge ID records, and referral/eligibility state.
• Profile and device details: developer and tester profile fields such as bio, support details, links, country, languages, interests, experience level, and tester device/OS entries submitted in the app.
• Listing, application, feedback, and media data: app listing details, official TestFlight links, App Store/TestFlight metadata, categories, screenshots, listing icons, profile images, saved listings, tester applications, feedback records, join-intent/reward records, and related timestamps/status fields.
• Public and shared visibility: published listings, developer profile information, tester profile information used for applications, uploaded listing media, and application/feedback details may be visible to other Beta Bridge users involved in the relevant listing or workflow.
• Safety and moderation data: reports, blocks, moderation actions, moderation notes, takedown/restriction records, abuse/fraud signals, audit data, and support communications used to protect users, enforce rules, and preserve service integrity.
• Purchase, entitlement, reward, and ad-credit data: Apple StoreKit product and entitlement state, remove-ads status, developer plan status, listing-slot or boost-credit state, BetaBank/reward activity, rewarded-ad completion records, and server-side verification data used to grant credits and prevent fraud. We do not receive your full payment card details.
• Notifications: in-app notification records, notification preferences, quiet-hours settings, unread counts, device installation identifiers, APNs tokens, Firebase Cloud Messaging tokens, app version/build metadata, and delivery status needed to send and manage notifications you enable.
• Ads: Beta Bridge includes Google Mobile Ads / AdMob for free users. Ad requests, impressions, rewarded-ad events, and fraud-prevention checks may involve Google and may include technical information such as device identifiers made available by the platform/SDK, IP-derived region, app version, ad interaction data, SKAdNetwork attribution data, and diagnostics. Paid remove-ads or developer-plan entitlements are intended to remove ads from the account where supported. If personalized advertising or cross-app/web tracking is enabled, it must follow applicable consent, opt-out, and Apple permission requirements.
• Usage, ranking, and operational events: app actions such as listing creation, saving, applying, joining through TestFlight, feedback, rewards, boosts, referrals, ranking changes, and help/support actions may be recorded to operate features, prevent abuse, calculate rankings/rewards, and troubleshoot reliability.
• Optional App Store Connect credentials and import data: if a developer chooses to use the App Store Connect import tools, Beta Bridge collects the developer's Key ID, Issuer ID, and .p8 private key file. These credentials are saved locally in that user's device Keychain for convenience and can be removed using Clear ASC Credentials. When the developer runs an import, metadata check, or quick TestFlight import, the credentials are sent over HTTPS to a Firebase Cloud Function, used only to create a short-lived App Store Connect API token and request authorized app metadata from Apple's App Store Connect API, and are not stored on Beta Bridge servers. Imported data may include app names, bundle IDs, platforms, beta/localization details, build/version/expiry information, icon/screenshot URLs, support/privacy URLs, and related metadata used to prefill listing drafts or check live status. Users remain responsible for securing their device, protecting and revoking their own App Store Connect keys where appropriate, using credentials only when authorized, and verifying imported data before publishing listings.
• Technical diagnostics: app, device, server, and Cloud Function diagnostics needed to maintain reliability, investigate errors, secure the service, and troubleshoot faults.

Current service stack: Beta Bridge currently integrates Firebase Authentication, Firestore, Cloud Storage, Cloud Functions, Firebase Cloud Messaging, Sign in with Apple, Apple StoreKit, Apple Push Notification service, and Google Mobile Ads / AdMob.

5G. Final Horn (iPhone and iPad app)

Final Horn is an iPhone and iPad app that provides multi-sport timers and match clock utilities.

Information Final Horn is currently expected to handle:

• On-device timing and preset data: sport presets, custom timer settings, favorites, and recent selections stored locally on your device.
• On-device preferences: local display and convenience settings used to personalize timing workflows.
• Purchase state (if enabled): store-provided entitlement status for optional one-time Remove Ads functionality.
• Technical diagnostics: app/device diagnostics needed to maintain reliability and troubleshoot faults.

Current design: Final Horn is designed as a local-first timing app with offline-reliable core operation. If accounts, cloud sync, online competition features, or additional analytics are introduced, this policy will be updated before those features are released.

5H. Sports Hakken (in development, iPhone app)

Sports Hakken is in development as a public directory for niche sports events across Australia. It uses cloud-backed services to provide event discovery, account-backed submissions, reports, saved events, source import, and admin review workflows.

Information Sports Hakken collects or handles depending on feature use:

• Account and authentication data: Firebase Auth user identifiers, Sign in with Apple identifiers, Apple relay or Apple-provided email where supplied, display name, sign-in state, role, saved sports, saved states, saved event IDs, blocked status, and related timestamps.
• Public event data: event titles, descriptions, sport tags, event type, dates and times, timezone, venue names, addresses, suburbs, states, latitude/longitude where supplied, cost and price details, booking links, organiser details, source URLs, image URLs, age group, skill level, accessibility tags, confidence scores, status, and update timestamps.
• Submissions and reports: event details you submit for admin review, source links, notes for admin, submitted-by identifiers, report type, report messages, moderation status, admin notes, and related timestamps.
• Location data: optional current location is used only when you choose Near Me or similar location-based discovery. You can browse by state or search without sharing your location.
• Calendar permission: Apple Calendar access is requested only when you choose to add an event to Calendar. Calendar entries are created on your device using event details and source links.
• Saved events and preferences: saved event IDs, saved sports, saved regions, Near Me radius, appearance preference, onboarding state, and other local or account-backed settings used to personalize discovery.
• Source import and admin data: source records, importer logs, stale-event flags, admin review decisions, cleanup/expiry records, and moderation workflow data used to keep the directory current and trustworthy.
• Planned paid listing data: if paid event listing or organiser plans are released, StoreKit transaction and server-side entitlement records may be used to grant listing credits or organiser access. We would not receive full payment card details.
• Support communications and diagnostics: if you contact us, submit feedback, or encounter errors, we use the information provided and relevant app/server diagnostics to respond, troubleshoot, secure the service, and improve reliability.

How we use this information: to authenticate users, show and filter public events, save events, process submissions and reports, support admin review, improve event-source reliability, provide optional location-based discovery, add events to Calendar when requested, prevent abuse, and respond to support or deletion requests.

Current plan: Sports Hakken is account-backed for submissions, reports, saved events, and admin workflows. Before any public store release that allows full account creation, Sports Hakken should provide a clearly discoverable account-deletion path and web-based deletion request support where platform rules require it.

5I. Stock4Chairs (Apple App Store, iPhone and iPad app)

Stock4Chairs is live on the Apple App Store as a stock-count and inventory helper for chair-based businesses, venues, clubs, schools, hire teams, and other teams managing chair-related stock or supplies.

Information Stock4Chairs currently handles:

• Inventory records: item names, categories, quantities, locations, condition notes, availability notes, reorder reminders, barcode or SKU values, selected item photos, and related details you create in the app.
• Camera and barcode scanning: camera access is used for scanning barcodes or item codes to speed up inventory entry and lookup. Camera access is controlled by your device permission settings.
• Photo selection: Stock4Chairs uses Apple's PhotosPicker so you can choose item photos from your library. Only the photos or media you select are made available to the app; Stock4Chairs does not receive access to your full photo library.
• Purchases and entitlements: Apple StoreKit product, transaction, and entitlement information needed to provide in-app purchases, restore purchases, and handle refunded or revoked transactions. We do not receive your full payment card details.
• File export and sharing: export files are generated from inventory data you choose to export and are saved or shared using your device's file and share controls. You choose where exported files go.
• Operational notes: stock-check notes, saved lists, export settings, and local preferences used to make repeat checks faster.
• Technical diagnostics: app/device diagnostics needed to maintain reliability and troubleshoot faults.

Current design: Stock4Chairs is currently a local-first stock and inventory utility for core workflows. Core inventory records, scanned codes, selected photos, notes, generated exports, and settings remain on your device unless you choose to export, save, or share them using system controls. StoreKit purchases are processed by Apple. If cloud sync, account login, team sharing, ads, or new server-backed features are introduced, this policy will be updated before those features are released.

5J. SubmitWise (Mac, iPhone, and iPad app)

SubmitWise is a developer tool for App Store Connect analysis. It is built for Mac, iPhone, and iPad, with separate App Store availability for Mac and mobile devices but the same core app experience.

Information SubmitWise handles depending on feature use:

• App Store Connect credentials: Key ID, Issuer ID, private .p8 key material, and optional vendor number you provide for App Store Connect API access. SubmitWise uses API keys and does not ask for your Apple ID password.
• Credential storage: credentials are stored in Apple Keychain. If you enable credential sync, the same credential item may be stored in iCloud Keychain so your own trusted Mac, iPhone, and iPad signed into the same Apple Account can use it.
• Imported app data: app names, bundle IDs, SKUs, primary locales, App Store version states, localizations, privacy policy URLs, metadata, reviews, analytics-report metadata, Sales and Trends report data, subscription or revenue signals, and other App Store Connect data available to your API key.
• Workspace and analysis data: selected app scope, imported reports, local analysis results, competitor selections, manual review samples, tasks, readiness checklists, region/currency preferences, appearance settings, and similar workspace records are stored on your device.
• Public App Store search data: competitor discovery uses Apple's public App Store search/lookup endpoints for the selected region and may process search terms, app identifiers, public app metadata, artwork URLs, ratings, and App Store listing URLs.
• User-selected files: on Mac, SubmitWise may read Sales and Trends report files you choose to import. The Mac app entitlement is limited to user-selected read-only files.
• Support communications: if you contact us about SubmitWise, we use the information you provide to respond.

How we use this information: to connect to App Store Connect, import authorized app and report data, analyze revenue, subscriptions, analytics, reviews, competitors, optimization, localization, accessibility, launch, and readiness signals, save your local workspace, and respond to support requests.

Current design: SubmitWise is local-first. Credentials are stored in Keychain, the private key is not shown after import, and workspace records stay on your device unless you choose to sync credentials through iCloud Keychain or share/export information through system controls. Users remain responsible for securing their devices, using only App Store Connect keys they are authorized to use, and revoking keys in App Store Connect if a key is no longer needed or may be compromised.

5K. DiskLint (Mac app)

DiskLint is a native macOS developer cleanup tool for finding generated developer clutter on a Mac. It is not an iPhone or Android app.

Information DiskLint handles depending on feature use:

• Local disk scan results: developer cache categories, file and folder paths, sizes, timestamps, safety labels, cleanup selections, and scan summaries created while reviewing generated developer files.
• User-selected folders: project roots or folders you choose to let DiskLint inspect. The Mac app uses sandboxed, user-selected file access and app-scoped bookmarks where needed to remember approved folders.
• Cleanup records and settings: selected cleanup preset, retention preferences, ignored paths, low-disk threshold settings, cleanup history summaries, and local app preferences.
• System commands: DiskLint may use supported macOS or developer-tool commands, such as Apple's simulator tooling, to inspect or clean eligible developer items. It is designed to protect source code and sensitive CoreSimulator operational data by default.
• Support communications: if you contact us about DiskLint, we use the information you provide to respond.

How we use this information: to show what is using disk space, explain cleanup tradeoffs, preserve user choices, move selected eligible items to Trash where supported, and help users avoid deleting source code or important developer assets.

Current design: DiskLint is local-first. Core scan results, file paths, project names, cleanup selections, settings, and history stay on your Mac unless you choose to share/export them or send them to us for support. DiskLint is not designed to upload file paths, project names, or scan results to MrOldManDave servers.

5L. Am I Wrong? Vote (in development, iOS and Android app)

Am I Wrong? Vote is in development as a community voting app where users can post everyday situations and other users vote Yes, Unsure, or No. Because it is built around user-generated content and public or community interaction, the app has a 16+ rating and minimum age and is not designed for children under 16.

Information Am I Wrong? Vote is expected to collect or handle depending on feature use:

• Account and authentication data: account identifiers, email address, display name, sign-in provider identifiers, sign-in state, age or eligibility signals where required, and account status such as active, suspended, or banned.
• Posts and voting content: post titles, situation/body text, categories, optional anonymous display choices, timestamps, vote counts, user's own votes, community-result data, and moderation status.
• Discussion and safety data: comments or replies if released, report-post and report-user submissions, block lists, report reasons/details, banned-word filter matches, moderation queue records, admin actions, warnings, removals, suspensions, bans, and related timestamps.
• Subscriptions, vote limits, and entitlements: store transaction and entitlement records used to provide posting subscriptions, voting subscriptions, free vote limits, restore purchases, handle refunds or revoked transactions, and reduce subscription or vote-limit abuse. We do not receive full payment card details.
• Fraud-prevention and service-integrity data: server-side free vote counts, account/device or installation identifiers where legally permitted and disclosed, App Check or similar abuse-prevention signals, rate-limit records, and technical security metadata.
• Technical diagnostics and support communications: app version, device/platform diagnostics, crash or performance data, and information you provide if you contact us.

How we use this information: to authenticate users, publish and display posts, record votes, calculate community results, provide subscriptions and free vote limits, operate reports, blocks, filters and moderation, enforce community rules, reduce abuse, troubleshoot issues, and respond to support or deletion requests.

Current plan: Am I Wrong? Vote is expected to use cloud-backed account, post, vote, subscription, and moderation services. Before any public store release, eligibility, the 16+ age rating and minimum age, account-deletion, reporting, blocking, and moderation controls should be reviewed against Apple App Store, Google Play, online safety, privacy, and age-restriction requirements in the regions where the app is offered.

6. Sharing and third parties

We do not sell your personal information. We share information only as needed to provide functionality and comply with law. When service providers handle user data for us, we expect them to protect it consistently with this policy and applicable law.

• Firebase (Google): authentication, database, storage/media handling where enabled, cloud-function hosting, App Check/App Attest enforcement, messaging/push token support where enabled, diagnostics, and operational event processing for GoalCall, StreetTucker, Beta Bridge, Sports Hakken, and Am I Wrong? Vote, plus planned cloud features for Tap4Shift and Yard2Road.
• Apple: App Store purchases and subscriptions (where applicable), StoreKit entitlement and transaction handling, Sign in with Apple (if used), Apple Push Notification service where enabled, Apple Calendar/EventKit features where you choose to add an event to Calendar, TestFlight handoff, SubmitWise App Store Connect API requests and public App Store search/lookup requests, App Store Connect API metadata requests when a developer uses optional Beta Bridge import tools, Keychain/iCloud Keychain storage where enabled, DiskLint macOS sandbox/user-selected file access, local A Traders Journey save and preference storage on device, and store review or platform services.
• Apple MapKit/CoreLocation: map display, vendor map pins, optional customer-side Near Me location features in StreetTucker, and optional Near Me event discovery in Sports Hakken where enabled by the app and allowed on your device.
• Google: Google Play purchases (where applicable), Google sign-in (if used), Android push delivery services, and Google Play platform services for Android app distribution.
• Ad technology providers (apps/features with ads enabled, including StreetTucker, FadSherpa, Beta Bridge, and A Traders Journey): Google AdMob and, where configured, mediation partners to deliver, verify, reward, prevent fraud, and measure ads in line with your device permissions, in-app privacy choices, platform rules, and applicable law.
• ABN Lookup / Australian Business Register services: StreetTucker vendor ABN trust checks use ABN Lookup data via a server-side Firebase Cloud Function. ABN results are public business register signals and are not a licence, insurance, food-safety, or trading-permission certification.
• Other Beta Bridge users: profile, listing, application, feedback, and moderation-visible content may be shared with developers, testers, moderators, or admins as needed for the relevant workflow.
• StreetTucker users and moderators: vendor listing details, reviews, ratings, loyalty-related customer/vendor records where relevant, and moderation-visible report information may be visible to customers, vendors, moderators, or admins as needed for discovery, loyalty, and safety workflows.
• Sports Hakken users, organisers, and admins: public event details, submitted event information, source links, report details, saved-event operations, and moderation-visible data may be visible to users, organisers, reviewers, moderators, or admins as needed for event discovery and directory integrity.
• Am I Wrong? Vote users and moderators: post titles, situation text, categories, public vote results, comments or replies if released, reports, block-related effects, and moderation-visible data may be visible to users, moderators, or admins as needed for community voting, safety, and service integrity.
• Content, weather, or condition-data providers (if enabled for FadSherpa or CIF - Can I Fish): to return requested content, trend information, forecasts, or related condition summaries.
• Legal requirements: if we are required to disclose information by law.

7. Data security

We take reasonable steps to protect information. For cloud-backed features (GoalCall, StreetTucker, Beta Bridge, Sports Hakken, Am I Wrong? Vote, planned Tap4Shift and Yard2Road services, FadSherpa content/ad services, and any future CIF - Can I Fish forecast integrations), we use encrypted connections (TLS) for data in transit and provider-side access controls such as Firebase security rules, App Check/App Attest where configured, and storage restrictions for user-owned records and uploaded images. Optional Beta Bridge App Store Connect private keys are stored locally in the user's device Keychain, are transmitted only when an import/check is run, and are not intentionally stored on our servers. SubmitWise App Store Connect credentials are stored in Keychain, may sync through iCloud Keychain only if enabled, and are used for direct App Store Connect API requests from the app. For local-first apps (Netball Scoreboard, the current Diamond Scoreboard design, Coach Me Netball, Coach Me Soccer, Coach Me Hockey, Coach Me Baseball, Coach Me Umpire Netball, theAngler, Stock4Chairs, SubmitWise workspace data, DiskLint scan and cleanup data on Mac, Final Horn on iOS, CoachMe EqualPlay Lineup, and the Element Flux and A Traders Journey local-first designs), core planning, stock, reference, analysis, cleanup, timing, or game data remains on your device. No system is 100% secure, but we work to keep data protected.

8. Data retention and deletion

• Netball Scoreboard: data remains on your device unless you delete the app or reset your device.
• GoalCall: data is stored in the cloud to provide the service. If you leave a club/team, your access ends. Some records may remain to preserve team history and operational integrity (for example, message history for the group).
• Tap4Shift: employer account, staff, roster, attendance, location, audit, export, and subscription-entitlement records may be retained while an account, business, workplace, or entitlement is active and as needed for operational history, workplace audit needs, StoreKit reconciliation, troubleshooting, service integrity, legal compliance, and dispute handling. De-linked employer accounts may be retained for up to 30 days for cleanup.
• StreetTucker: account, customer profile, vendor profile, listing, review, favourite, report, ABN check, loyalty, purchase-entitlement, subscription, ad-measurement, and uploaded media records may be retained while an account, vendor listing, entitlement, or moderation record is active and as needed for safety, abuse prevention, fraud prevention, StoreKit reconciliation, troubleshooting, service integrity, legal compliance, and dispute handling.
• Yard2Road (planned): account and operational workflow records are expected to be retained while an account or workspace is active and as needed for operational history, safety, audit, legal compliance, troubleshooting, and service integrity.
• Beta Bridge: account, profile, listing, application, feedback, notification, entitlement, reward, ad-credit, analytics/operational-event, App Store Connect import result, and moderation records may be retained while an account is active and as needed for service operation, ranking/rewards, abuse prevention, fraud prevention, troubleshooting, and service integrity. In-app account deletion triggers account de-identification, removal of profile mappings, removal of saved listings, and queued cleanup or soft deletion of owned listings/media assets. Limited records may be retained where required for moderation, security, fraud prevention, payment/entitlement reconciliation, legal compliance, dispute handling, or protection of other users. Locally saved App Store Connect credentials should be removed using Clear ASC Credentials and revoked in App Store Connect if the user believes the key is compromised.
• Diamond Scoreboard (current design): core scoreboard data is expected to remain on your device unless you delete the app or clear/reset the device.
• Coach Me Netball (iOS): planning data currently remains on your device unless you delete the app or clear/reset the device.
• Coach Me Soccer (iOS): planning data currently remains on your device unless you delete the app or clear/reset the device.
• Coach Me Hockey (iOS): planning data currently remains on your device unless you delete the app or clear/reset the device.
• Coach Me Baseball (iOS): planning data currently remains on your device unless you delete the app or clear/reset the device.
• Coach Me Umpire Netball (iOS): learning progress, quiz history, bookmarks, searches, checklist progress, and match-day notes currently remain on your device unless you delete the app or clear/reset the device.
• FadSherpa: content/usage and ad-measurement records (if ads are enabled) may be retained for service operation, safety, fraud prevention, and reporting periods required by providers or law.
• CoachMe EqualPlay Lineup: lineup, rotation, team, stats, notes, report, and export data remains on your device unless you delete it in-app, delete the app, clear/reset the device, or choose to export/share it.
• CIF - Can I Fish (planned): saved trip preferences or local planning data are expected to remain on your device unless you delete the app or clear/reset the device. Query logs tied to cloud data providers, if introduced, may be retained for service reliability, abuse prevention, and legal compliance.
• theAngler (iOS): saved quick-reference preferences, favourites, or other local guide data currently remain on your device unless you delete the app or clear/reset the device.
• Element Flux (planned): gameplay saves, unlocked progression, and related local game settings are currently expected to remain on your device unless you delete the app or clear/reset the device.
• A Traders Journey (planned): gameplay saves, player name, fictional market progress, holdings, contracts, route state, crew-share rank, company/fleet progress, and related local game settings are currently expected to remain on your device unless you delete the app, reset the save in-app, or clear/reset the device. StoreKit subscription records are handled by Apple, and entitlement state may remain available as needed to restore purchases or handle refunds/revoked transactions.
• Final Horn (iOS): timer presets, custom profiles, and related local timing settings are currently expected to remain on your device unless you delete the app or clear/reset the device.
• Sports Hakken (planned): account, profile, saved event, saved sport/state, submitted event, report, source-import, admin review, moderation, and event-directory records may be retained while an account, event, source, submission, report, or moderation record is active and as needed for directory reliability, public event history, abuse prevention, troubleshooting, service integrity, legal compliance, dispute handling, or protection of other users.
• Am I Wrong? Vote (planned): account, profile, post, vote, comment or reply, report, block, filter, moderation, subscription, entitlement, free vote-limit, fraud-prevention, and safety records may be retained while an account, post, entitlement, report, or moderation record is active and as needed for community safety, abuse prevention, vote integrity, troubleshooting, service integrity, legal compliance, dispute handling, or protection of other users.
• Stock4Chairs (iOS): inventory records, stock counts, saved lists, locations, barcode or SKU values, selected item photos, reorder notes, generated export files, and related local settings remain on your device unless you delete the app, clear/reset the device, or choose to export, save, or share them outside the app. StoreKit purchase records are handled by Apple, and entitlement state may remain available as needed to restore purchases or handle refunds/revoked transactions.
• SubmitWise: workspace records, imported reports, selected app scope, competitor selections, manual entries, tasks, readiness checklists, settings, and analysis outputs remain on your device unless you delete them, delete the app, or clear/reset the device. App Store Connect credentials remain in Keychain until you remove them from this device or, if iCloud Keychain sync was enabled, remove them from all synced devices.
• DiskLint (Mac): scan results, local paths, cleanup selections, cleanup history summaries, ignored paths, user-selected folder bookmarks, and settings remain on your Mac unless you delete them, delete the app, clear/reset the device, or choose to share/export them. Items moved to Trash remain subject to your Mac's Trash behavior until you empty Trash or restore them.

If we receive a valid account or data deletion request, we will review it, verify the requester where appropriate, and handle the request within a reasonable period, subject to any records we must keep for security, fraud prevention, legal compliance, or preservation of other users' legitimate service history.

8A. Account deletion, consent, and your controls

For any released app that allows account creation, users should be able to request deletion of the full app account and associated personal data. This page also serves as the public web-based deletion resource for account-based apps.

• Website deletion requests: use the Suggestions & Ideas form with the subject line Account Deletion Request and include the app name and account email or identifier.
• In-app controls: when an account-based app is released, we expect the live build to provide a readily discoverable in-app deletion path where platform rules require it.
• StreetTucker in-app controls: StreetTucker includes a visible in-app Delete Account entry point, plus report controls for vendors and reviews. If you have an active Apple subscription, deleting your StreetTucker account does not automatically cancel Apple billing; manage subscriptions through your Apple account.
• Sports Hakken account controls: if released account features allow public account creation, Sports Hakken should provide a discoverable account-deletion request path. Public event records, source records, and moderation records may be retained or de-identified where needed for directory integrity, safety, legal compliance, or protection of other users.
• Am I Wrong? Vote account controls: if released account features allow public account creation, Am I Wrong? Vote should provide a discoverable account-deletion request path. Posts, votes, reports, block effects, moderation records, and safety records may be removed, retained, or de-identified where needed for community safety, vote integrity, legal compliance, dispute handling, fraud prevention, or protection of other users.
• Beta Bridge App Store Connect credentials: use Clear ASC Credentials in the Beta Bridge App Store Connect import screen to remove locally saved Key ID, Issuer ID, and .p8 key material from the device. Account deletion does not revoke an App Store Connect API key in Apple's systems; users should revoke keys directly in App Store Connect if they are no longer needed or may be compromised.
• SubmitWise App Store Connect credentials: use the SubmitWise credential removal controls to remove credentials from this device or from all synced devices where iCloud Keychain sync was enabled. Removing credentials from SubmitWise does not revoke an App Store Connect API key in Apple's systems; users should revoke keys directly in App Store Connect if they are no longer needed or may be compromised.
• DiskLint local controls: use DiskLint settings to adjust retention rules, ignored paths, project folder access, and cleanup preferences. You can also remove app-scoped folder permissions or delete local settings/history through normal macOS app and file controls where available.
• Permission withdrawal: you can turn off optional permissions such as notifications, location access, photos, or tracking in your device or browser settings. Unsubscribing from launch alerts is handled separately through email unsubscribe links or browser notification settings.

8B. Region-specific privacy rights and ad consent

Privacy laws differ by country and state. We apply this policy globally and provide additional controls where local law requires them.

• Using our apps: using an app means you acknowledge this Privacy Policy and the Terms / EULA. It does not by itself create consent where law requires an explicit opt-in or opt-out choice (for example, personalized ads or tracking in certain regions).
• EEA, UK, and Switzerland: where consent is required for personalized advertising or tracking identifiers, we use or require a consent flow and only use those identifiers after the required choice is granted. For apps using AdMob, including StreetTucker and A Traders Journey where ads are enabled, this includes consent messaging before personalized ads where required. You can withdraw or change choices later using available in-app/device privacy controls.
• United States (state privacy laws): users in applicable states may have rights to opt out of targeted advertising and certain data sharing/sale activities. Where required (including apps using AdMob), we support or require opt-out handling and restricted processing modes.
• iOS tracking permissions: where Apple AppTrackingTransparency applies, cross-app/web tracking for advertising uses Apple's permission prompt. If permission is not granted, tracking-linked identifiers must not be used for that purpose.
• Other jurisdictions: where local law grants rights such as access, correction, deletion, portability, objection, or complaint, you can contact us and we will handle verified requests in line with applicable law.

Important: this section provides general information and is not legal advice. We update this policy as laws and platform requirements change.

9. Children and age considerations

Our apps are intended for a general audience unless specifically positioned for workforce, business, developer use, or 16+ community use. GoalCall is designed for organised clubs and teams and may be used by under-18s where appropriate supervision and consent exists. Tap4Shift, Yard2Road, and Stock4Chairs are workforce/business-oriented and not designed for child-directed use. Beta Bridge, SubmitWise, and DiskLint are designed for developers and testers or developer teams and are not positioned as child-directed services. Am I Wrong? Vote is a user-generated social voting app with a 16+ rating and minimum age, and is not designed for children under 16. The Coach Me collection, CoachMe EqualPlay Lineup, Diamond Scoreboard, StreetTucker, FadSherpa, Sports Hakken, CIF - Can I Fish, theAngler, Element Flux, A Traders Journey, and Final Horn are intended for a general audience and are not designed to knowingly collect personal information from children.

10. Australia: Under-16 social media age restrictions (SMMA)

Australia has introduced a Social Media Minimum Age (SMMA) regime for age-restricted social media platforms starting from 10 December 2025. In general terms, the obligation is on platforms to take reasonable steps to prevent under-16s from holding accounts (there are no penalties for under-16s or parents/carers).

Am I Wrong? Vote is planned as a public or community user-generated social voting service with a 16+ minimum age. Because its final feature set may include public posts, voting, comments, accounts, and moderation, it requires separate age-restriction, online-safety, and store-compliance review before launch. Eligibility, account creation, and age-gating may be adjusted upward before release based on applicable law, platform rules, and safety design.

GoalCall, Tap4Shift, StreetTucker, Sports Hakken, SubmitWise, DiskLint, and Yard2Road are designed as private coordination, product/service or event discovery, developer analysis, cleanup, or workflow tools (not public social media platforms). The Online Safety (Age-Restricted Social Media Platforms) Rules 2025 exclude certain classes of services, including (for example):

• Services whose sole or primary purpose is messaging, email, voice calling, or video calling
• Online games
• Product/service information services (e.g., reviews, technical support, advice)
• Professional networking or professional development services
• Education and health services

Whether a service is in-scope depends on its features and how it operates. We regularly review our apps against regulator guidance and will update our approach if required.

Note: This is general information and not legal advice.

11. Launch-alert subscriptions (Notify Me)

When you subscribe to the website's Notify Me launch alerts, we process your email address, your selected channels (email and/or browser push), a fixed alert scope of all_apps, source-page attribution, and subscription timestamps.

• Email alerts: configured as double opt-in. You must confirm your email address before receiving launch alerts.
• Browser push: only enabled when you explicitly choose it and grant browser permission on an HTTPS page.
• Use limitation: launch-alert subscriptions are used for MrOldManDave app launch notifications, not unrelated marketing blasts.

You can unsubscribe from email alerts using the unsubscribe link in alert emails, or by contacting us. Browser push alerts can be disabled in your browser/site notification settings at any time.

12. Changes to this policy

We may update this Privacy Policy from time to time. The latest version will be available on this page at momd-digital.com/privacy-policy.html.

13. Contact

Support: Suggestions & Ideas (privacy questions and account/data deletion requests)
Website: www.MrOldManDave.com