This policy covers Flowney: the iOS app, the web client at app.flowney.app, its Telegram bots and this website. It says what we collect, why, who else handles it, how long we keep it and what you can ask of us.
01Who we are
Flowney is run by Bohdan Bunchuk, a private individual (фізична особа) in Ukraine, who is the controller of your personal data — in the words of Ukrainian law, its owner (володілець). “We” in this policy means the operator.
Write to support@flowney.app about anything in this policy.
02What we collect
Your account
- Your email address and password, which are how you sign in. The password is stored only as a hash. We prove the address with a six-digit code sent to it when you create an account, reset your password or your passcode, or change the address.
- When you ask for a code by email, the network the request came from, so that one network cannot ask for letters without end. That is your IP address as Cloudflare passes it on to us, or with IPv6 only its first half, the part a provider gives a whole household or phone.
- The name you give.
- If you sign in with Apple or Google: the identifier the provider gives your account, the email address it confirms — with Apple, possibly a private relay address that forwards to your own — and your name, which we take only if your account has none yet. For Apple we also keep, encrypted, one token for the app and one for the web, which the web client and the page where you connect an assistant share, so that we can withdraw Flowney’s access at Apple for each of them when you delete your account.
- Your four-digit passcode, which locks the app, stored only as a hash, and a record of each wrong attempt.
- If you link Telegram: your Telegram user ID, username and first name.
- When you create an account, a message reaches the operator in Telegram with your name, your email address and how you signed up: with a password, Apple, Google or Telegram.
- The devices you are signed in on: the kind of device as iOS reports it, such as “iPhone”, or for a browser its name and system, such as “Chrome, macOS”, and when each session was started and last used. A browser’s session is listed with your devices in the app, Settings → Security, and can be ended there like any other.
- If you allow notifications in the app: the address Apple’s push service gives the app on that phone, called a device token, whether the app is a test build, and the app’s language, so that a notification reaches that phone in its language; which kinds of notification you switched off; and when the morning’s and the evening’s last went out.
- If you set a limit on a category: which of its two thresholds, 80 per cent of the limit and the limit itself, we have told you of in the current period, in the app and in Telegram, so that neither is told twice.
Your ledger
Everything you keep in Flowney: accounts and balances; operations with their amounts, currencies, dates, categories, descriptions and notes; payees, budgets, debts, loans, instalment plans, recurring payments and the rules that sort your operations.
Receipts you attach to operations: the photo or PDF itself, its type and size, who attached it and when. In a shared ledger, everyone who can see an operation can see its receipts.
If you bring your history over from another app, you send us the file that app exported. Our server reads it, with no language model involved. We do not keep the file itself: we keep the operations, accounts and categories read from it, and what you chose to bring over, until the import is written into your ledger. From then on what you brought is part of your ledger.
In a shared ledger we also keep who belongs to it, what each member may see, whose money each account is and who wrote each entry.
If you set up the Apple Pay automation in Shortcuts, every payment you tap sends us its amount and currency, the merchant, the account you chose for that card and the time.
If you record an expense by Siri, Siri hears the amount and the category or account you name, and the app gives iOS the names of your accounts and expense categories so that Siri can recognise them. Siri says back the amount, the account and the category it recorded, never a balance.
A bank you connect
To connect monobank you give us your personal monobank token. With it we read your accounts and jars, including the masked card number and IBAN, your statement for up to 92 days back, and every new operation the bank sends from then on. An operation from the bank can include the other party’s name, IBAN and EDRPOU code, the sender’s comment and the merchant’s category code. The bank sends us each new operation on every card and jar the token reaches, including those you have not added to Flowney, and we keep each of these messages as the bank sent it.
The personal token only lets us read. Nobody can make a payment or move money with it.
Other people in your ledger
Your ledger can hold data about other people: the name of someone you lent money to, the email address of someone you invite to a shared ledger, the other party of a bank transfer. Add it only if you are entitled to. We use it only to keep your ledger and, for an invitation, to let that person join. We never write to the person you invite: they see the invitation when they sign in with that address.
Problem reports
A problem report sent from the app carries the text you wrote, the app’s version and build, the iOS version, the device model and the app’s language. We keep it with your account, and a copy reaches the operator in Telegram together with your name, email address and Telegram username, so that we can answer.
Messages to support
When you write to our support bot in Telegram, @flowney_support_bot, our server copies each message — text, a photo, a file, a voice message — into the operator’s Telegram chat, under a line with your Telegram name, username, user ID and language, and copies the operator’s answers back to you. Our server keeps only which message stands for which: your Telegram user ID and the numbers of the messages, never what they say. The messages themselves stay in Telegram, in your chat with the bot and in the operator’s.
An assistant you connect
If you connect an AI assistant to Flowney — Claude, ChatGPT, Cursor or another app that speaks the Model Context Protocol — you sign in on our page with a code sent to your address, or with Apple or Google as in the web client (below), then with your passcode, and choose one of your ledgers for it. We then keep a session for the assistant, as we do for your devices: which assistant, which ledger, when it was connected and last used. The assistant can read that ledger and change it — record, edit and delete operations — but not your settings, your bank connection, your password or any other ledger.
While you sign in there, the page keeps two cookies in your browser, for twenty minutes at most: __Host-flowney-connect ties the sign-in to that browser, and __Host-flowney-connect-provider, while you are on Apple’s or Google’s page, holds the one-time values that finish the sign-in. Both are strictly necessary, and the page uses no other.
The web client
If you use Flowney in a browser, at app.flowney.app, our server sets one cookie in that browser, __Host-flowney-refresh, under its own address, api.flowney.app. It holds the token that keeps you signed in. The web client cannot work without it, so it is strictly necessary, and it is the only cookie the web client uses. Scripts on the page cannot read it, and the browser sends it to our server alone. It lasts 90 days from the last time your session was renewed, and is deleted when you sign out.
The web client also remembers in your browser the language and the theme you chose, which ledger was open and the account you last recorded in, so that it opens as you left it. These are kept only in that browser.
Sign in with Apple and Sign in with Google in the web client send your browser to Apple’s or Google’s own sign-in page, which brings it back to us with a one-time code. Our server exchanges the code with Apple or Google for the identifier described above and signs you into the account that has it. The web client makes no new account. While you are on Apple’s or Google’s page, the tab keeps the one-time values that finish the sign-in, and drops them when you are back.
What we do not collect
- No analytics, advertising or tracking in the app or the web client, and no advertising identifier. The web client loads no script, font or image from another company and talks to our server alone. The one exception is a button for Apple or Google, which sends the browser to that company’s sign-in page when you press it.
- No crash-reporting service.
- No location, contacts or microphone. The camera and your photos are used only when you attach a receipt, and then only the pictures you take or pick, or the files you choose, are sent. The app saves every picture anew as a JPEG before sending it, without its location or anything else the camera recorded about it; a PDF is sent as it is.
- Nothing from Face ID: iOS checks your face on the device and never tells us anything about it.
- No IP addresses stored by our server, except the network a code by email was asked from (above). Cloudflare, which carries the traffic to it, sees them all (section 4).
- No cookies and no analytics on this website. The web client’s one cookie, described above, belongs to our server’s address, not to this website.
03Why we use it
- To provide Flowney: your account, your ledger, bank sync, shared ledgers, the bots and the notifications. This is the performance of our contract with you (GDPR, Art. 6(1)(b)).
- To keep accounts safe: the codes that prove your address, the passcode, limits on attempts and on the letters one network may ask for, the list of your sessions. This is our legitimate interest in security (Art. 6(1)(f)).
- To answer you when you write or send a problem report: the performance of our contract with you (Art. 6(1)(b)) and our legitimate interest in running the service (Art. 6(1)(f)).
- To comply with the law when it requires us to keep or disclose something (Art. 6(1)(c)).
Under the Law of Ukraine “On Personal Data Protection” these are the grounds of its Article 11: the conclusion and performance of a contract with you, our legitimate interest, and a duty the law places on us.
We do not make decisions about you based solely on automated processing, profiling included, that have legal or similarly significant effects on you. We do not sell your data, show you ads, build a credit profile of you or hand your ledger to anyone for their own purposes. Operations are sorted into categories by rules on our server. Flowney itself sends none of your data to an AI service. If you connect an assistant yourself, it receives what it asks for from the ledger you chose, because you asked it to (section 4).
04Who else handles it
Four companies handle data on our behalf, as our processors. Each gets only what its job needs, may use it only to do that job for us, and is bound by terms that protect it at least as this policy does:
- Cloudflare, Inc. (USA) carries all traffic that reaches our server from the internet — from the app, the web client, Shortcuts and the bank’s notices of new operations — and hosts this website and the web client. The encryption of that traffic ends on Cloudflare’s servers, which pass it on to ours over a separate encrypted connection, so Cloudflare could read what passes through it, your IP address included. It also stores the receipts you attach, in Cloudflare R2 in the European Union: the storage is closed to everyone but our server, which hands a receipt out only after the same check that decides who may see its operation.
- Resend (Plus Five Five, Inc., USA) sends our letters: the code that proves your address, and notices about your account, such as the one your old address gets when you change it. It gets your email address and the letter, sends it from Ireland and keeps it in the USA for 30 days.
- DigitalOcean, LLC (USA) provides the virtual server Flowney runs on, in its data centre in Frankfurt, Germany. Everything our server stores is on DigitalOcean’s disks, your account and ledger included, and DigitalOcean keeps a copy of the whole disk for us each day, for seven days, in the same data centre. It does not encrypt those disks or copies, so it could read them.
- Grafana Labs (Raintank, Inc., USA) keeps a copy of our server logs (section 7) for 14 days, on Amazon Web Services’ servers in Germany, so that we can search them and learn of errors. The logs carry identifiers of accounts, ledgers and operations, and no names, email addresses, Telegram IDs, amounts or descriptions.
- Backblaze, Inc. (a US company, storing in the EU) keeps our backups. They are encrypted on our server before they are sent, so Backblaze cannot read them.
An AI assistant you connect is an independent controller of what it receives: Anthropic for Claude, OpenAI for ChatGPT, Anysphere for Cursor, or whoever makes the assistant you chose. It gets what it asks Flowney for, from the ledger you chose, at your instruction, and keeps it under its own privacy policy. You can revoke it at any time in the app, Settings → Security, where it is listed among your sessions as «MCP · » and its name.
Telegram (Telegram Messenger Inc.) is an independent controller: it decides for itself what it does with data, under its own privacy policy. If you link Telegram, it carries the bot’s messages, which include amounts, payees and balances. Problem reports and the notice of a new account reach us through Telegram too, and so does everything you write to our support bot.
Apple’s push notification service (Apple Inc., USA) delivers the notifications our server sends to the app, once you allow them on your phone. For each one it gets the device token and the notification’s text: its title; the name of the ledger, if you are in more than one; and for the upcoming charges, the name, amount and day of each charge and, for an account that will run short, its name and how much it lacks; for a deposit, its name and the day its term ends; and for a category’s limit, the category’s name, what was spent in it and the limit. It keeps a notification only until the phone receives it, and drops one the phone has not received within 12 hours. Apple’s own privacy policy applies to it.
We run our server ourselves, on DigitalOcean’s machine.
monobank, Apple and Google are independent controllers as well, and their own privacy policies apply to what you do with them directly: the token you issue in monobank, signing in with Apple or Google, the App Store, Shortcuts and Siri.
As the operator, we can see account details — name, contacts, plan and the features open to the person, number of accounts and operations — on an internal admin page. We have access to the database and to the storage of receipts to keep the service running. We use that access only for support, maintenance and legal obligations.
We disclose data to authorities only when Ukrainian law obliges us to, and only what it obliges us to.
05Data outside Ukraine and the EU
Cloudflare, Resend, DigitalOcean, Grafana Labs, Telegram, Apple and Google work outside Ukraine and the European Union; our server and its daily copies stay at DigitalOcean in Germany, its logs at Grafana Labs in Germany, the receipts Cloudflare stores for us stay in the EU, and Resend sends our letters from Ireland but keeps them in the USA. For Cloudflare, Resend, DigitalOcean and Grafana Labs we rely on their certification under the EU–US Data Privacy Framework and on their data processing addenda, which include the European Commission’s standard contractual clauses. For Telegram, Apple and Google the transfer is necessary for the performance of our contract with you: without it we cannot deliver the bot’s messages once you have linked Telegram, sign you in with the provider you chose, or deliver the notifications you allowed on your phone (GDPR, Art. 49(1)(b); Article 29 of the Law of Ukraine “On Personal Data Protection”). An assistant you connect may work outside Ukraine and the EU as well; it receives your data because you connected it and asked it to.
06How we protect it
- Traffic between the app or your browser and Cloudflare, and between Cloudflare and our server, is encrypted.
- The bank token and Apple’s token are encrypted on our server (AES-256-GCM). The bank token is never shown in full again, not even to you: the app shows only its last four characters.
- Passwords and passcodes are stored as argon2id hashes, and the codes sent to your address only as keyed hashes, valid for five minutes. A session uses a token that expires after 15 minutes and is renewed by a second one, valid for 90 days; the app keeps both in the iOS Keychain, on that device only. In a browser, the web client keeps the first only in the open page’s memory, and the second in the cookie described in section 2.
- The app is locked with your passcode, and you can let Face ID open it instead.
- Backups are encrypted on our server before they go to Backblaze.
- Receipts are kept in private storage that hands nothing out by itself: only our server reads from it. Cloudflare encrypts them on disk (AES-256).
- The admin tools are reachable only from our private network.
Your ledger itself is not hidden from us: the server has to read it to show it to you, sort it and sync it with your bank. No system is perfectly secure. If a breach affects your data, we will tell you and the authorities as the law requires.
07How long we keep it
- While your account exists, we keep what it holds.
- When you delete your account (Settings → Delete account), it is erased from the live database at once: the ledger you own, the bank token, what the bank sent, the Telegram link, your sessions and sign-in records, and your problem reports. The files of your receipts are removed from storage right after. If you signed in with Apple, we first ask Apple to withdraw Flowney’s access; if Apple does not answer, the account is deleted all the same, and you can remove Flowney in your Apple ID settings. Then we send a letter to the account’s email address saying it was deleted; Resend keeps it for 30 days, like our other letters (section 4).
- A receipt is kept as long as its operation. When you take it off, delete the operation or delete your account, its record leaves the database at once and its file leaves storage right after. If removing a file fails, or attaching one breaks off half-way, the file can stay in storage for a short while, with nothing pointing to it and nobody able to open it; a daily clean-up deletes such files automatically within three days. If it finds unusually many of them at once, it deletes none and waits for the operator to look first.
- A file from another app is not kept: the server reads it and forgets it at once. The rows read from it are deleted as soon as the import is written into your ledger or writing it fails. Our server writes it in the minutes after you finish. If you do not finish, the rows are deleted after a day. If a backup was taken meanwhile, the rows stay in it until it is replaced.
- Backups keep a copy for up to six months, until they are replaced by newer ones. Receipt files are not in the backups; they hold only the record that a receipt existed, with its type and size.
- What reaches the operator in Telegram — messages to support, copies of problem reports, and the notices that an account was created or deleted, with its name and contacts — stays in the operator’s chat until we delete it; write to us and we will. The record of which support message stands for which is deleted automatically after 90 days, and at once when you delete an account your Telegram is linked to.
- An invitation to a shared ledger keeps the email address it was made for until it is accepted or cancelled, or the ledger is deleted.
- Session records, which say when a session was started and each time it was renewed, are deleted 91 days after each entry.
- An assistant’s session lasts until you revoke it, change your password, sign out of your other sessions or delete your account, or until it has gone 90 days unused.
- A device token goes with the session that registered it. It is deleted at once when you switch notifications off in the app; when that phone’s session ends — you sign out on it, end it in Settings → Security, change or reset your password, or leave it 90 days unused; when you delete your account; and when Apple tells us the token no longer works. Which kinds you switched off, when the last notification went, and which thresholds of a limit you were told of, are kept while your account exists.
- Technical records such as the codes sent to your address, sign-in attempts, and the record of recent requests the app keeps so that an operation is never written twice, are deleted automatically within a month. The network a code by email was asked from is deleted with its record of the attempt, after seven days.
- Server logs record each request to our server: which operation it asked for, whether it succeeded, how long it took and the internal number of the ledger it concerned; and the errors and warnings on the way. They hold identifiers of accounts, ledgers and operations, ours and the bank’s, and no names, email addresses, Telegram IDs, amounts or descriptions. On our server they are erased each time it is updated, and the oldest lines go sooner once a part of the server has written 50 MB of them; the copy Grafana Labs keeps (section 4) is deleted after 14 days. They are not in our backups, but DigitalOcean’s daily copies of the disk keep them for up to seven days more.
- Out of our reach: messages the bot has already sent stay in your Telegram chat. What an assistant you connected has already read stays with its company, under its own policy. What you added to someone else’s shared ledger stays in that ledger without your name on it: your entries and receipts, and any account that was yours there, which passes to the ledger’s owner, closed, with its history and the masked card number and IBAN the bank gave for it.
We do not delete an account for being inactive.
08Your rights
You can:
- get a copy of your data, in a form you can take elsewhere: the app exports your operations to CSV at any time; for anything else, write to us;
- correct it: almost all of it can be edited in the app;
- delete it: in the app, or by writing to us. If you own a shared ledger that others are still in, remove them first;
- withdraw access: disconnect the bank in the app at any time and revoke the token in monobank itself; revoke a connected assistant in Settings → Security; to unlink Telegram, write to us;
- object to processing based on our legitimate interests, or ask us to restrict it;
- complain to a supervisory authority: in Ukraine, the Ukrainian Parliament Commissioner for Human Rights; in the EU, the authority of the country where you live or work, or where you believe the law was broken.
We answer within one month. We may ask you to confirm a request from the email address of the account.
09Children
Flowney is not meant for anyone under 16. If we learn that an account belongs to a child under 16, we delete it.
10Changes to this policy
The date at the top is the date of this version. If a change affects what we collect or who receives it, we will let you know before it takes effect.
11Contact
Bohdan Bunchuk, Ukraine — support@flowney.app.