Skip to the content.

Privacy Policy — VaultWise

Effective date: 2026-05-16 App: VaultWise (iOS · App Store) Operator: Su Rong (individual developer, Singapore) Contact: wowstorm99@gmail.com

This document explains what data VaultWise collects, how we use it, who else sees it, and the choices you have. Plain language — short, specific. If anything reads as fuzzy, email us; we’ll fix it.

1. What we are

VaultWise is a personal finance tracker. You import bank statements you already have, the app categorises them, and you see your spending trends. We are not a financial institution. We do not move money. We do not connect to bank APIs. We do not give investment advice.

2. What we collect

2.1 You give us this data

Data Where it lives Why we need it
Phone number (E.164) Our backend (identity_links table, Neon Postgres, EU/US region) Authenticating you. We never display it; we hash it for analytics.
Display name (optional, you set it) Backend (users table) What the app shows on your profile
Bank statements (PDFs) Parsed in memory; the PDF itself is never stored on our servers To extract transactions you can categorise. The decrypted PDF lives only for the duration of one parse request.
Bank statement passwords Your device’s iOS Keychain only — never our servers, never logged So you don’t re-enter them every time you import
Transactions (date, amount, merchant, category) Backend (transactions table) The product itself
Categorisation rules you create Backend (categorisation_rules table) So your rules survive a reinstall

2.2 What we automatically collect

Data Why Retention
Access/refresh tokens (issued by us) Keep you signed in 30 days for refresh; rotated on every use
Source IP — hashed (HMAC-SHA256), not stored plaintext Refresh-token forensics if a token is stolen Lives with the refresh-token row
User-Agent string Same as above Same
Crash logs (no PII) Fix bugs 90 days

2.3 What we don’t collect

3. Who else sees your data

We use these third parties because we couldn’t build them ourselves. They each see only the slice they need.

Provider What they see Why
Twilio (Verify API) Your phone number, the OTP code we asked them to send Sending the one-time login code
Google Gemini (LLM) The text of your statement PDF (account number redacted), the categorisation prompt AI extraction & categorisation of transactions
Neon (Postgres host) Everything in §2.1 + §2.2 above Database hosting
Apple (iOS Keychain) Your bank statement passwords Local secure storage on your device

Google Gemini’s data handling for paid API customers: input is not used for model training. Twilio retains OTP records for 30 days for audit; we cannot disable this on their side.

4. How we secure it

5. Your rights

You can, at any time:

We respect GDPR (if you’re in the EU/EEA) and PDPA (Singapore). Singapore residents can contact the Personal Data Protection Commission if they’re unhappy with our response: pdpc.gov.sg.

6. Children

VaultWise is not directed at children under 13. We don’t knowingly collect data from anyone under 13. If you believe a child has used the app, email us and we’ll delete the account.

7. Changes

If we materially change how we handle your data, we will notify you in the app at least 14 days before the change takes effect. The “Effective date” at the top of this page always reflects the current version.

8. Contact