Privacy Policy
Effective 18 November 2026
Dompet Oyen is a personal finance tracker. This page explains what data we keep about you, why, for how long, and what your rights are. We try to keep it plain.
1. Who we are
The controller of your personal data is Dompet Oyen, which is run by an individual (not a company). Privacy questions: [email protected].
2. Data we keep
- Account: name, email address, password (stored only as an argon2id hash that cannot be read back), time zone, language, base currency, and your weekly summary choice.
- Security: your authenticator secret (encrypted), hashed recovery codes, and a list of signed-in devices: IP address, browser type and last-used time.
- Google (only if you choose Sign in with Google): your Google account ID, email address and profile name, which we receive from Google only to create and recognise your account. We do not request access to your Gmail, Drive, contacts, calendar or any other Google data.
- Your finance records: account and category names, transactions (date, amount, currency, description, note), budgets, and the change history of transactions (before and after copies so you can undo). If you use the debt tracker: names and notes you enter about other people (for example a friend who owes you or whom you owe), plus installment plans and due dates. Those people are not told and are not users; enter only what you need, and delete it when you no longer do. If you use recurring items and category rules: the schedules you create (amount, description, dates) and the text you write to match descriptions, for example a shop or merchant name.
- Import files: every cell of an uploaded CSV or XLSX is kept temporarily for review and rollback. The original file is not stored.
- AI features (only if you use them): how many calls you made per day, without the message, the photo or the answer. If you add your own API key: it is stored encrypted with its last 4 characters, your provider and chosen models, and is never exported or written to logs. The time you agreed to send data to AI providers is kept too.
- Technical logs: request ID, user ID, route, status and duration. We do not log request bodies, amounts, descriptions, emails, tokens or passwords.
- Cookies: three session cookies, see section 8.
3. What we use it for
- Running the service: signing in, storing and calculating your finances, converting currencies.
- Security: preventing account abuse, limiting login attempts, and emailing you when your data is exported or your account changes.
- Service emails: email verification, password reset and security notices.
- A weekly email summary with your spending and income totals. You can turn it off in Settings or with the unsubscribe link in each email. It is off by default and is only sent after you turn it on yourself; the basis for processing is your consent, which you can withdraw at any time.
- We do not sell your data, show ads, or currently use third-party analytics.
4. Who receives data
We use these providers to run Dompet Oyen:
- DigitalOcean: application hosting, database and backup storage, in a Singapore data center.
- Amazon Web Services (Amazon SES, Singapore region): sends service emails. It receives the recipient address and message content.
- Xendit and Midtrans (payment providers): process the one-time payment for your account. A provider receives your email and the invoice amount, plus the payment details you enter directly on its page; we do not store your card or bank account numbers.
- Cloudflare: serves traffic to the site (DNS and proxy), so traffic, including IP addresses and request content, passes through its systems.
- AI providers (only if you use the AI features): the provider you choose when you add your own API key, or the provider named in the app when you agree to send data. A provider receives the message text or receipt photo you send, plus the names of your wallets and categories and today's date; not your balances, transaction history, email or name. The photo is scaled down and re-encoded without location data, processed in memory, and never stored by us. The AI answer is only a draft on your screen until you save it yourself. We ask providers not to keep this data [each provider's retention terms: to be confirmed]. You are asked to agree before first use; if you use your own API key, your data goes to the provider you chose under your own account terms there.
- Google: only if you sign in with Google. The Google account data we receive (ID, email, name) is used only to sign you in and manage your account. We do not sell it, share it with third parties, use it for advertising, or let people read it except where the law requires. Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. You can revoke access at any time in your Google account settings, and delete your account in Settings > Delete account.
- Frankfurter (reference rates): we send only public currency codes, no personal data.
- We may disclose data when the law requires it.
5. How long we keep it
- While your account is active, your records are kept until you delete them.
- If you delete your account, every row tied to you is permanently removed by our system, usually within minutes and at most 24 hours.
- The change history (audit log) is deleted together with your account. We do not delete inactive accounts automatically.
- Database backups are made every day and kept for at most 30 days, then expire. If a backup is restored, account deletions are replayed before the service reopens, so deleted accounts do not come back.
- The deletion record holds only a random ID with no name or email, and is kept as long as backups that might contain it exist.
- Daily AI usage counts are removed after 90 days. Your own API key is removed when you remove it or delete your account.
- Sign-in sessions last 7 days. One-time tokens (verification, password reset) expire in 5 minutes to 24 hours. Idempotency keys are removed after 48 hours. Uncommitted import uploads are removed after 7 days.
6. Security
- Connections use HTTPS.
- Each user can read only their own rows; this is enforced in the database, not just in the app.
- Passwords are hashed with argon2id. Two-step verification is available. Sensitive actions (export, delete account, change password) ask you to confirm again.
- Your finance records are not encrypted inside the app because we need to sum them in the database. Our team's access to production data is restricted and logged.
- No system is perfectly secure. If personal data is breached, we will tell you and the authorities as the rules require: within 3 x 24 hours of the breach being confirmed.
7. Your rights
You have the right to access, correct, export and delete your data, and to withdraw consent. Most of it you can do yourself:
- Access and portability: Settings > Data > download JSON, CSV or XLSX. JSON is the complete, restorable copy.
- Correction: edit accounts, categories and transactions in the app; edit your profile in Settings.
- Deletion: Settings > Delete account.
- Withdrawing consent or objecting to processing: turn off the weekly summary in Settings, or contact us.
- Other requests or complaints: [email protected]. We reply within 2 working days and complete your request within 7 days.
8. Cookies
- access_token and refresh_token (HttpOnly): keep you signed in.
- csrf_token: protects against forged requests.
- locale: remembers your language.
- No advertising or tracking cookies. The app can be installed as a PWA; our service worker does not store your financial data.
9. Changes
If this policy changes in a meaningful way we will tell you by email or in the app before it takes effect, and update the date above.