Bugzila Car Play Billing Disclosure
1. Premium purchase
Google Play manages checkout, payment methods, taxes, order processing, refunds, and the Google account associated with the purchase. Bugzila Car Play does not receive or store payment-card numbers.
2. Purchase verification and acknowledgement
To verify Premium entitlement, Bugzila Car Play sends the Google Play purchase token over HTTPS to the dedicated Bugzila billing verification backend. The backend validates the purchase using the Google Play Developer API.
For an eligible transaction in the PURCHASED state, the backend may perform Google Play acknowledgement before returning a completed VERIFIED result. If Google Play already reports the transaction as acknowledged, the backend treats that state idempotently and does not need to create a duplicate acknowledgement side effect.
3. Replay and duplicate-processing protection
The backend does not store the raw purchase token in the replay ledger. Instead, it derives a one-way SHA-256-based fingerprint and uses that value as the durable ledger identifier.
The ledger may retain minimal verification metadata such as package name, product ID, purchase state, acknowledgement state, verification decision, verified/test-purchase indicators, first/last verification timestamps, acknowledgement timestamp, verification/replay counters, and minimal Google/backend status information required for replay prevention and troubleshooting.
Raw purchase tokens are not intentionally written to Analytics, Crashlytics, diagnostic screens, support reports, configuration backups, or the D1 replay ledger.
4. Premium entitlement and temporary verification failures
A new Premium grant requires a valid Google Play purchase and successful verification according to the app's current entitlement rules. Pending, cancelled, or invalid-product states do not grant a new Premium entitlement.
If the billing verification infrastructure, network, backend, or ledger is temporarily unavailable, the app may report the verification state as UNKNOWN. A temporary infrastructure failure is not treated as proof that a previously valid purchase has become invalid, and the app is designed not to automatically revoke an entitlement that was already valid solely because of that temporary verification failure.
5. Restore and device changes
Restore and silent entitlement checks use the user's Google Play purchase state. Reinstalling the app or changing devices may require the same Google account used for the original purchase and availability of the purchase through Google Play.
6. Backup & Restore is separate from Premium
Bugzila Car Play configuration backup files do not contain Premium entitlement, purchase status, raw purchase tokens, or order identifiers. Importing a configuration backup cannot unlock Premium or transfer Premium ownership.
7. Refunds and disputes
Refunds, cancellations, charge disputes, and payment issues are handled according to Google Play policies and the transaction state reported by Google Play.
8. Privacy
For details about purchase-related data, the one-way replay ledger fingerprint, retention, security, and deletion requests, see the Bugzila Car Play Privacy Policy.
9. Contact
Developer: Bugzila Labs
Email: bugzila@gmail.com