ROUNDCALL

Privacy Policy

Published by Big Dog Studios LLC · Effective date: July 8, 2026 · Last updated: October 6, 2026

1. Information we collect

a. Usage and diagnostics (Google Firebase)

We use Firebase Analytics and Firebase Crashlytics (services provided by Google) to understand how the app is used and to find and fix crashes. Through these services we collect, under pseudonymous identifiers that are not linked to your name, email, or optional account:

• Product-interaction events (which screens and features are used, such as scoring a round);
• Device and app information (device model, operating-system version, app version);
• Pseudonymous identifiers — an app-instance identifier and a Firebase installation identifier used for diagnostics; on iPhone and iPad, the Identifier for Vendor (IDFV);
• Crash reports, stack traces, and performance/diagnostic data;
• Approximate ("coarse") location that Google derives from your IP address. We do not collect precise/GPS location.

This data is not tied to your name, email, or optional account (Section 1e). We do not use advertising identifiers on either platform: not the iOS advertising identifier (IDFA) — the app shows no App Tracking Transparency prompt because it does not track you — and not the Android Advertising ID, which the Android app disables entirely (it requests no advertising-ID permission).

b. App identifier (pseudonymous, or linked to your Apple Account if you sign in) and community poll (Google Cloud Firestore)

• When you first open the app, on every platform, it signs in anonymously with Firebase Authentication so it can read live updates (Section 1c) and the community poll ("who do you have?"). This creates a random, pseudonymous identifier that is not linked to your name, email, or phone. On iPhone and iPad the identifier is kept in the device keychain, which can survive deleting the app, so reinstalling can bring back the same identifier and your earlier poll votes. Firebase Authentication keeps a record of that identifier with its creation and last sign-in times.
• If you sign in with Apple on iPhone or iPad (Section 1e), that identifier usually becomes your account identifier. If your Apple Account is already linked from another device, the app switches to that existing account identifier instead. The earlier identifier is then no longer used, but it is not deleted: Firebase Authentication keeps its record, and any poll votes stored under it remain, until we delete them on request (Section 9).
• Voting (iPhone and iPad): your first pick on a fight is recorded as your vote so the app can show the crowd's split. The vote holds the bout, the fighter you picked, and a timestamp, and is stored under the identifier the app held when you voted. Each bout gets one vote, which cannot be changed; changing your pick later does not change your vote. If you delete your account, the votes stored under your account identifier are deleted with it (Section 9). The Android app shows the crowd's split but does not currently record votes.
• The app shows the crowd's split from server-maintained tallies that contain counts only; our database rules let each signed-in app user read only their own vote records.

Poll votes contain no name, email, or phone number.

c. Live updates (Google Cloud Firestore and Firebase Hosting)

The app reads published data from our servers so it can stay current between app releases: upcoming cards, live scoring, results, rankings, the roster, news, broadcast details, and fighter-photo takedown notices. These reads are made using the identifier described in Section 1b (your account identifier, if you signed in). When you open a matchup with a community poll, the app also looks up your own vote on that fight under that identifier. On iPhone and iPad the app additionally downloads data updates from our web host (Firebase Hosting); that request carries no identifier of yours. Like any network request, these reveal your IP address to Google. They send no name, email, or other content of yours.

d. Information stored on your device

Unless noted, the following are stored on your device and are not sent to us. Your device's own backup (iCloud on iPhone and iPad, or Google's Android backup) may include them under your Apple or Google account.

• Your saved scorecards and round-by-round scoring (if you sign in on iPhone or iPad, these also sync to our servers — Section 1e);
• Your fight picks (on iPhone and iPad, except your first pick on each fight, which is recorded as your poll vote — Section 1b) and your "MY SCORECARD" / season history;
• The card you choose to follow.

e. Optional account and scorecard sync (iPhone and iPad; Sign in with Apple and Google Firebase)

The app on iPhone and iPad lets you sign in with Apple so your scorecards can follow you to your other Apple devices. Signing in is optional, and the rest of the app works without it. The Android app does not offer an account at this time.

• What Apple shares with us: a signed token containing an identifier for your Apple Account that is unique to our developer team, which the app passes to Firebase Authentication to sign you in. We do not ask Apple for your name or email address. When you delete your account, you confirm with Apple again, and the one-time code Apple returns is passed to Firebase Authentication so that Apple can revoke the app's access.
• Your account: signing in links that Apple identifier, through Firebase Authentication, to the pseudonymous identifier described in Section 1b, which becomes your account identifier (or switches you to your existing account, as described there).
• What syncs: every scorecard that holds at least one round score, a finish call, or a finished card, including ones you scored before signing in. For each, the event name, identifiers for the two fighters, your round-by-round scores, whether the card is finished, whether you scored it while the fight was live, any finish call you made (method and round), a format version, and a server timestamp. Scorecards synced from your other devices are added to this device; a round you already scored on this device is never replaced. Two kinds of scorecard stay on your device and do not sync: one with more than five rounds, and one whose internal name cannot be used as a database record name (for example, because its event name contains a slash).
• Where it is stored: Google Cloud Firestore. Our database rules let only your signed-in account read or change your scorecards from the app, and other app users cannot access them. Big Dog Studios can access them through Firebase administrative tools and backups to operate and recover the service.
• What does not sync: your fight picks and the card you follow. Community-poll votes are stored separately (Section 1b).
• Stopping sync: the app does not currently offer a sign-out, or a way to remove a single synced scorecard. To stop syncing, delete your account (Section 9).

f. Fight-night notifications (Apple Push Notification service and Firebase Cloud Messaging)

The app can notify you when a card you follow goes live, and when the official scorecards and fight stats are in for a card you scored.

• When the app asks (iPhone and iPad): once, when the app first finds a finished scorecard — after you tap FINISH CARD, or as soon as the app opens if you already have one or one arrives through sync.
• When the app asks (Android): on Android 13 and later, once, the first time your scorecards change while a finished scorecard exists (for example, when you tap FINISH CARD), not when the app opens. On Android 12 and earlier there is no request, and notifications are allowed by default.
• Turning them off: there is no in-app switch. You can turn notifications off at any time in your device settings.
• To deliver notifications, your device registers with Firebase Cloud Messaging (a Google service) and, on iPhone and iPad, with Apple's push service. This creates a messaging token for your device, held by Google's messaging service for our Firebase project and by Apple. We do not copy it into our own database.
• Your device subscribes to topics named after events: the card you follow and the cards you scored (on iPhone and iPad, including cards synced from your other devices). Topic names are built from the event name alone and contain no name, account, or other identifier of yours. Google's messaging service records which topics your device's token is subscribed to.
• On Android, the app creates your device's messaging token when it starts, and subscribes to the cards you follow or score even if you have not allowed notifications. Alerts appear only if notifications are allowed.

2. Information we do NOT collect

We do not collect or request: your name, email address, phone number, mailing address, contacts, photos, precise/GPS location, health data, messages, financial account details, or your browsing/search history from outside the app. An account is optional, is offered on iPhone and iPad only, and Sign in with Apple shares no name or email with us (Section 1e). If you email us, we receive your email address and whatever you include in your message, and use it only to respond.

3. How we use information

We use the limited data described above only to:

• Operate core app features (community poll, live updates, scoring, optional scorecard sync, and optional fight-night notifications);
• Understand aggregate usage so we can improve the app;
• Diagnose crashes and improve stability and performance;
• Carry out account deletion, including keeping a deleted account's scorecards from being uploaded again and keeping poll votes from being cast again under that account's identifier (Sections 6 and 9);
• Keep backups and recover the service (Sections 1e and 6).

We do not use your information for advertising, profiling for ads, or sale to third parties.

4. We do not track you, show ads, or sell data

ROUNDCALL does not track you across other companies' apps or websites, does not contain third-party advertising or ad networks, and does not sell or share your personal information with data brokers. In Apple's App Tracking Transparency terms, our "Data Used to Track You" is none.

5. Third-party services

We rely on Google Firebase (Analytics, Crashlytics, Cloud Firestore, Authentication, Cloud Functions, Cloud Messaging, and Hosting) to provide the functionality above. On iPhone and iPad, optional sign-in uses Sign in with Apple and notifications are delivered through Apple's push notification service; see Apple's Privacy Policy. The optional in-app rating prompt uses Apple's in-app review on iPhone and iPad and Google Play's in-app review service on Android. Your use of the app is subject to Google's handling of that data; see Google's Privacy Policy and Firebase's privacy information.

If in-app purchases are offered in the future, any purchase is processed by Apple through the App Store or by Google through Google Play; we do not receive or store your payment-card details. (At launch, no purchase feature is active on either platform.)

6. Data retention

Analytics and diagnostic data are retained by our analytics providers for the periods they define and then deleted or aggregated. Community-poll votes are retained to display ongoing tallies, until you delete your account in the app (which deletes the votes stored under your account identifier) or we delete them on request. Firebase Authentication keeps a record of each app identifier with its creation and last sign-in times; a signed-in account's record is deleted when you delete your account in the app, and other records remain until we delete them on request (including the earlier identifier's record if signing in switched you to an existing account, Section 1b). If you sign in, your synced scorecards are kept until you delete your account; the app does not currently let you delete individual synced scorecards. When you delete your account in the app, we keep a minimal deletion record: the app's internal identifier for your account (Section 1b) and the date and time of the deletion, and nothing else. It contains no name, email address, Apple Account identifier, scorecards, or votes. Our servers use it to refuse scorecard uploads for that account for 7 days from the most recent time the deletion was recorded, and to refuse poll votes under that account's identifier for as long as the record is kept (Section 9). We currently keep this record with no set deletion date. If you ask us to remove it, we will do so once the account it belongs to no longer exists (after a finished in-app deletion, it already does), where we can identify the record as yours. On-device data (scorecards, picks, the card you follow) remains on your device until you delete the app or clear its data. After records are deleted, whether on request or by deleting your account, copies can remain in our database backups for up to about 14 weeks before those backups expire, and Google removes a deleted Firebase Authentication record from its own live and backup systems within 180 days. Your subscription to a followed card ends when you stop following it. Subscriptions for cards you scored remain until you delete the app. Turning notifications off in your device settings stops alerts from appearing but does not remove the subscriptions.

7. Children's privacy

ROUNDCALL is a general-audience sports app and is not directed to children under 13 (or the equivalent minimum age in your region). We do not knowingly collect personal information from children. The app requires no account (signing in with Apple is optional and shares no name or email) and never asks for a name, email address, or other directly identifying information. If you believe a child has provided us information, contact us and we will address it.

8. Your choices and rights

• The app has no in-app analytics switch, and device settings for advertising identifiers do not affect it because it uses none. Deleting the app resets its analytics identifiers, and you can ask us to delete analytics data (Section 9).
• We store no name, email, or other directly identifying information. An account is optional. If you sign in, your account consists of the Apple identifier linked to it and your synced scorecards. Deleting your account in the app deletes the account, the scorecards synced to it, and the poll votes stored under it. Section 9 explains what is kept.
• Poll votes are stored under the identifier the app held when you voted. Deleting your account in the app deletes the votes stored under your account identifier. That includes votes you cast on a device before signing in on it, because signing in keeps that device's identifier, unless signing in switched you to an account you already had (Section 1b). Votes stored under any other identifier, for example an earlier identifier left behind by that switch, or the identifier of a device where you never signed in, can be deleted by email request (Section 9). On-device data is under your control, and deleting the app removes it (on iPhone and iPad, except the sign-in identifier kept in the keychain — Section 1b).
• You can turn fight-night notifications off at any time in your device's settings.
• The app does not currently offer a sign-out. To stop syncing, delete your account (Section 9).
• Depending on where you live (for example, the EEA, UK, or California), you may have rights regarding personal data. To ask a question or make a request, contact us at the address below.

9. Data deletion

This section applies to the ROUNDCALL app, published on the App Store and Google Play by Big Dog Studios LLC, and explains how to have the data described above deleted.

If you signed in with Apple (iPhone or iPad): tap the About (i) button on the Home screen, then under ACCOUNT tap Delete account, confirm, and confirm again with Apple. This asks Apple to revoke the app's access to your Apple Account, records the deletion on our servers, deletes the scorecards synced to your account and the community-poll votes stored under it (including votes cast on another of your devices while it was signed in to this account), and then deletes your account. If Apple's revoke does not succeed, deletion can still go ahead, and if it does, the app tells you how to remove the app's Sign in with Apple access yourself in your Apple Account settings. Scorecards saved on your device stay there until you delete the app, and the app carries on without an account under a new pseudonymous identifier (Section 1b).

After you delete your account: for 7 days, our servers refuse any scorecard upload for that account, so another iPhone or iPad that is still signed in to it cannot put your scorecards back. Our servers also refuse any new poll vote under that account's identifier for as long as we keep the deletion record described below, so the deleted votes cannot be cast again under it.

If deletion does not finish: the ACCOUNT section tells you whether the account could not be deleted, whether deletion is not finished, or whether the app is not sure because our servers did not answer in time (in some cases, for example if the app was closed before the deletion was recorded on our servers, it may show nothing). Your account is not deleted, except that when the app is not sure, the last step may have reached our servers; the app checks with them. Depending on how far deletion got, the app may already have asked Apple to revoke its access to your Apple Account, and some of your synced scorecards or poll votes may already have been deleted. If it got as far as recording the deletion, our servers refuse uploads of your scorecards (downloading them still works) for 7 days from the most recent time the deletion was recorded, and each retry that gets that far starts the 7 days again. Poll votes can then no longer be cast under your account's identifier for as long as we keep the deletion record (your picks are still saved on your device). Scorecards on your device are not affected. Retry from the ACCOUNT section: a retry completes a half-finished deletion, and is safe if an earlier attempt already finished. If it still does not finish, use the email request below. We will delete the account and its remaining data where we can identify them as yours; we may need details from you to do that, and if we cannot identify them, we will tell you.

In-app deletion does not remove:

• A minimal deletion record. We keep the app's internal identifier for your account and the date and time of the deletion, and nothing else, so our servers can refuse uploads for that account and votes under its identifier as described above. We currently keep it with no set deletion date. If you ask us to remove it, we will once the account it belongs to no longer exists, where we can identify it as yours (Section 6).
• An earlier identifier. If signing in switched this device to an account you already had (Section 1b), the pseudonymous identifier the device used before is not deleted, and neither are poll votes stored under it. To delete those, use the email request below.

If you never signed in, you have no account to delete. The app may still have stored a small amount of pseudonymous data with us, and you can ask us to delete it at any time.

How to request deletion:

1. Email support@bigdogstudios.app with the subject line "Data deletion request."
2. Because no name or email is attached to the data we hold, we may work with you to identify the records that came from your installation (for example, roughly when you used the app and, on iPhone or iPad, which fights you voted on).
3. We act on verified requests within 30 days and confirm by reply when deletion is complete.

What is deleted on request:

• Community-poll votes. Each vote is a single record — the bout, your pick, and a timestamp — stored under the identifier the app held when you voted. We delete the vote records we can identify as yours.
• Your Firebase Authentication record for the app identifier we can identify as yours.
• Synced scorecards that remain on our servers, for example because an in-app deletion did not finish, where we can identify them as yours.
• The deletion record described above, once the account it belongs to no longer exists and where we can identify it as yours.
• Analytics and diagnostic data. We can delete Firebase Analytics data for your app instance only if we can identify it. The app does not display that identifier, so we will tell you if we cannot. Crash and diagnostic records also expire automatically under the retention periods described in Section 6.

What is kept: once we complete a deletion request, none of the records covered by that request that we could identify as yours remain in our live database, though copies can remain in our database backups for up to about 14 weeks, and Google removes a deleted Firebase Authentication record from its own live and backup systems within 180 days (Section 6). If we cannot determine which records are yours — a consequence of collecting no name or email — we will tell you. Those records contain no name, email, or phone number, and the analytics and diagnostic portions still expire automatically under Section 6.

Notification data: we never hold your device's messaging token, so we cannot find or delete it, or its topic subscriptions, on request. A followed card's subscription ends when you stop following it, and notifications stop reaching your device once you delete the app.

Your picks (other than, on iPhone and iPad, the first pick on each fight, which is stored as a poll vote and can be deleted on request, or through in-app account deletion if it is stored under your account identifier, above) are stored only on your device and in its own backups. So is the card you follow, and so are your scorecards unless you signed in; synced scorecards are deleted through in-app account deletion. The app does not save what you type into search. Deleting the app (or clearing its data) removes what the app stores on your device, except that on iPhone and iPad the sign-in identifier can remain in the device keychain (Section 1b).

10. This website

Our websites (bigdogstudios.app and roundcall.app) use two Google measurement tools:

• Google Analytics (GA4) — to measure aggregate site traffic, such as pages visited, referral source, and the approximate location Google derives from your IP address.
• Google Ads conversion tracking — to measure how many visitors who arrive from our Google ads tap through to the app's store listing (App Store or Google Play). We keep ad-personalization signals turned off, so this is used for conversion measurement only: we do not build advertising profiles about you and do not run remarketing or retargeting from the sites.

Both tools set Google cookies and identifiers. Apart from these two Google measurement tools, the sites carry no other trackers, ask you for no personal information, and serve their fonts, images, and video themselves. This section describes the websites only — the ROUNDCALL app uses no advertising identifiers and does not track you across other apps or websites (see Sections 1, 2, and 4).

11. International users

The app and its service providers may process data in the United States and other countries. By using ROUNDCALL, you understand your information may be processed in the United States.

12. Changes to this policy

We may update this Privacy Policy as the app evolves. When we do, we will revise the "Last updated" date above and post the new version at this URL. Material changes will be reflected here before they take effect.

13. Contact us

Big Dog Studios LLC
Email: support@bigdogstudios.app

For questions about this Privacy Policy or ROUNDCALL's data practices, email us at the address above.

14. Intellectual property and rights complaints

If you believe anything on this site or in the ROUNDCALL app infringes your rights — copyright in a photograph or other material, a trademark, or your rights in your own name or likeness — contact:

Copyright Agent, Big Dog Studios LLC
Email: support@bigdogstudios.app
Subject line: Rights complaint

Please tell us what the material is and where you saw it, what right you hold and how you hold it, and how to reach you. A screenshot is usually enough to identify it.

We act on any complaint we consider credible within 24 hours of receiving it, whether or not a formal legal notice is sent. Acting may mean removing the material while we look into it. We will reply and tell you what we did.