Security
Journl holds other businesses' financial records. This page says how we look after them, and how to tell us if you think something is wrong.
Reporting a security concern
If you believe you have found a vulnerability in Journl, or that an account or data has been accessed without permission, email security@journl.co.uk. It is read by the people who build the software, not a ticket queue.
- We will acknowledge your report within two working days and tell you what we are doing about it.
- Tell us what you found and how to reproduce it. Please do not access, change or download data that is not yours while demonstrating it, and do not test against other customers' books.
- We will not take action against anyone who reports a genuine concern in good faith and gives us reasonable time to fix it.
If there is a breach
If we discover that personal or customer data has been exposed, lost, or accessed without authority, we follow a written procedure:
- Contain it. Revoke the affected credentials or sessions, close the route in, and preserve the logs.
- Establish what happened: which data, which customers, since when.
- Tell the businesses affected within 48 hours of becoming aware, as our data processing addendum promises, with what we know, what we have done, and what they should do. Anyone else affected, such as a user whose own sign-in details were exposed, is told without undue delay.
- Tell the Information Commissioner's Office within 72 hours where personal data is involved, as UK GDPR requires.
- Tell HM Revenue & Customs immediately where the breach concerns data handled through Making Tax Digital, as HMRC's terms of use require, by logging a ticket on the HMRC Developer Hub with a named contact and telephone number.
- Fix the cause, and write down what we learned.
How your data is protected
- Where it lives. Amazon Web Services, London region (eu-west-2). The database, backups and file storage are in the United Kingdom.
- In transit. Every connection to Journl is encrypted (TLS 1.2 or later). Browsers are told to use HTTPS only (HSTS).
- At rest. The database and backups are encrypted. HMRC access and refresh tokens, and the secrets behind two-factor codes, are additionally encrypted with keys kept outside the database, so the database alone never holds a token or a secret that works.
- Separation. Each business's data is isolated at the database level: a query for one set of books cannot read another's.
- Sign-in. Passwords are stored only as one-way hashes. Two-factor authentication with an authenticator app is required for every user, and the time it was used is reported to HMRC with each filing, as their fraud-prevention rules require. Repeated attempts at a password or code from one address are limited, then refused.
- Who can see what. Access to a set of books is by named role (owner, bookkeeper, accountant, read-only). Journl's own staff can see a customer's books only to provide support that customer has asked for, under confidentiality, and that access is logged.
- The record. Posted entries cannot be edited or deleted; a correction is a further entry. The audit trail shows who did what and when.
- Testing. Changes are checked with Journl's automated tests before release, including checks that one business can never see another's data. Journl is scanned for known weaknesses with recognised security tools (OWASP ZAP, Nuclei and Trivy) before release, and anything found is fixed and scanned again. The fraud-prevention data sent to HMRC is checked with HMRC's own validation service in its test environment.
What we ask of you
- Use a strong, unique password. Two-factor sign-in is required on every account; keep your recovery codes somewhere safe.
- Give people access to your books by role, and remove it when they leave.
- Tell us straight away if you think your account has been used without your permission.