CardBal

Last updated: September 26, 2026

This privacy policy describes how the CardBal app ("CardBal") handles information when you use it. CardBal is published by Kitta Co.

Station Reports You Submit

When you submit a missing-station or station-code correction report, CardBal sends the station name, report type, the station code or suggested code, and any optional line, operator, city, country, or notes you enter. You may also choose a pin on a map or use your current location. If you do, the exact coordinates of that pin are sent. CardBal does not read your location automatically for reports.

Each report also includes a SHA-256 hash of the associated card ID, an app-specific device ID, the app version, and the card family. The raw card ID and trip history are not sent with a station report. We store submitted reports in Cloudflare D1 to review requests and improve station data. The public request list at cardbal.ieb.app shows station details and an approximate location when a pin was supplied. It does not show the card ID hash, device ID, app version, notes, or exact coordinates.

Optional Korean Card Research Data

If you enable Korean card crowdsourcing, eligible T-money and EZL/Cashbee scans may upload technical trip-record data to help improve decoding. This can include raw trip-record bytes, station and fare fields, a deduplication hash, a SHA-256 hash of the card ID, and the last four characters of the card ID. You can turn this setting off at any time. This data is not collected through station reports.

Data on Your Device

Transit card information, scan results, imported backups, card artwork, and app settings may be stored locally on your device according to how the app and your operating system work. That data remains under your device and account unless you submit a station report, enable Korean card crowdsourcing, explicitly export it, sync it through platform services, or share it using operating system features.

NFC and Transit Card Data

CardBal reads supported transit cards through your device NFC hardware. Decoded balances, transaction records, station codes, route names, and related card metadata are used to show card details and maps in the app. This processing happens on device except for the optional submissions described above, or when you choose an explicit export, import, sharing, backup, or sync flow.

Platform and Distribution

Your device manufacturer, operating system provider, and app store provider may process technical, crash, purchase, or billing information according to their own terms and privacy notices when you download, purchase, update, back up, or use apps. That processing is not governed by this policy.

Changes

If CardBal's data practices change materially in a future version, we will update this page and, where required, provide notice through the app or store listing.

Contact

Questions about this policy or requests concerning submitted data: [email protected]