Bracket Hub: Tournament Maker — Privacy Policy
Last updated: 2026-10-05
This privacy policy applies to the mobile app "Bracket Hub: Tournament Maker" for Android:
- Google Play: package com.simonj.bracket, developer "Global Utility App Maker"
The app is developed and operated by Kyu-Hee Jang (Google Play developer name: Global Utility App Maker).
Contact: wkdrb2100@gmail.com
OVERVIEW
Bracket Hub does not require an account, and we do not sell personal information. You create tournaments (single or double elimination, round robin, Swiss, or groups followed by a knockout), enter results, and can export the event as a PDF or poster image, show it on a venue display, or back it up to files. Your tournaments are kept in the app's storage on your device. The app also uses Google services and an advertising mediation partner for analytics, crash reporting, remote configuration, and advertising.
TOURNAMENTS, NAMES, AND FILES YOU CREATE
Tournaments contain the names you type for the tournament and its entrants, which may be names of other people. Only enter names you are allowed to use. Exported PDFs and poster images show the tournament name, entrant names, pairings, results and standings. The venue display shows the tournament name and match cards with entrant names and scores, and moves to the next page every ten seconds unless you pause it. Backup files contain the tournament data described below, and "Export raw data" files contain the saved text of the tournaments being recovered. Files are made on your device; the app does not upload them. A file leaves the app only when you choose a destination in the system share sheet, which opens when you tap Share (for one file, or for all parts of a backup together) or Export raw data.
INFORMATION STORED ON YOUR DEVICE
For each tournament the app keeps its name, format and settings (seeding, points, ranking rules, group and qualification options), the dates it was created and last changed, its entrants (name, optional rating, seed and random draw number), the matches with their results (including sets and walkovers), qualifiers, the champion, and a revision history of corrected results with the earlier results. Each tournament has 2 to 256 entrants; the app does not save or restore a tournament outside that range. There is no fixed limit on the number of tournaments. The app also keeps a list of the IDs of tournaments you deleted.
Backups and exported files are kept in the app's own storage, as described under STORAGE AND YOUR CONTROL. The app may also store basic operating information such as cached advertising settings and a cached More Apps list.
The developer does not run a server that receives your tournaments. The app reads developer-controlled advertising settings and a More Apps list from Google Cloud Firestore, but it does not upload your tournaments or files. When you open More Apps, app icons are loaded from the web addresses in that list.
ANALYTICS, CRASH REPORTING, AND ADS
Google Firebase Analytics may process limited app-usage and technical information, such as app launches, the splash screen view, opening the privacy policy or More Apps in the menu, review-prompt requests and their outcome (with where they were opened from), ad revenue events (ad format, value, currency and precision), app version, device type, and app-instance identifiers. These events do not include tournament names, entrant names, results, or your files.
Google Firebase Crashlytics may process crash reports and related technical information needed to diagnose app problems.
The app shows ads through Google AdMob (banner, native, interstitial and app-open ads). AdMob may also request ads from the InMobi mediation network. Google and InMobi may process advertising identifiers and device, app, consent, network, and ad-performance information to provide and measure ads, and may use an IP address to estimate an approximate location even though the app has no location permission.
The banner appears only on the event list, and a native ad may appear in the exit dialog. Full-screen ads may appear when the app starts, when you come back to the event list from another app, and on the screen shown after a tournament is completed or a file is exported. The app does not start a full-screen ad while another tournament screen, such as result entry, pairings, history, export, backup or the venue display, is open.
PERMISSIONS AND ADVERTISING CHOICES
The app declares internet access, the Android advertising ID permission and vibration, which is used for short feedback when you tap some buttons or save a result and does not show a request. The app does not request camera, microphone, location, contacts, photo library, Bluetooth, health data, or notification permissions. Restoring a backup uses the system file picker, which gives the app only the files you select. The venue display keeps the screen on and switches to full-screen landscape while it is open.
When the app starts, Google's consent message (UMP) is checked first. Where it is required (for example in the EEA and UK), personalized advertising stays off unless your choice allows it, and ads are requested only when Google's consent result allows it. Where no consent message is required, ads may be personalized. If the consent message cannot be loaded, the app still requests non-personalized ads and personalized advertising stays off. The app works whatever you choose. Where Google requires it, the app menu shows "Privacy choices", which reopens the consent message so you can change your advertising choice.
STORAGE AND YOUR CONTROL
You can delete a tournament with Delete in the event list. This removes the tournament's saved file from the app's library; its ID stays in the deleted list and is included in later backups so that a restore does not bring it back. The app then also tries to remove the PDFs and poster images it exported for that tournament from the app's storage. Copies of that tournament in earlier backups and "Export raw data" files, and any copies you shared or saved elsewhere, stay. An exported file the app could not remove then may stay until a later start removes it.
"Backup" writes your readable tournaments and the deleted-ID list to a set of files (a manifest and numbered parts) in the app's private storage; tournaments that cannot be read are left out. Each backup is kept there and the app does not delete earlier backups. PDFs, poster images and "Export raw data" files are written to an exports folder in the app's storage. Each time the app starts and has loaded your tournament list, it looks at these files made before that start: for each tournament in your library it keeps the three newest PDFs and poster images and tries to delete older ones, it tries to delete the PDFs and poster images of tournaments that are no longer in your library, and of the remaining files ("Export raw data" files and older exports not linked to a tournament) it keeps the three newest and tries to delete older ones. Files made after that start stay until a later start, and if the tournament list cannot be loaded, no exported files are deleted at that start. Temporary files used while rendering a PDF or poster are deleted after use, and any leftovers beyond the three newest are deleted at a later start. "Restore backup" reads the files you pick, checks a temporary copy that is deleted when the restore ends (or at the next start if the app closes first), and merges their tournaments into your library (deleted tournaments stay deleted, and the app tries to remove their exported PDFs and poster images). The app has no separate control to remove backups or exported files; clearing the app's data on Android or uninstalling the app removes them from the app's storage, but where you sent or saved files is your choice, and the app does not delete copies kept elsewhere. Local data may be included in a Google or device backup depending on your backup settings; uninstalling normally removes the active copy but may not remove an older backup.
Because we do not receive your tournaments, we cannot delete them for you; the controls above remove them from the app. For questions about data processed by Google or InMobi, or to ask us for help with a privacy request, contact us at the address below.
Data processed by third parties is retained according to their service settings and policies. We use these services under their applicable terms, and we ensure that third-party service providers with whom we share user data provide the same or equal protection of that data as stated in this policy.
- Google Privacy Policy: https://policies.google.com/privacy
- Firebase privacy information: https://firebase.google.com/support/privacy
- Google advertising technologies: https://policies.google.com/technologies/ads
- InMobi Privacy Policy: https://www.inmobi.com/privacy-policy
SECURITY
Your tournaments, backups and exported files are kept in the app's private storage on your device, which the operating system protects from other apps; they are not separately encrypted by the app, so protect your device with a screen lock. Apart from the limited analytics events described above, the app does not upload your saved data. Communication between the app and Google services and the ad mediation partner uses encrypted connections (HTTPS/TLS). No method of storage or transmission is completely secure, but we limit what the app collects to what is described in this policy.
IMPORTANT NOTICE
Brackets, standings and qualifiers are calculated from the results you enter, using the format and ranking rules you choose; the app does not check results against any official source. It is a tool for running events and is not intended for betting or gambling. Names shown on exports and the venue display can be seen by anyone who views them.
CHILDREN
The app is not directed to children under 13, and we do not knowingly collect personal information from children.
CHANGES
We may update this policy if the app or its services change. The date above shows the latest revision.
CONTACT
Kyu-Hee Jang (Google Play developer: Global Utility App Maker)
Email: wkdrb2100@gmail.com