Scope and developer
This policy describes Subscription Manager (com.vinsontech.subscriptionmanager) by Vinson Developers. It distinguishes the published 2.0 (code 3) app from the planned native 3.0 (code 4) update. Features described as belonging to 3.0 become available only when that update is released. Contact vinsondevelopers@gmail.com for privacy questions.
Subscription records on your device
You enter subscription names, prices, currencies, billing dates, categories and other optional details. The native update also stores payment history, notes, reminder preferences and app settings. These records are kept in the app's private device storage for tracking and displaying your subscriptions. The app does not require a Subscription Manager account or your subscription-service passwords, and does not connect to your bank or automatically charge or cancel your subscriptions.
The native update can migrate records from the earlier app's local database. Recovery and migration copies may contain older records, even after an individual record is edited or deleted.
Internet requests and service logos
In the native 3.0 update, catalogue and recognised service names load their icons from Google's favicon service. A request includes the catalogue service domain and standard connection information, including your IP address. It does not include your price, payment history, notes or a subscription-service password. Generic custom names are not used to guess external domains. Icons may be cached on the device; the app displays a generic symbol while an icon is unavailable.
Google operates this service. Its processing is subject to Google's Privacy Policy. We do not control its server logs or promise a particular provider retention period. Your saved records remain usable offline, although online icons need an internet connection.
Earlier version: currency conversion and optional voice input
The published 2.0 app requests currency exchange rates from api.frankfurter.app. The reviewed request sends the source and target currency codes and normal network information such as your IP address; it does not send subscription amounts in that request. The Frankfurter API documentation states that its public API does not retain personal data, IP addresses or request-URL logs. The native 3.0 update instead uses bundled reference rates and does not make this exchange-rate request.
The published 2.0 app also offers optional voice entry using Android's speech-recognition service and microphone permission. When you start voice entry, the speech provider selected on your device may send your audio to its servers and return recognised text. What you say can include subscription names, amounts, currencies or other information. This is not guaranteed to be on-device processing. The provider and its storage, security and deletion practices depend on the speech service configured on your device; review that service's privacy notice and settings before use. Use manual entry and deny microphone access if you do not want to use voice recognition. The native 3.0 update has no voice-entry feature and requests no microphone permission.
Reminders, backups and files you choose
The native update schedules local notifications for reminders. Android may require notification permission; you can disable reminders in the app or system settings. Reminder text can appear on the lock screen depending on your device settings.
Android device backup or device transfer may include app data, depending on your Android version, account and backup settings. These copies are managed through Android and your backup provider, separately from the app's own recovery files.
When you choose an export, the native update writes JSON backups, CSV records or calendar files to a destination you select through Android. A selected cloud or file provider may receive the exported contents under its own practices. When you choose a backup to import, the app reads that selected file. Exports can contain your subscription and payment details; protect them and choose a trusted destination.
Retention and deletion
Local records remain on your device until you change or remove them using the available app or Android controls. In native 3.0, Settings → Clear all data removes local subscription records, the app's recovery copies and the earlier subscription database; app preferences can be reset separately with Reset settings. Deleting one subscription does not guarantee that older recovery or migration copies are removed. Android's app-storage controls can remove the app's local storage.
Exports and Android or cloud backups are separate copies. Delete those through the destination or backup service; removing local records does not remove those copies or a speech provider's server records. For speech-processing data, use the relevant provider's deletion controls. There is no Subscription Manager account to delete.
Security and third parties
The app uses Android's private app-storage boundary. The reviewed direct favicon and exchange-rate URLs use HTTPS. This does not promise additional encryption of local files, every speech provider's transport security, or absolute security. No advertising or analytics SDK or developer-operated subscription-record server was found in the reviewed native update. Google's favicon service, the earlier exchange-rate service, Android backup and your chosen speech or file providers process requests as described above; they are separate from the app's local record storage.
Audience, your choices and policy changes
Subscription Manager is intended for adults managing their recurring spending and is not directed to children. You can use manual entry, control notification and microphone permissions through Android, manage backup settings, and choose whether and where to export your data. Send privacy questions to vinsondevelopers@gmail.com; avoid including unnecessary financial details or passwords in email. We use correspondence you send to respond to your request and retain it as needed to handle the request and applicable obligations, following the established Policy Center website privacy practice.
This policy is dated 26 October 2026. Material changes will be reflected in an updated policy. Published dated revisions will remain accessible from the policy history.