DRAFT for legal review — not yet in force. Text in [square brackets] must be completed. Blue review notes are for the lawyer and must be removed before publishing. Version 2026-10-24-draft.
Privacy Policy
Last updated: [date]
Miplaka ("we", "us") helps you understand your money by reading the bank statements you upload. Your financial information is personal and sensitive, and we treat it that way. This policy explains what we collect, why, who can see it, where it is stored, how long we keep it and what your rights are.
Miplaka is operated from Bonaire (Caribbean Netherlands) with servers in the Netherlands, backups in France, and customers on Bonaire, Curaçao and Aruba. Please confirm which laws apply: the Wet bescherming persoonsgegevens BES, the EU GDPR (servers in the EU and possibly customers in the EU), and the Curaçao and Aruba personal-data ordinances. This draft is written to the GDPR standard as the strictest baseline.
1. Who is responsible for your data
Tjitro Holding B.V., trading as Miplaka, Kaya Dawari 18, Bonaire (Caribbean Netherlands), registered with the Chamber of Commerce and Industry Bonaire under number 15314, is the controller of your personal data. Contact us about privacy at info@miplaka.com.
2. What we collect
| Data | Where it comes from | Why |
|---|---|---|
| Name, email address, preferred currency and language | You, when you sign up | To run your account and contact you about it |
| Password (stored only as a one-way Argon2id hash), two-factor authentication secret and recovery codes (stored only as hashes) | You | To keep your account secure |
| If you use Face ID or fingerprint sign-in (a passkey): a public key, a random key ID chosen by your device, the device name shown when you added it (encrypted), and when it was added and last used. Your face or fingerprint is checked by your own device and never reaches us. We don't ask for, or keep, your device's make or model. | Your device, when you add a passkey | To let you sign in securely without typing a code |
| Transactions from your bank statements: date, description, amount, account type (current or savings), how it was paid (card or bank transfer) and the category we assign | Statements you upload | To show your income, spending, loans and savings insights |
| The name and period of each statement you upload | Statements you upload | So you can see and delete what you uploaded |
| Savings buckets, deposits and loan details you enter, and how you filed savings transfers | You | To show your plans and loan overviews |
| Account activity: sign-ins, IP address, device/browser type | Automatically | Security, and so you can see activity on your account |
| A random code that recognises a browser you signed in on before (stored only as a code derived with your own key) | Automatically, when you sign in | To warn you by email when your account is used on a new device |
| Your email preferences (for example whether you want the monthly reminder) | You | To send only the emails you want |
| Feedback you send us, with your device/browser type | You (optional) | To improve Miplaka |
| If you join the waitlist: your email address, where you live, if you chose it (an island or country), your language, and when you joined, confirmed and were invited. Your address is stored encrypted and only added after you confirm it with the link we email you | You, on our front page | To send you an invitation to the beta when there's a place for you |
| If you lose your phone and your recovery codes and ask us to remove two-step sign-in or delete your account: when you asked, the country it was asked from, and short safety notes (for example "new country"). Not linked to what's in your account | You, on the sign-in screen | To check the request is really yours before we carry it out |
| Emails you send us, for example to ask for a beta invitation: your name, email address and what you write | You | To answer you and, if you ask, send you an invitation |
| Anonymous visit statistics for our public pages: daily totals per page, the site or tagged link you came from, your country and whether you use a phone or computer. Not linked to you or your account | Automatically, when you visit without being signed in | To see how people find Miplaka and improve the website |
| Subscription status and payments: the amount, the date, how you paid and your Miplaka payment reference. We never see or store your card details. If you pay by bank transfer, your name and account number appear on our own business bank statement; Miplaka records only the payment itself, and deletes the statement file as soon as the payments have been matched | You, our payment providers and our bank | To provide the paid service, and to keep the financial records the law requires |
We do not store your bank statement files. A PDF or CSV you upload is read in memory and discarded immediately; only the transactions extracted from it are kept. We do not connect to your bank and cannot move money.
Sensitive information in your transactions
Transaction descriptions can indirectly reveal sensitive information, for example donations to a religious organisation or payments to a pharmacy or doctor. We do not look for or analyse this information; it is only used to categorise your own transactions and show them to you. By uploading statements you give your explicit consent to this processing. You can withdraw your consent at any time by deleting the statement or your account.
Transaction data may contain special categories of personal data (GDPR Art. 9: religion, health, trade-union membership, political donations). Please confirm that explicit consent at sign-up/upload is an adequate basis and whether a separate, specific consent step is needed at the first upload.
3. Legal bases
- Contract: to provide the service you signed up for (account, statement processing, insights, loans, savings) and to send the emails the service needs, such as confirming your email address, resetting your password and security warnings.
- Explicit consent: for any sensitive information that may appear in your transactions (see above).
- Consent: for the waitlist. You can withdraw it at any time with the link in our emails, or by emailing us, and we delete your address straight away.
- Legitimate interests: to count visits to our public pages anonymously (see section 9), to keep Miplaka and your account secure (activity logs, new-device warnings, preventing abuse, backups), to remind you once a month to upload your latest statement (you can turn this off at any time), and to improve Miplaka using feedback you choose to send.
- Legal obligation: to keep financial records of payments where the law requires it.
4. How we protect your data
- Two-factor authentication is required for every account.
- Your financial data is encrypted with a key unique to your account (AES-256-GCM). Your email address is stored encrypted as well. These keys are themselves encrypted with a master key that is kept separately from the database.
- All connections use HTTPS. You are signed out automatically after 30 minutes of inactivity, and always after 12 hours.
- When your account is used on a device it hasn't been used on before, we email you, so you can act quickly if it wasn't you.
- Only Miplaka's founder, Jendric Janga, can access the production systems, using two-factor authentication. We do not look at your financial data unless you ask us to in writing (for example to fix a problem), and we log any such access.
- Error reports we receive about the service contain the page and the place in our code where something went wrong, never your financial data.
- To block attackers who try many passwords, your IP address is held briefly in our server's memory to count attempts. It is never written to disk, and our server logs don't record visitors' IP addresses.
- [The service is tested by an independent security firm before public launch.]
5. Emails we send you
- Account and security emails, such as confirming your email address, resetting your password, a password change, a sign-in on a new device, and a Face ID or fingerprint sign-in being added or removed. You can't turn these off, because they protect your account.
- Subscription emails, once payments are switched on: your free trial is ending, your paid period is ending, we've received your payment, your access has ended. They never contain amounts.
- Service announcements about Miplaka itself, for example that the beta is ending or that this policy or our terms change. Not marketing: we send them only when something affects your account.
- Waitlist emails, only if you joined the waitlist: one email to confirm your address, and one with your invitation when it's your turn. Both have a link to remove yourself.
- A monthly reminder to upload your latest bank statement, if you haven't yet. You can turn it off with the link in the email or under Account in Miplaka.
Our emails never contain your amounts, transactions or other financial information. We don't send marketing emails or newsletters.
6. Who we share data with
We never sell your data and never use it for advertising. We use a small number of service providers ("processors") who may only use your data to provide their service to us:
| Provider | Purpose | Where your data is |
|---|---|---|
| Fly.io, Inc. | Servers and encrypted storage that run Miplaka | The Netherlands (Amsterdam). Fly.io is a US company. |
| Scaleway SAS | Off-site backup copy of the database (in which your financial data and email address are already encrypted) | France (Paris) |
| Scaleway SAS (Transactional Email) | Sending our emails; receives your email address and the email text. Emails are sent exactly as we write them: no tracking of whether or when you open them, and no rewritten links | France (Paris) |
| Google (Google Workspace) | Our mailbox: receives emails you send to us, and our own notifications about your payments (your email address and the amount) | [EU / global] |
| Our bank ([bank name]) | Receives your bank transfer: your name, your account number, the amount and your Miplaka payment reference | [Bonaire] |
| Sentoo | Local bank payments, only once they're switched on; receives a random account reference and the payment amount | Curaçao |
| Lemon Squeezy | Card payments, only once they're switched on. Lemon Squeezy is the seller of record: it receives your name, email address and card details directly from you and handles them itself; we receive only the subscription status and payment amounts | USA |
Your transactions, savings plans and loans are never shared with any of these providers, except with the companies that store our servers and backups. Scaleway only receives encrypted copies and doesn't have the key. Fly.io runs our servers: like any hosting company it could technically access data while Miplaka runs, and our data processing agreement with Fly.io forbids it from doing so.
Please check the transfer mechanisms and data-processing agreements for each provider: Fly.io (US company, data in Amsterdam; possible US government access), Google Workspace and Sentoo (Curaçao), e.g. EU–US Data Privacy Framework or Standard Contractual Clauses. Banks receiving transfers act as independent controllers. Scaleway's email delivery records are kept while the service is in use, also after an account is deleted: check whether that is acceptable or whether we must ask Scaleway to delete them. Payments are not yet switched on during the beta. From 29 September to 22 October 2026 our previous email provider (Brevo) added a hidden open-tracking pixel to our emails, contrary to this policy; it was found and stopped on 22 October (recorded as an incident). Please advise whether customers and waitlist sign-ups should be told. Lemon Squeezy is a merchant of record (likely an independent controller) and a US company: please confirm how to describe it.
7. How long we keep data
- Account, transactions, plans, loans, email preferences and activity: for as long as your account exists.
- Recognised devices: forgotten after 400 days without a sign-in on that device.
- Passkeys: until you remove them under Account, or delete your account.
- Anonymous visit statistics (daily totals, not about you): 25 months.
- Waitlist: an address that isn't confirmed within 7 days is deleted. Once you're invited (or create an account), your address is deleted within 30 days; in any case after at most 12 months on the list. Removing yourself deletes it straight away.
- Requests to remove two-step sign-in or delete your account: 90 days after they're decided or cancelled.
- Emails you send us without becoming a customer, such as a request to join the beta: at most 12 months.
- Emails you send us as a customer, and our own notifications about your payments: [24 months].
- When you delete your account, all of this is permanently deleted from our live systems immediately, and from backups within 30 days.
- Email links expire: confirming your email after 24 hours, resetting your password after 30 minutes. Invitation codes expire after 7 days if unused.
- Feedback you send: until it has been handled, and at most [12 months].
- Payment records: [7 years], where tax law requires us to keep them.
- Emails we send you: our email provider deletes the text as soon as the email has been delivered. It keeps a delivery record (the address, the subject, the date and whether it arrived) for as long as we use its service.
8. Your rights
You can at any time:
- See and download all your data: Account → "Download my data".
- Correct your data: change your name, currency and transaction categories in the app, or contact us.
- Delete your data: delete individual statements, or your whole account under Account → "Delete my account".
- Object to or restrict processing, or withdraw consent, for example by turning off the monthly reminder.
- Complain to a data protection authority: [authority name and website].
For anything you can't do in the app, email info@miplaka.com. We answer within one month.
Please confirm the competent supervisory authority/authorities (e.g. the Commissie toezicht bescherming persoonsgegevens BES, the Dutch Autoriteit Persoonsgegevens, and the Curaçao/Aruba authorities).
9. Cookies
Miplaka uses two strictly necessary cookies and nothing else:
- a sign-in cookie that keeps you signed in. It is deleted when you sign out, and expires after at most 12 hours;
- a device cookie with a random code, so we can recognise a browser you signed in on before and warn you about sign-ins on new devices. It expires after 400 days.
We use no analytics, advertising or tracking cookies, and no third-party scripts, so we don't ask for cookie consent.
Anonymous visit statistics. When you visit our public pages without being signed in, we add one to daily totals: which page, the website or tagged link you came from, your country and your type of device. On the front page we also count, the same way, how many people send the waitlist form (not who). A small script on the page sends this once the page has been shown for a moment, so bots aren't counted. Your IP address is used only for a moment to look up the country, on our own server, and is never stored. To estimate how many different people visited, we use a code made from your IP address and browser together with a random value that changes every day and is never saved, so we can't recognise you on another day. Nothing is stored on your device. Totals are kept for 25 months. Country lookup uses data from DB-IP (CC BY 4.0).
Please confirm the device-recognition cookie counts as strictly necessary (security of the service the user requested) under the applicable cookie rules (e.g. Dutch Telecommunicatiewet art. 11.7a / ePrivacy).
10. Automated processing
Miplaka automatically categorises your transactions, recognises transfers to and from your savings, and generates insights. This has no legal or similarly significant effect on you; you can change any category or choice, and nothing is decided about you on this basis.
11. Data breaches
If a security incident puts your data at risk, we will tell you and the competent authority as the law requires, without undue delay.
12. Children
Miplaka is for people aged 18 and over.
13. Changes
If we change this policy in a way that matters, we'll tell you by email or in the app before the change takes effect.