Privacy Policy
This policy explains what data the Warranty Tracking app developed by Deepnode Studios may process, when it is processed, which third-party services are involved, and how users can exercise data deletion rights. The policy is based on the current Android feature set of the app.
Quick summary
- Records stay in the local database on the device by default.
- Cloud backup is only used when a linked account and premium access are enabled.
- OCR and barcode scanning are optional flows initiated by the user.
- Accounts and remote data can be deleted from inside the app.
Third-party services
- Firebase Authentication
- Cloud Firestore
- Firebase Storage
- Firebase Analytics
- Firebase Crashlytics
- Google Mobile Ads (AdMob)
- Google Play Billing
1. Data processed by the app
The app processes the information entered by the user for warranty and inventory tracking. This may include product name, brand, model, serial number, purchase date, warranty period, price, currency, notes, and archive status. Users may also attach a product image or an invoice or warranty document as a photo or PDF file.
2. Local storage by default
Inventory records and attachments are stored in the app's local database and app-specific device storage. Reminders are scheduled locally and do not rely on a remote push service.
3. Identity and account information
On first launch, the app may create an anonymous Firebase Authentication user ID to manage app state technically. If the user enables cloud backup or account linking, they may connect a Google or other supported identity provider. In that case, the app may also process email address, display name, and linked provider information.
4. Cloud backup and sync
Cloud backup is optional and only available when a linked account and premium access are active. When the feature is enabled, the following data may be transferred to Firestore and Firebase Storage:
- Inventory records: product name, brand, model, serial number, price, purchase date, warranty period, notes, and archive status.
- Attachments: product visuals and invoice or PDF files selected by the user.
- Account context: user ID, linked providers, and when available, email address and display name.
If cloud backup is not enabled, this data is not sent to remote servers and stays on your device.
5. Ads, analytics, and diagnostics
The free tier may use Google Mobile Ads (AdMob). In addition, Firebase Analytics may process events such as app opens, screen views, scan results, exports, and cloud sync outcomes, while Firebase Crashlytics may process crash reports and diagnostics. These services are used to improve performance and stability.
6. Purchases and premium
Premium features are provided through Google Play Billing. The app uses purchase status and the related product identifier to verify premium access. Payment card details are not stored by the app or by Deepnode Studios, as payment processing is handled by Google Play.
7. Permissions and device features
- Camera: used on demand for product or invoice photos, OCR, and barcode scanning.
- File selection: used when the user chooses a PDF invoice or a gallery image.
- Notifications: used to schedule local reminders for warranty expiry dates.
- Internet: used for Firebase, ads, premium verification, and similar network-connected features.
8. Data safety summary
The summary below reflects the operational view you can use while filling out the Google Play Data Safety form. Update it if the app's data processing changes.
Email address
Only processed when the user links an account with Google or another supported provider. Purpose: account linking, cloud backup context, and preserving premium status.
User ID
The anonymous Firebase UID or linked account UID is used for app state and optional cloud backup.
Product and invoice attachments
If the user selects a photo or PDF, the app stores it locally. When cloud backup is active, these files may also be uploaded to Firebase Storage.
Inventory and warranty records
Product details, notes, and warranty dates are stored in the local database and synchronized to Firestore when cloud backup is enabled.
Analytics events
Screen views, record creation, scan success, export actions, and cloud sync events may be sent to Firebase Analytics.
Crash logs and diagnostics
Crashlytics may process crash records and stack traces when the app encounters an error.
Purchase status
Purchase results and related product identifiers may be used for premium verification through Google Play Billing. Full payment card data is not kept by the app.
Ad-related data
Device and ad ecosystem data may be processed by Google for AdMob ad delivery in the free tier.
9. Sharing of data
The app does not sell user data. Information may only be shared with the service providers listed above for technical purposes such as operating the app, backup, advertising, premium verification, analytics, and diagnostics.
10. Retention period and security
Local data stays on the device until the user deletes it or removes the app. Cloud backup data may remain until the user deletes the backup or their account. Reasonable technical and organizational safeguards may be used, but no system can guarantee absolute security.
11. Account and data deletion
The user can delete local inventory records, local attachments, remote cloud backup data, and the current Firebase account from the in-app account or data deletion flow. After the process, the app may return to a new anonymous account. If you need help, contact [email protected].
12. Policy updates
This policy is updated when the app's data handling behavior changes. The date on this page is refreshed whenever a new version introduces an important privacy-related change.