Confidential until publication. Accountable after.

That depends on the hosting model. In the shared SaaS environment, the platform runs in AWS data centres in Frankfurt, Germany — the data stays inside the EU. A dedicated environment runs isolated from other customers. With on-premise, the data never leaves the organisation’s own network.

Sign-in runs through single sign-on against the organisation’s own identity provider: accounts are created and revoked in its own directory, not in a separate user list at a vendor. Inside the platform, access is configurable per project, per output channel and per section.

Yes, both ways. In transit: TLS 1.2 as the minimum, with TLS 1.3 where the client supports it; an unencrypted connection is redirected to HTTPS. At rest: AES-256 — the volumes holding the application and the reporting data are encrypted through AWS KMS, and object storage is encrypted by default. The full description, including key management, is in the security documentation shared under NDA.

Every change to the report: what was changed, by whom and when, down to section level. In addition, data-lineage reports connect every figure in the XBRL output to its source — recorded for the audit, not just for the security review.

Two, both named in the data processing agreement: Amazon Web Services (hosting, Frankfurt — inside the EU) and Microsoft Office 365. No new subprocessor is engaged without the client’s prior written consent, so the list does not change without the client knowing.

The client chooses. At the end of the agreement all personal data is either deleted, or returned in a generally readable and properly documented file format. Until that choice is made the data stays put — Taxxor deletes nothing without an explicit instruction. The only exception is data that law requires be kept. That is the standard from the data processing agreement; other arrangements are possible by agreement.

Yes — continuously in-house, and additionally by an independent third party. Automated scanning with OWASP ZAP runs inside the development process: passive scans at set points and periodically an active scan with simulated attacks. On top of that, Taxxor DM is assessed by an independent, qualified party, including penetration testing. Those reports are available on request to clients and prospects. A customer-initiated penetration test is welcome too: scheduled by agreement and run in two rounds, so findings can be fixed in between. Findings are scored with CVSS; severity sets the priority, with critical findings taking precedence over other work. Reports from outside fall under the responsible disclosure policy.