Privacy
Privacy policy
Effective November 18, 2026. This policy explains what FolioFlux collects, why, and how to remove it.
Who we are
FolioFlux, operated by Andrii Furmanets, runs folioflux.com ("we"). Contact us about privacy at hello@folioflux.com.
Your account
When you sign up or sign in with Google or GitHub, we store the following.
| Data | Why |
|---|---|
| Name, email address and profile picture from Google or GitHub, and whether the provider verified the email | To create your account, show it to you and contact you about your account. |
| Your Google or GitHub account ID for each sign-in method, and when it was linked and last used | To sign you in and list your sign-in methods. |
| For each passkey you add: its credential ID and public key, a signature counter, the name you give it (at first the browser and system it was made on), whether it is synced, when it was added, last used and last presented with a valid signature, and, if you signed in with a recovery code, when that paused it. | To sign you in with it and list your passkeys. The private key stays on your device or in the app that keeps your passkeys. |
| Recovery codes, as keyed hashes only, and when each was used | To let you back in once if you lose every passkey. |
| The time of your latest account recovery and counts of sessions ended, passkeys paused and pending invitations cancelled; the time a session last verified a passkey | To show a recovery notice on your devices until you dismiss it, and require a recent passkey check before replacing recovery codes. The notice contains no IP address or device fingerprint. |
| For each session: a hash of its token, the sign-in method, a device label such as "Chrome on macOS", when it was last used and when it expires | To keep you signed in for up to 30 days and let you sign out on any device. |
| For each sign-in attempt: Google, GitHub, passkey or recovery code, sign-up or sign-in, how it ended, campaign tags, the page you started on, the site that sent you and the button you pressed | To find where sign-in goes wrong and which links bring people. It holds no email, name or IP address. |
| If you ask for sign-in help: the email address you give, the problem and what you write | To answer you and fix the problem. |
Your workspace data
Your workspace holds accounts and opening balances, manual and imported entries, categories, rules, transfers, budgets, month closes, findings and their source rows, comments, member roles and invitations, and cash-forecast items you add or confirm (expected invoices, known bills, tax set-aside lines, and recurring series you dismiss). For a tax set-aside line we store the jurisdiction you pick from a fixed list, the date, the amount and the set-aside rate you set. A dismissed series is kept as a hash of the merchant name, the name as shown, its currency and whether it is money in or out, so it stays dismissed if it is detected again. We use these records to show your finances, support collaboration, explain figures with receipts, and project cash over the coming weeks. Set-aside findings retain their recorded calculation so later settings changes do not rewrite their explanation.
Imports
Imports. If you import a bank or card CSV file, we read it on our servers and don't keep the file itself. When we show you a preview, we store the file's name, a fingerprint of the file so we can recognise it if it's uploaded again, the column settings used, and every row in it, both as written in the file and as the date, amount, description, counterparty and balance we read from it. Rows you save become entries in your workspace. Entries that came from an import can't be deleted one by one; you can exclude them or undo the whole import. Discarding a preview deletes it and its stored rows. Undoing a saved import removes its entries, but we keep the import, its file name and all its stored rows. A preview nobody saves or discards within 7 days is deleted with its stored rows in a daily cleanup. We also record when someone previews, discards, saves or undoes an import, and who did it; the records of previews and discards include the file's name and how many rows it had, but not the rows themselves. We delete these import records after 12 months in a daily cleanup. Our server logs can also include the file's name, and we keep them for up to 7 days.
Who in your workspace sees it. Everyone in a workspace, whatever their role, can see its imports, their file names and their stored rows. Owners and admins can also see the workspace's activity log, which includes the import records above.
Review records. When you or someone in your workspace categorises an entry, archives or merges a category, deletes an entry added by hand, or adds, edits, dismisses, restores or deletes a cash-forecast item, we record who did it and when. A merge also keeps a list of the entries, rules and budgets it moved, so it can be undone. A deleted entry is removed, but our activity record keeps its date, amount, currency, account and category (not its description) so the change stays traceable. For a cash-forecast change, the activity record keeps the kind, amount, currency, date, cadence and jurisdiction, not the item's label; for a deleted item, only its kind and whether it was active. If someone leaves the workspace, their name stays on the records they made; if they delete their account, the records lose the link to them.
How long we keep it. We keep saved imports, their stored rows, entries, cash-forecast items and the records above for as long as the workspace exists, and delete them 7 days after the workspace is deleted. Some things go sooner: previews nobody saved or discarded, after 7 days; the import records described above, after 12 months; and a cash-forecast item an owner or admin deletes, at once.
Deleting your data. You can delete a saved import from its page: its entries, the rows read from its file and the import go at once, and reports change to match. Only a record that it was deleted stays, without the file's name. An owner can delete a workspace from its settings: everyone in it loses access at once, an owner can restore it for 7 days, and then we delete it with everything in it. When you delete your account from your account page, we also delete the workspaces no one else uses. A workspace you share with others stays with them, including what you imported or recorded there, but it's no longer linked to you. Deleting an account or a workspace needs a sign-in, or a passkey confirmation, from the last 10 minutes. You can also email hello@folioflux.com and we'll delete it within a month.
The earlier waitlist
Before accounts opened, people joined a waitlist with their email. On November 18, 2026 we removed the remaining waitlist emails and then deleted every waitlist record. Deleted records may remain in our hosting provider's backups until those backups expire. New sign-ups never create waitlist entries.
Why we may use it
We keep your account to provide the service you signed up for. We keep sign-in attempts, help requests and logs because of our legitimate interest in keeping sign-in working and secure.
How long we keep it
Your account, its sign-in methods, passkeys, recovery codes and sessions stay until you delete your account or ask us to. A passkey you remove is deleted at once. A session ends when you sign out or after 30 days.
When you sign in with a recovery code, your other passkeys are paused. They can't sign you in until you keep them, which takes a fresh sign-in with a recovery code or a passkey. A paused passkey you don't keep within 30 days can't be kept any more; we delete it in the daily cleanup or when you next sign in or open your account.
We keep sign-in attempts and help requests to run and secure sign-in. We delete sign-in attempts and sign-in help requests older than 13 months in a daily cleanup.
How to delete your data
You can delete your account yourself from your account page, after signing in again or confirming a passkey. We delete it at once, with its sign-in methods, passkeys, recovery codes and sessions, so you're signed out everywhere, and straight after, every workspace only you use, with everything in it. If you're the only owner of a workspace others use, add another owner or delete that workspace first. Sign-in attempts linked to your account lose that link and keep no personal data. If you prefer, email hello@folioflux.com from the address on your account and we'll delete it within one month. Signing out ends a session and keeps your account. Deleted data may remain in our hosting provider's backups until those backups expire.
Server logs
When you visit the site or sign in, our hosting providers record request logs, including your IP address, so we can keep the service running and secure. We keep these logs for at most 7 days. To limit abuse, our rate limits keep a keyed hash of your IP address for up to one day. We rely on our legitimate interest in keeping the service secure.
Accounts from the earlier version
Accounts from the earlier version of FolioFlux, and the records added to them, were deleted on October 27, 2026.
Who processes data for us
- Vercel: Hosts the website.
- Railway: Hosts the API and the database.
- Namecheap: Runs our domain and forwards email sent to hello@folioflux.com and security@folioflux.com.
- Google Gmail: Holds the mailbox those addresses forward to.
Our providers may process data in the United States and the European Union.
Your rights
Under GDPR and UK GDPR you may access, correct, delete, restrict or export your data, object to its use, withdraw consent, and complain to your data protection authority.
Under CCPA/CPRA California residents may know, delete and correct their personal information, and opt out of its sale or sharing.
We do not sell your personal information, and we do not use it for advertising.
To use any of these rights, email hello@folioflux.com.
Children
FolioFlux is not directed at children under 13, and we do not knowingly collect their data.
Changes and version history
- November 18, 2026: the earlier waitlist is deleted. We removed its remaining emails and then every waitlist record, so this policy no longer lists waitlist data, its consent basis or how to leave it.
- November 17, 2026: the workspace data section now includes cash-forecast items you add or confirm, including tax set-aside lines and dismissed recurring series, and the activity records of changes to them. Deleting your account is described as something you can do yourself or ask us to do, and we say that deleted data may remain in our hosting provider’s backups until they expire. The terms, dated the same day, describe deleting your account yourself.
- November 15, 2026: you can now delete your account, a workspace or a saved import yourself; a deleted workspace can be restored for 7 days. Previews nobody saves or discards are deleted with their stored rows after 7 days, and the records of who previewed, discarded, saved or undid an import after 12 months, both in a daily cleanup.
- November 13, 2026: documented the data, controls, session cookie and access logs for planned board sharing, which remains switched off. Corrected authentication retention to reflect the daily cleanup observed in production.
- November 12, 2026: the imports section now states exactly what an import stores, who in a workspace sees it and how long we keep it. We commit to deleting an account and its data within one month of a request, and to deleting remaining waitlist emails by 31 March 2027. The 13-month target for sign-in attempts and help requests is withdrawn, because no automatic deletion runs yet.
- November 11, 2026: added workspace imports, financial and review records, actual deletion controls and retention limits; documented recovery notices, verified passkey attempts, recent passkey verification and the temporary recovery email cookie.
- November 10, 2026: this policy now states that a recovery-code sign-in pauses your other passkeys, that keeping one takes a fresh sign-in with a recovery code or a passkey, and that a paused passkey you don't keep within 30 days can't be kept any more and is deleted the next time you sign in or open your account. It also lists when a recovery paused a passkey.
- October 29, 2026: accounts with Google or GitHub sign-in replace the waitlist form, and passkeys with recovery codes can be added to them. This policy lists what accounts, passkeys, recovery codes, sign-in attempts and help requests store, the sign-in cookies and how to delete your account.
- October 27, 2026: accounts from the earlier version of FolioFlux and their records were deleted, and this policy no longer describes them.
- October 27, 2026: the site no longer uses Google Analytics or analytics cookies.
- October 27, 2026: the waitlist consent text names everything we store, and this policy states what removal keeps and lists every provider that processes data for us.
- October 22, 2026: rewritten for the relaunch as an AI finance workspace, covering the waitlist.
- Earlier versions covered the previous product and are kept in our records.