Security

Version 2026-10-27 · Effective 27 October 2026

This page describes the security measures that TexaCore uses and stands behind. It is deliberately limited to what is true today. TexaCore is the name of our product, which is provided by Next Revolution for Software Development, Dublin, Ireland ("we", "us"). It is part of the Data Processing Agreement (Annex 2) and belongs with the Privacy Policy.

1. Where your data lives

1.1 The cloud service is hosted on Supabase, running on Amazon Web Services in London, United Kingdom (region eu-west-2), and delivered through Cloudflare. The companies we rely on are listed on the Subprocessors page.

1.2 The desktop edition keeps your company data on your own computer. Securing that computer is your responsibility: use a login, keep the system updated and, where available, switch on disk encryption.

2. Protection of data

2.1 In transit. Connections to the cloud service are protected with TLS.

2.2 At rest. The data of the cloud service is encrypted at rest by our hosting provider's infrastructure.

2.3 Backup files. Backup and export files in the .tcdb format that are protected with a passphrase use AES-256 encryption. Protect the passphrase: we cannot recover it for you.

2.4 Backups and recovery. We keep backups so that the service can be restored after a failure. Copies of desktop company files that the program uploads for cloud backup are described in the Desktop Edition End-User Licence Agreement.

3. Access control

3.1 Isolation. Company data is isolated at the database level, so that one customer's data is not visible to another.

3.2 Permissions. Role- and action-based permissions decide who can see and do what. Document visibility can be limited to the owner, a team or the whole company.

3.3 Approvals. The service has approval workflows for documents and actions that need a second person.

4. Records and controls

4.1 Audit trail. Document activity logs show who performed an action and when.

4.2 Posted entries. Posted accounting entries are protected from ordinary edits. Controlled changes go through recorded workflows.

5. How we change the software

5.1 Changes that touch money, stock or security are independently reviewed before they are released. Security fixes receive the highest priority.

6. Reporting a problem

6.1 If you find a security problem, write to [email protected] with enough detail for us to reproduce it. Please do not access other people's data, do not disrupt the service, and give us reasonable time to fix the problem before you make it public. We acknowledge reports and keep you informed.

6.2 If a personal data breach affects you, we will tell you and the authorities as the law requires.

7. What we do not claim

7.1 We do not claim any independent security certification. Our hosting providers describe their own controls on their own websites. This page is not a promise of any outcome: no system is free of risk, and your own practices (strong passwords, removing leavers, protecting computers and backup passphrases) matter as much as ours.