1. Developer and Contact
Subs is provided by Soosu Studio. For privacy questions, data requests, or support, please contact us at contactus@soosu.studio.
2. Information Subs Handles
Subs helps you track subscriptions, upcoming payments, monthly cost trends, payment calendars, reminders, widgets, service icons, and optional Google account sync. The app does not ask for your contacts, precise location, microphone, or calendar access.
- Subscription records: service name, product or plan name, web domain, service icon URL, start date, billing cycle, amount, currency code, payment method, memo, card color, created time, and plan history.
- Account information: if you sign in with Google, Subs uses Firebase Authentication and may handle your Firebase user ID, display name, email address, profile photo URL, and Google sign-in token needed to authenticate your account.
- Cloud sync data: when signed in, subscription records and plan history may be synchronized to Firebase Firestore under your user account so the data can be backed up and used across devices.
- Custom icon images: if you select and upload a service icon, the image file, content type, generated file name, and download URL may be stored in Firebase Storage.
- Preset and icon data: Subs may load subscription preset information from Firebase Realtime Database. When loading brand icons, service domains or icon URLs may be requested from external image services such as Google favicon services and images.weserv.nl.
- Exchange rate data: Subs may request exchange rates from open.er-api.com to estimate totals in your selected main currency. The request does not need your subscription list, but the provider may process standard network information such as IP address and request metadata.
- App settings: notification preferences, day-before payment reminder settings, main currency, theme mode, language settings selected through Android, and app version information.
- Widget settings: upcoming-payment widget configuration, including background transparency and the subscription payment information shown by the widget.
- Usage, diagnostic, and integrity information: Subs uses Firebase Analytics, Firebase Crashlytics, Firebase App Check with Play Integrity, Google Play services, and Android system services. These services may process app interaction, screen view, crash, device, app version, operating system, diagnostic, and integrity information according to their own policies.
3. How We Collect Information
- Subscription records are created when you add, edit, import from a preset, or delete subscription information in the app.
- Account information is collected when you choose to sign in with Google.
- Cloud sync data is uploaded and downloaded through Firebase Firestore while you are signed in.
- Custom icon images are uploaded only when you select an image and use the icon upload feature.
- Preset and brand icon information is loaded when the app displays service presets or service icons.
- Exchange rates are requested when the app needs to convert foreign-currency subscription amounts.
- Settings and widget preferences are stored when you configure app settings, reminders, currency, theme, or widgets.
- Firebase Analytics, Firebase Crashlytics, Firebase App Check, Google Play services, and Android system services collect data through their SDKs or platform features when the app is used.
4. How We Use Information
- To save, display, update, and delete your subscription records.
- To calculate upcoming payments, payment calendars, estimated paid amounts, monthly totals, and currency-converted totals.
- To show reminders and notifications when you enable them.
- To update home screen widgets and remember widget appearance settings.
- To provide optional Google account sign-in, sign-out, account deletion, backup, and cross-device sync.
- To upload and display custom service icons and load preset service icons.
- To maintain, debug, secure, measure, and improve Subs.
- To protect backend services from abuse through app integrity checks.
- To respond to support or privacy inquiries that you send to us.
5. Local Storage, Cloud Sync, and Sharing
Subs stores subscription records in a local Room database named subs.db. App settings are stored in local shared preferences named subs_settings, and widget settings are stored in local shared preferences named upcoming_payments_widget_settings. Brand images may be cached on your device.
If you do not sign in, your subscription records are primarily stored on your device, subject to Android backup and device transfer behavior. If you sign in with Google, Subs may synchronize subscription records and plan histories to Firebase Firestore under your account. If you upload custom service icons, those images may be stored in Firebase Storage.
We do not sell your personal information. Data may be processed by third-party services used by Subs, including Firebase Authentication, Firebase Firestore, Firebase Storage, Firebase Realtime Database, Firebase Analytics, Firebase Crashlytics, Firebase App Check, Google Sign-In, Google Play services, Google favicon services, images.weserv.nl, open.er-api.com, Android system services, and device backup services. Those services are governed by their own privacy terms.
If you send a support email, share a screenshot, export information through another app, use device backup, or transfer data through another service, that action is controlled by you and may be handled by the service you choose.
6. Permissions
- Internet and network state: used for Firebase services, Google sign-in, subscription preset data, icon loading, custom icon upload, exchange rates, analytics, crash reporting, app integrity, and related service communication.
- Post notifications: used for subscription and day-before payment reminders when enabled.
- App widget access: used through Android app widget APIs to show upcoming payments on your home screen when you add the widget.
- Image picker or document access: handled by Android when you choose a custom icon image. Subs uses the selected image only for the icon upload or display workflow you start.
7. Account Deletion, Retention, and Deletion
- Local subscription records, settings, widget settings, and cached images remain on your device until you delete them, clear app data, or uninstall the app.
- When signed in, synced subscription records and plan histories may remain in Firebase Firestore until you delete your account, sign out and stop syncing, or request deletion where applicable.
- The in-app delete account action deletes your Firebase account's sync document and then deletes the Firebase user account. Local data on the device may remain unless you clear app data or uninstall the app.
- Custom icon images uploaded to Firebase Storage may remain until deleted through app or backend cleanup processes, or until you contact us for assistance.
- Android device backup may back up app data when enabled on your device.
- Firebase Analytics, Firebase Crashlytics, Firebase App Check, Google Play services, and other third-party providers retain data according to their own settings and policies.
- Support emails are retained only as long as reasonably necessary to respond to your request, maintain records, or meet legal obligations.
8. Security
We use reasonable technical and organizational measures to protect information handled by Subs, including Firebase security features and Android platform storage. Subscription records can include sensitive spending, billing, and account notes, so you should protect your device, Google account, backups, screenshots, and any information you share. No method of transmission or storage is completely secure.
9. Children's Privacy
Subs is not directed to children under the age required by applicable law to use online services without parental consent. We do not knowingly collect personal information from children. If you believe a child has provided personal information through Subs, please contact us.
10. International Processing
Information processed by Firebase, Google, open.er-api.com, images.weserv.nl, or other service providers may be stored or processed in countries outside your country of residence. We take steps intended to use service providers with appropriate privacy and security commitments.
11. Changes to This Policy
We may update this Privacy Policy from time to time. When we make changes, we will update the date below and publish the revised policy on this page.