Last updated: 26 September 2026
Keeping the data in EcoTorque safe is one of the most important things we do. This page says plainly how the Service is run and protected, including the parts that are small-business rather than data-centre. The live facts further down are read from the Service itself each time this page is opened, so they show what is true today, not what was true when this was written.
Where the Service runs
- The Service runs on one computer at our workshop in Arlesey, England. It is not directly on the internet: no ports are open to it. All traffic arrives through Cloudflare Tunnel, an encrypted connection the computer makes outwards to Cloudflare.
- While the Service restarts (for example after an update) a holding page answers instead, and updates are made out of working hours.
- One computer is a single point of failure. We plan for it: nightly verified backups kept off the premises, a written step-by-step recovery on a new computer (target: working again within one working day), and a monthly test that a backup really restores.
Signing in and access
- Everyone has their own named account; there are no shared logins.
- Two-step sign-in with passkeys (Face ID, fingerprint, phone PIN or Windows Hello), with one-time recovery codes and an authenticator app as a fallback. Admins are asked to set it up at every sign-in.
- Lockout after 5 wrong passwords in 15 minutes (and for an internet address that keeps failing), with every lock logged; an admin unlocks.
- A sign-in log of every sign-in and failure (time, address, device); an alert to the owner's phone when an admin signs in from a new device; "sign out everywhere".
- Confirm it's you: deleting records, changing users, exporting or erasing a person's data needs a fresh passkey check in the last 5 minutes, and every such action is logged.
- Roles decide who sees money, customers and settings; they are checked on every page and every request, not just in the menus. Technicians never see customer contact details or money; outside contractors see only the job they are on.
- A monthly access review lists who can see what, dormant accounts and changes, and raises a task to review it.
Encryption
- In transit: HTTPS only, with HSTS (browsers refuse plain connections), through Cloudflare. The TLS grade is checked weekly (see the live facts).
- Passwords are stored only as bcrypt hashes. Passkeys: we hold only the public half. Secrets the Service uses (keys to Shopify, eBay, email) are kept out of the code, and their nightly backup is encrypted with AES-256-GCM using a key kept off the computer. Supplier portal passwords and two-step secrets are sealed (encrypted) in the database.
- At rest: the database sits on the workshop computer's disk. Whole-disk encryption (BitLocker) on that computer is to be confirmed. The weekly off-site copy is encrypted with AES-256-GCM before it leaves the building.
Backups and recovery
- Every night at 21:00 the database is copied with SQLite's own online-backup method (so nothing half-written is missed), opened and checked straight away, and stored off the premises in Microsoft OneDrive with version history.
- Every month a backup is automatically restored to a scratch copy, integrity-checked and compared table by table with the live database.
- A copy the office computers cannot alter: once switched on, every week an encrypted copy goes to Cloudflare storage under a lock that refuses deletes and overwrites for weeks to months, even from the computer that sent it. This is our protection against ransomware.
Watching and testing
- A self-audit runs every night and every three hours: the site, errors, background jobs, database integrity, backup age, security settings and the tests. Anything wrong becomes a task.
- Every night: known-vulnerability checks on the software we depend on (npm audit), a search for secrets accidentally committed to the code (gitleaks), and static security analysis of our code (Semgrep).
- Every week, out of hours: an automated attack scan of the live site (OWASP ZAP baseline), TLS and security-header grades (SSL Labs, Mozilla Observatory), and our own tests that lockout, passkeys, role limits, signed links, data export and erasure still refuse what they should.
- Every month: a gentle, capped load test and the backup restore test.
- Every result is kept with its date as evidence. A serious finding raises a task and an alert to a phone.
- An independent penetration test is planned before we offer the Service to other businesses.
Changes and code
Changes go through version control, one deployment script that builds alongside the running Service, checks it and rolls back automatically if it is unhealthy, and a change log of who changed customers, prices, users, permissions and settings (before and after). Changes to the online shop go through a single tool that records the value before each change. The code is written with AI coding assistance under written rules (our "Lessons" and checklist) and reviewed for security before major releases.
AI
Every AI feature is listed in an AI register with what it sends and why, has its own off switch, and is logged with its cost. AI output is labelled and is only a suggestion until a named person confirms it. Contact details are removed before sending where the task allows, and our provider does not train on our data.
Customer data and your rights
A register of every kind of personal data, why we hold it and for how long, applied automatically every night with legal holds (accounts are kept 6 years). "Everything we hold" (a full export) and "Erase this person" are built in, logged, and need the "confirm it's you" step. See the Privacy Policy.
Standards
We run an information security management system written to ISO/IEC 27001:2022 (scope, risk assessment, a Statement of Applicability for all 93 Annex A controls, quarterly internal audit and management review, training records). We are aligned with ISO 27001, not certified. Cyber Essentials is planned. We never store card data: payments are taken by PCI DSS compliant providers.
If something goes wrong
We have a written incident and breach-response plan. We contain first (sign-outs, locks, maintenance mode), assess the same day, report to the ICO within 72 hours where the law requires, and tell affected customers without undue delay, with what happened and what to do.
To report a security problem or a suspected vulnerability, email info@eco-torque.co.uk with "Security" in the subject. Please do not test the live Service without our written agreement. We will acknowledge your report within 3 working days.
Adapted in part from the 37signals (Basecamp) security overview by 37signals LLC, used under the Creative Commons Attribution 4.0 International licence (CC BY 4.0). Changes: rewritten entirely for Eco Torque's own set-up; live facts added. The original is provided "as is", without warranties of any kind.