# Data security in Financist

> In Financist, each company’s data is isolated in its own workspace, access is managed through roles with 45 separate permissions, and administrative actions are recorded in an audit log. The service is hosted on servers in the EU (Germany). This page describes only what can be verified and honestly lists what the service does not do yet.

Financial data is sensitive, so this page contains only what can be verified in the product, plus an honest list of what the service does not do yet.

## Data isolation between workspaces

Each company works in its own **workspace**. All tables holding business data are tied to a workspace, and every request to the server is filtered by the workspace of the current session. A user who is not a member of a workspace cannot see or change its data.

Isolation between workspaces is covered by automated tests, including for reports, the team, the AI assistant and the Claude connection. One user can be a member of several workspaces and switch between them.

## Roles and access rights

Access is defined by **45 separate permissions** (scopes): view and manage rights are separate for accounts, reports, documents, budgets, the team, backups, the AI assistant and more.

- there are four system roles: Owner, Administrator, Responsible employee and Observer, as well as custom roles with any set of permissions;
- an employee can see only the accounts assigned to them;
- a user cannot grant permissions they do not hold, so an Administrator cannot create or assign the Owner role;
- the Owner role and membership cannot be changed or removed, and nobody can change their own role or remove themselves;
- permissions are checked on the server for every request, not only in the interface.

## How sign-in and API access are protected

| Mechanism | How it works |
| --- | --- |
| Passwords | Stored only as a hash (bcrypt), never in plain text |
| Session | The session token is kept in an httpOnly cookie and has a limited lifetime |
| Personal API tokens | Stored as a hash, shown only once when created, act with the owner’s current permissions and are removed together with the owner’s access to the workspace |
| Employee invitations | A single-use link valid for 7 days; only a hash of the token is stored |
| Sign-in attempts | Request limits on sign-in, sign-up and demo creation per IP address |
| Response headers | Protective headers, including a ban on framing, content-type restrictions and HSTS in the production environment |

## Audit log

Financist keeps an audit log: who changed what, and when. It records changes to roles, employees and invitations, access tokens, workspace settings, automation rules, budgets, integrations, backup export and import, as well as AI assistant actions and every tool call made through the Claude connection (without the contents of records).

The log is available to users with the right to manage settings. It records administrative actions and access, but it is not a complete history of every change to individual transactions.

## Backups and data export

The workspace owner (and users with the relevant permission) can download a **full copy of the workspace’s business data** as a JSON file and restore it. Restoring fully replaces the workspace’s business data, so it requires separate confirmation and shows how many records will be loaded.

The copy does not include user accounts, roles, tokens, invitations, the audit log or integration settings. Reports, budgets and transaction lists export to CSV; in report and budget exports, values beginning with formula characters are protected from being executed in spreadsheet editors.

The server deployment procedure also provides for regular database backups.

## Hosting and channel protection

The service is hosted on servers in the EU: in a data centre in Germany (hosting provider Hetzner). The app is accessed over HTTPS, and the certificate is issued automatically. The database is not exposed to the internet: only the web server is reachable from the network.

## The Claude connection and the AI assistant

The **Claude connection (MCP)** works through OAuth 2.1 with mandatory PKCE. On the consent screen you choose the workspace and can enable read-only mode, in which write tools are unavailable altogether. Access tokens last 1 hour and refresh tokens 30 days, and both are stored only as hashes. A connection can be revoked in settings. A connection’s effective permissions never exceed the user’s current role.

The **AI assistant** works within the user’s permissions. Changes to the books are made only after a preview and confirmation, and background tasks write nothing, they only suggest changes. Conversations with the assistant are visible only to their owner.

If a language model is enabled in the service, the request and the data fragments needed for the answer are processed by the model provider. See the [Privacy Policy](https://findir.rozum.one/en/privacy/) for more.

## Data minimisation

An account needs only an email address, a password and, optionally, a name. You enter financial data into the service yourself: we do not pull it from banks or receive it from third parties. This marketing website uses no cookies and no analytics trackers. Demo workspaces are created with temporary data and are cleaned up automatically.

## What the service does not do yet

- There is no two-factor authentication.
- There is no sign-in with Google or Microsoft (SSO).
- There is no self-service password recovery by an email link.
- Employee invitations are not sent by email: the link is shown to the administrator, who passes it on.
- The audit log does not record every change to individual transactions.
- We hold no security certifications and do not cite the results of an independent audit.

## Questions about security?

**Questions about security?** Write to us and we will answer questions about storage, access or the Claude connection. [Contact us](https://findir.rozum.one/en/contact/)

## Frequently asked questions

### Where is Financist data stored?

Data is stored on servers in the EU, in a data centre in Germany. Each workspace is isolated from the others, and the database is closed to outside access: only the web server is exposed to the network, over HTTPS.

### Who on my team can see my financial data?

Only members of your workspace, and only within their assigned role. Permissions are set separately for viewing and managing, and an employee sees only the accounts assigned to them. Every change to access is recorded in the audit log.

### Is it safe to connect Claude?

The connection works through OAuth, needs your consent, can be limited to read-only mode and can be revoked. Its permissions never exceed those of your role, and every tool call is logged. Statement imports always go through a preview.

### Can I take my data with me?

Yes. A full copy of workspace data can be exported as JSON, and reports and transaction lists as CSV. Export is available to the workspace owner and to users with the relevant permission.

### Does the service hold security certifications?

No, and we do not claim any. Everything on this page describes real mechanisms in the product. If you need extra assurances for your company, write to us and we will tell you honestly what exists and what does not yet.

---
Source: https://findir.rozum.one/en/security/