Your data

The connection to your books is read access only, enforced at three points that do not depend on each other. The access we request from your accounting system is read-only. Those credentials are checked as read-only before any sync runs. And a guard in the transport layer blocks a write request from ever leaving Clarity. A write would have to defeat all three to reach your books.

Data flows one way: out of your accounting system and into Clarity's own environment. Clarity does not create, edit, or delete anything in your books. Your accounting system stays the single record of truth, untouched.

For a client deployment, the database, the dashboard, and the AI connection all run in the same EU region (Frankfurt). Your accounting data is held there.

Each client deployment has its own database and its own web server. Your data is not pooled with another client's and there is no shared table that mixes them. The separation is at the infrastructure level, not a filter applied inside a shared store.

Access to your accounting system is granted through that system's own authorisation flow, and you can withdraw it there whenever you choose. If you revoke, Clarity stops syncing. The dashboard keeps working on the data it already holds; nothing new comes in until you reconnect.

The database is standard PostgreSQL and the dashboard is built on open tools. If the engagement ends you can take a full export of your data in a standard format and keep it, or take ownership of the hosting account. There is no proprietary format holding your data hostage.