Subbing, on the web at subbing.net and as the mobile app. Last updated 6 November 2026.
Subbing is a networking quiz with no accounts and no login. This page lists what is processed, why, where it goes and how to control it.
Submitting a competitive score is optional. When you submit, the name you type, the score, the topic, mode and difficulty, the number of answers and the time are stored in the app's database and shown publicly on the board for that topic. Any name works; it does not have to be yours.
To keep the board honest, the server stores a salted one-way hash of your IP address next to each submission in a private collection that no client can read. It is used for rate limiting and abuse detection only, and the address cannot be recovered from it. The round session used to verify a score is deleted within two hours.
A report sent from the app contains the category, your message, the app version and platform, the theme, the topic, mode and difficulty you were in, and the reply address if you give one. It is stored in a private collection and emailed to the developer, who uses it only to answer you and fix the problem. Reports are rate limited with the same IP hash as above and deleted once handled, or earlier on request.
The free version shows a banner on the home and results screens and an occasional full-screen ad between rounds: Google AdMob in the app, Google AdSense on the web. Google may use cookies or the device's advertising identifier to show and measure ads, as described in how Google uses data in ads.
Subbing Pro is sold through the app store you installed from, which handles payment and holds the payment details. RevenueCat checks whether the purchase is active: it receives an anonymous app-generated identifier and the store receipt, never a name or email. See the RevenueCat privacy policy.
Firebase Analytics counts rounds started and finished, the modes and topics used, settings opened, purchases and ad events, so the app can be improved. On the web it runs without cookies unless you grant storage consent. Firebase Crashlytics collects crash reports from the app: device model, OS version and the stack trace. No name, email or precise location is collected.
Requests to the server carry a Firebase App Check token so that only the real app and site can submit scores and reports: reCAPTCHA v3 on the web and the platform's app attestation service in the app. Google processes device signals for that check.
Streak, totals, accuracy by question type, personal bests, round history, the chosen theme, topic and mode, and the last leaderboard name are kept in the app's local storage and never uploaded. Settings > Reset stats, streak and history clears the progress; uninstalling the app or clearing site data removes everything.
Subbing is made for students and professionals studying networking and is not directed at children under 13. No personal data is knowingly collected from children.
Depending on where you live, you can ask for access to, correction of or deletion of your data, and withdraw consent at any time. Email napahlm.dev@gmail.com with the leaderboard name or the report concerned, or start from the support page. Requests are answered within a month, usually within days.
This page changes whenever the app's data practices do; the date at the top is the latest revision.