Security and data control

Your data deserves clear answers.

Your own instance, traceable entries and controlled access. Find out how Accounting Scalable supports your work.

Protection suited to the risk

Prevent. Trace. Recover.

  1. Your own instance1

    Your address. Your database. Your bookkeeping.

  2. Controlled access2

    Passkeys for people, separate tokens for agents.

  3. Plan recovery5

    Consider backup scope and recovery together.

SECURITY, IN PRACTICE

The right measure for each risk.7

Discover how we address different risks.

OUR RESPONSE

Unauthorized access

Controlled access

Passkeys protect human sign-in. Give AI agents separate access that you deliberately authorize and can revoke.2

  • Passkeys
  • Agent tokens
Access in the App →

OUR RESPONSE

Eavesdropping on the connection

Transmit with encryption

HTTPS encrypts traffic between your browser and the application. Transport encryption protects data on this connection.12

  • HTTPS
  • Transport encryption

OUR RESPONSE

Access through other customers

Your own data area

Your own App instance and separate database form your personal bookkeeping area, separate from other customer instances. Keep several companies within your instance with separate books for accounting purposes.1

  • Your own instance
  • Separate database
Cloud and data areas →

OUR RESPONSE

Lost storage media

Protect stored data

If your instance operates with encrypted storage media, this protects stored data when a storage medium is lost. This protection complements sign-in and the encrypted connection.13

  • Disk encryption
Operating scope of your instance →

OUR RESPONSE

Unnoticed changes

Trace entries

The change log makes edits to entries traceable. Finalization protects finalized entries against silent changes.3

  • Change log
  • Finalize entries
Entry review and finalization →

OUR RESPONSE

Data loss and outages

Enable recovery

When separate backups with Object Lock are configured, they support backup-data protection and later recovery. Backups remain separate from live application data.5

  • Separate backups
  • Object Lock
Backup scope of your instance →

Your own instance · Encrypted connections · Traceable bookings

Your everyday work

Check for yourself. Keep working independently.

Review entries for accounting accuracy3

Check document links, account allocation and open questions and finalize reviewed entries. You handle bookkeeping and year-end accounts yourself; professional responsibility and approvals remain with you.

Handle bookkeeping and year-end accounts yourself →

Take your data with you6

Export DATEV files, reports and documents for your records or targeted collaboration. Your figures remain usable outside the App.

DATEV files and audit export →

Work transparently

Your bookkeeping.
With clear work steps.

Assign receipts, check bookings, trace changes and prepare annual accounts yourself: get to know the app’s workflows.

Standards and infrastructure

What lies behind the names.

App hosting
HTTPS certificates
Bank data connection
Electronic invoice format · FeRD

Cloud and data areas

Your bookkeeping is accessible online.

Cloud hosted: access your bookkeeping in the browser. You do not need to install or manage your own server.

Use your bookkeeping as a hosted application in Germany. Your personal instance has its own database and data area.8

Your instance and its backups

The app, database and receipts form your personal bookkeeping area. Backups complement this area for recovery. Contact us for details of your instance’s location and agreed backup scope.

Connect additional services deliberately

Bank data, payment services and your own AI assistants extend the workflow. These services have their own data paths and conditions.9

GoBD and GDPR

Traceable bookings. Deliberate data protection.10

Organize documents, entries and access traceably: Accounting Scalable supports your bookkeeping and data protection processes.

Traceable bookkeeping

The change log, document links, entry finalization and export support traceable bookkeeping. Complete documents, correct entries, retention and procedural documentation must also be ensured through organizational measures.

Change log and finalisation →

Controlled access and data areas

Your instance has its own database. Passkeys and separate agent access help you grant and revoke access deliberately.11

Privacy information →

Notes and requirements

  1. Separation applies to your own App instance and its database, not to dedicated hardware or complete infrastructure isolation. Several companies within a customer instance are separate for accounting purposes; this differs from separation between customers. This does not include group consolidation.

  2. Agent access applies across the instance. Individual roles per company are not included. Passkeys and client connections require a compatible browser or MCP environment.

  3. The change log and entry finalization serve different purposes: the log documents editing steps; finalization prevents certain changes to finalized entries. This does not mean that all data is immutable or that all customer processes automatically comply with GoBD. Professional review, timely finalization and responsibility remain with you.

  4. Location, encryption and operating scope of your instance depend on the agreed configuration. GoBD and GDPR describe requirements for the software and your organisation. Brands identify providers and formats, not endorsements by those providers.

  5. Separate backups and Object Lock require appropriate setup. Backup scope, retention, access rights and recovery depend on the agreed operating configuration. Object Lock protects backup objects according to the configured retention rules and permissions. This does not imply immediate recovery, guaranteed zero data loss or complete resilience to outages.

  6. DATEV export uses the EXTF file format. Contractual data return after termination is governed by the terms and conditions. Read the terms and conditions

  7. The mapping explains prevention, traceability and recovery. Several measures can reduce one risk; one measure can address several risks. This presentation is neither a security certificate nor a penetration test and does not guarantee complete security.

  8. The App, database, document storage and backups must be considered together. The agreed operating configuration determines storage locations, backup scope, retention and recovery for your instance. A dedicated URL or database does not mean dedicated hardware or complete infrastructure isolation.

  9. Additional services have their own data flows: Cloudflare in front of the sales website, email and support services, payment and bank providers and optional AI assistants connected by you. Website analytics through PostHog are enabled only with consent. App hosting does not automatically describe the processing location of all third-party services. Privacy information

  10. Alongside the change log, document links, finalization and export, proper bookkeeping requires complete records and documented workflows in your company. Data protection also includes the participants' responsibilities and agreements, permissions, retention and deletion, and a risk-based review of safeguards. Any required data protection impact assessment depends on the specific processing risk.

  11. Certifications under Article 42 GDPR are voluntary. The features and symbols explained here are not official certification evidence. EDPB on certifications

  12. HTTPS protects transport between browser and application. It is not end-to-end encryption against the operator and replaces neither access control nor stored-data protection.

  13. Protection against lost storage media requires encrypted data areas and suitable key management. The agreed operating scope determines which database, document and backup areas are covered. An encrypted HTTPS connection does not prove disk encryption. Cloud and data areas