← FolioSum

Privacy Policy

Last updated: July 11, 2026

FolioSum ("we", "us", the "App") is a portfolio tracker for crypto and traditional assets. This policy explains what data the App handles and how. We designed FolioSum to keep as much of your data as possible on your own device. We do not sell your personal data and we do not show ads.

1. Data stored on your device

Your portfolio setup — wallet addresses, exchange labels, asset entries, custom ordering, alerts, and any API keys you enter — is stored locally on your device in the App's private storage. This information is not uploaded to us and is not readable by us. If you uninstall the App, this local data is removed.

2. Account data (optional)

You only need an account if you choose to buy prepaid sync credit. Account sign-in is handled by Google Firebase Authentication. Depending on the method you pick, we receive and store:

We use this only to identify your account and attach your credit balance to it. If you never buy credit, you do not need to create an account and none of this is collected.

3. Credit balance and payment records

When you top up credit, we store on our servers (Google Firestore) a record containing your user ID, the amount, the payment status, and timestamps. This lets us apply and track your prepaid balance.

Payments are processed by NOWPayments, a third-party crypto payment provider. Your payment is made on NOWPayments' checkout page; we do not receive or store your wallet, card, or other payment credentials. Please review NOWPayments' own privacy policy for how they handle payment data.

4. Wallet balance lookups

If you use the optional server-assisted wallet sync (paid with credit), the App sends the wallet address you want to refresh to our server, which forwards it to DeBank (a third-party blockchain data provider) to retrieve public on-chain balances for that address. We use the address only to perform that lookup and we do not store the address on our servers afterwards. Public blockchain data returned for the address is sent back to your device. Review DeBank's privacy policy for how they process address queries.

If you supply your own DeBank API key instead, lookups can run directly and this server step is not used.

5. Crash and stability data

The App uses Google Firebase Crashlytics to collect crash reports so we can fix bugs. These reports include diagnostic information such as the type of crash, device model, operating-system version, and app version. They are not used to identify you personally.

6. How we use data

We do not use your data for advertising and we do not sell or rent it to third parties.

7. Sharing

We share data only with the service providers needed to run the App: Google Firebase (authentication, database, crash reporting), NOWPayments (payment processing), and DeBank (blockchain balance lookups). Each processes data under its own terms. We may also disclose information if required by law.

8. Retention

Account and credit-balance records are kept while your account exists. Payment records are retained as needed for accounting and legal purposes. You can ask us to delete your account and associated server-side data (see Contact); note that consumed-credit and payment records may be retained where required by law.

9. Your choices

10. Children

FolioSum is not directed to children under 13 (or the minimum age required in your country), and we do not knowingly collect their data.

11. Changes

We may update this policy. Material changes will be reflected by updating the "Last updated" date on this page.

12. Contact

Questions or data requests: support@foliosum.app