Colly Portfolio Privacy Policy
Last updated: October 21, 2026
Colly Portfolio is provided by Colly Developer to help you manage subscription records locally.
1. Local Data and Security
Local account information, subscription records, payment and activity history, and settings are stored on your device. The app does not automatically upload this information. Sensitive text, including subscription account names, passwords and notes, is stored encrypted. Calculation fields such as amounts, currencies and dates are stored in plain text. Your local account password unlocks and encrypts data and is not sent to the developer.
2. Online Features You Initiate
After you successfully unlock or initialize a sync folder, the app securely remembers its password on this device using your operating system’s current-user encryption. It is bound to the local account and sync folder/channel and can be forgotten from the sync setup screen. The saved password is not sent to the developer or authorization service and is not included in account backups, exports, migration packages or sync files. Forgetting it does not change the password of existing encrypted files. To use a new password, finish syncing all devices that need the current data, then set up a new sync folder.
When you update exchange rates, the app contacts your selected service and may try alternatives after a failed request, including Frankfurter, the European Central Bank, the Bank of China or a custom service. Requests may contain currency codes, and providers receive network information such as your IP address. They do not contain subscription names, amounts or account passwords. External websites have their own privacy policies.
You initiate backups, exports, migrations and synchronization. Standard exports are readable without decryption and exclude subscription account passwords. Encrypted migration packages contain complete local account data, including encrypted subscription account passwords. Sync contents are encrypted; sync filenames include the device name, and migration filenames include the account name. Your cloud storage client transfers files in the chosen folder according to its settings and its provider's privacy policy. Colly Portfolio's authorization service does not receive your subscription database, sync file contents or their decryption password.
3. Purchase Identity, Pro and Device Authorization
When you choose purchase sign-in or purchase restoration, you can use a Google account or a Microsoft account. Sign-in happens on Google's or Microsoft's page, and you enter your password only there. Colly Portfolio's identity service uses only the account identifier in the sign-in proof and converts it one-way into an opaque purchase identity identifier. It does not read or store your email address, name, profile photo or password.
So you do not have to sign in repeatedly, the identity service obtains a renewal token from Google or Microsoft, stores it encrypted with keys protected by Azure Key Vault, and uses it only to confirm with that provider that your sign-in is still valid. Each device's sign-in session lasts at most 30 days, after which you sign in again; signing out or deleting the purchase identity clears the corresponding renewal tokens. Your device keeps only a device-bound renewal credential, encrypted in the system's secure storage (such as Windows Data Protection or Android Keystore), for renewing with Colly Portfolio's identity service. It does not keep Google or Microsoft tokens and is not included in app backups, exports, migration packages or sync files. Signing out clears the local sign-in cache and revokes that device's sign-in session.
Payments are processed by Google Play or the Microsoft Store; we do not receive your payment card or other payment details. For Google Play purchases, the app gives Google Play an anonymous identifier derived from your purchase identity so the purchase can be linked to it. The authorization service verifies and acknowledges purchases through the Google Play Developer API, reads the product, purchase state and refund state, and receives purchase and refund notifications sent by Google Play. Orders are recorded under hashed identifiers. The server reaches Google Play through federated identity without long-lived keys.
To verify purchases, restore Pro, manage five active devices and prevent duplicate authorization, Colly Portfolio's authorization service processes the purchase identity identifier, Store product and order identifiers, purchase or refund status, authorization revisions, device public keys and their fingerprints, system device names, device activation status, and short-lived verification records. A system device name may contain a personal name you chose. It is used only to identify the device, updated after device verification, and cleared from the live ledger when you delete the purchase identity. It is not included in tokens or operational logs. Store query credentials (Microsoft Store query credentials and Google Play purchase tokens) enable purchase checks with the stores. They are stored encrypted, with wrapping keys protected by Azure Key Vault, and are usable only by the authorization service. The services are hosted on Microsoft Azure; authorization data is currently stored in a US region. Microsoft and Google process hosting, store and sign-in data under their respective service terms.
After Pro activation, local record management works offline. Sync is available in Free and Pro; starting a sync does not check the purchase or device authorization online and sends no data to Colly Portfolio's identity or authorization services. Unavailable Pro verification is not treated as a refund: verified local rights and records are kept. Sign-in and purchases will open in releases that pass integration checks.
4. Retention, Deletion and Your Control
You can view, edit and export records, or delete a local account. Uninstalling leaves local data in place by default. Signing out, unlinking a device or deleting a local account does not delete your cloud purchase identity. You manage exports, backups, migration packages, sync folders and cloud copies yourself.
While the authorization service operates, it retains the minimum purchase identity, order, event and device authorization records needed to restore purchases and prevent duplicate claims or reversal of revocations. Store query credentials remain until replaced by an update or deleted with the purchase identity. Expired credentials stop being used for new purchase checks, but their encrypted records may remain. Purchase identity deletion requires ownership verification: in the app, signed in with your purchase identity, open Pro, choose "Delete purchase identity" and confirm. Deletion applies to Pro on all your devices. It deactivates device authorizations and clears device names, revokes sign-in sessions and their encrypted renewal tokens, and removes short-lived verification records and encrypted store query credentials. The minimal duplicate-prevention and revocation records remain and are not used for advertising or behavioral analysis. Deleting the purchase identity does not trigger a refund and does not delete your Google or Microsoft account or your store purchase history.
Sanitized operational logs are retained for 30 days. Automatic authorization database backups are retained for seven days; long-term backup retention is disabled. Data from before deletion may remain in backups until they expire. A restore must reapply confirmed deletions and revocations; an old backup state cannot justify renewed authorization.
5. Website, Support and Contact
Colly Portfolio and this help site have no advertising or behavioral tracking features. The help site does not set analytics cookies. Azure hosting may process IP addresses, request times and other operational or security information. If you contact support, we use the email and issue description you provide to respond. Do not send passwords, personal databases, sync files or complete Store credentials. For Microsoft's data processing, see the Microsoft Privacy Statement; for Google's, see the Google Privacy Policy. This policy will be updated when features or data handling change.
Contact the developer or ask a privacy question: collydeveloper@outlook.com