Skip to Content
Docs

Security and data

How Tosven separates organisations and companies, records who did what, protects the books, backs up data and handles erasure.

All Tosven modules share one database, so they share one set of controls. This page describes those controls as they work in the pilot: isolation, permissions, the audit trail, the immutable ledger, erasure and backups.

Isolation between organisations and companies

Your organisation is a tenant. Inside it you have one or more companies, each a legal entity with its own books.

  • Enforced in the database. Every record that belongs to a company is fenced to that company in the database itself, not only in the screens. A request that does not state its organisation and companies gets no rows.
  • Rights are per company. A role in one company says nothing about another.
  • Identity is separate from membership. A person has one sign-in and a separate membership in each organisation. An external accountant with several clients has one membership per client.

Roles and permissions

Access is denied by default and granted by addition. There are six system roles: owner, admin, approver, member, viewer and external. A role is a bundle of individual permissions, granted per company.

  • Ceilings. Accountant and portal memberships have a hard ceiling that no role can exceed.
  • Checked live. Permissions are evaluated at every action, so a withdrawn right stops working at once.
  • Sensitive fields. Restricted and secret fields need their own permission, also for totals. See Builder.
  • Agents. An agent has a human manager and never has more access than that manager has at that moment. See Agents.
  • Sign-in. Passwords are stored only as hashes. Sessions expire, and repeated failed sign-ins are throttled.

On the way

Two-step sign-in with an authenticator app, a fresh second step before signing a decision, and the settings screens for members and roles are not yet released in the pilot.

More detail is in Companies and roles.

Audit trail

Tosven records who did what, and under which authority.

  • Grant history. Every grant and withdrawal of a permission is written to a log that can only be added to.
  • Decisions carry their reason. A privileged action records which grants allowed it.
  • Record changes. A change is logged with the changed fields and the actor, person or agent. Secret values appear only as a hash.
  • Agent decisions. Proposer, approver and executor are recorded separately. An approval is a signature over the exact content. See Decisions and approvals.
  • Figures. A question asked in Lens leaves a trail of who asked, when and which measure, without the result. The question text is deleted after 12 months, the trail after 24 months.

The immutable ledger

The books are protected by rules in the database, so no screen, import or agent can go around them.

  • Posted entries do not change. A correction is a reversal plus a new entry, and both stay visible.
  • Entries balance. Debits equal credits, or the entry is refused.
  • Numbered and chained. Vouchers are numbered without gaps and linked in a hash chain.
  • Period locks. A locked period refuses new postings, and every lock change is recorded with the person who made it.
  • Filed VAT is kept as filed. The filed return is stored with a checksum.

See Ledger and VAT and periods.

Erasure and personal data

Erasure is scoped to a person, and it has to coexist with bookkeeping law.

  • The books stay. Accounting records must be kept for the statutory period, so posted entries are not erased. Ledger lines hold only a reference to the party.
  • Personal data is kept apart. Names and contact details live in separate records that can be erased or pseudonymised.
  • Coverage. Erasure reaches customer records, chat messages and knowledge pages. An automated check fails when a new kind of record is added without an erasure rule.

A self-service screen for data subject requests and a full export of your organisation's data are on the way. On the way Consent and erasure for contacts are described in Customers.

Backups and where data lives

In the pilot, the database is backed up every night. Live in the pilot The same night, the backup is restored into a separate, disposable database and compared with the live one. The age of the last backup and the result of the last restore test are monitored, and an alarm is raised when either is overdue.

On the way

A copy of the backups kept at a separate location is planned and not yet in place for the pilot.

What is agreed in the service agreement

Tosven is provided by Fidanet Solution Oy, Espoo, Finland. Tosven does not claim a security certification.

Hosting location, sub-processors, encryption, backup retention, retention after termination and breach notification are agreed in the service agreement and its data processing terms. The current privacy information is at https://tosven.com/privacy/.

Next steps

On this page