Privacy

What Finora stores, and why.

Finora does not connect to banks and does not move money, so there is no bank credential to store and nothing to transfer. This page describes the software as it is actually built, not an intention.

Do not enter real financial credentials

Never enter a banking password, a full payment card number, a security code, or an identity document anywhere in Finora. The product does not ask for them, has no field for them, and has no use for them. Treat everything you type here as example information.

What is stored

Every item below corresponds to a table in this application’s database. Nothing else about you is stored.

Your name, email address and a hash of your password
To create your account and let you sign in. The `users` table.
A keyed hash of your session token, when it was created, when it was last used, and the browser string your device sent
To keep you signed in and to show you your active sessions so you can end one. The `sessions` table.
The account labels, opening balances, notes, transactions, dates, amounts and categories you add, plus the sample dataset if you load it
They are the records the product exists to show you. Every one is marked with where it came from. The `accounts` and `transactions` tables.
Review suggestions, the rule each one matched, the numbers that made it match, and whether you have marked it reviewed
So a suggestion can explain itself, and so one you have dealt with does not come back. The `alerts` table.
Sign-ins, failed sign-in attempts, sign-outs, session revocations and password changes, each with a time and a salted hash of your IP address
So you can see activity on your own account on the security screen. The `security_events` table.
A message you send through the contact form: your name, address, topic, message and a salted hash of your IP address
So the site administrator can read and answer it. The `support_tickets` table.
A record of administrative actions, such as a role change or an account suspension
So those actions are accountable and reviewable. The `audit_events` table. It holds no money figures.
A counter per rate-limit key, which is a salted hash rather than an address
To limit repeated sign-in and form attempts. The `rate_limits` table.

Cookies

One cookie, and only when you are signed in.

finora_session
A random token that identifies your session. It is HttpOnly, so page scripts cannot read it; SameSite=Lax, so another site cannot make your browser send it; and marked Secure, so it is only ever sent over HTTPS. It expires after 7 days, or after 12 hours of inactivity.

There is no consent banner because there is nothing to consent to: no advertising cookie, no tracking pixel, and no third-party script is loaded on any page.

Analytics

None. No analytics provider is configured in this build, so no page-view, session-recording or heat-mapping service is loaded, and nothing is sent to a third party when you use the site.

Email

No mail provider is configured in this build, so Finora sends no email at all. Password reset by email and email-address confirmation are unavailable as a result, and both say so where they appear rather than failing quietly.

Where it runs

This instance runs against a PostgreSQL database reached over the network. The hosting and database providers are not named here because naming an unverified provider would be a claim this page cannot support.

How long it is kept

No automatic deletion schedule is implemented. Your records stay until you remove them or request that your account be deleted. Expired and revoked sessions remain as rows until the account is deleted, which is what lets the security screen show you a history.

This is stated plainly rather than as a retention period, because a period that nothing enforces would be a false promise.

Getting your records out, and getting them deleted

  • Export. The profile screen gives you every account and transaction you hold as a CSV file, generated at the moment you ask, with the source of each row included.
  • Deletion. The profile screen also lets you request deletion. You confirm by typing a phrase and entering your password. This removes your accounts, transactions and review suggestions immediately, marks your account deleted, and ends every session. The row that records the request remains in the administrative log, without your financial records.

Who can see your financial records

You, and nobody else. No administrative role in this product - including the owner - can read another person’s transactions, balances or account labels. There is no screen for it and no database query that does it. Support staff can find a person by email address and see whether their account works and how many records they hold; they cannot see what those records say.

Questions

Use the contact form. It stores your message so the administrator can read it.

No law, regulation, certification or standard is named on this page, because none has been verified as applying to this application. Nothing here is legal advice or a legal undertaking.

Privacy | Finora