Data Security

Tenant separation

Shop workspaces are separated by tenant checks so each shop only sees its own sales, service jobs, customers, settings and inventory.

Access control

Shop staff and platform administration areas are separated. Passwords are hashed and sensitive configuration stays outside source code.

Least privilege

Access to platform administration and support tooling should be limited to people who need it for their role. Access should be removed or changed when it is no longer needed.

Encryption and transport security

The live service should be delivered over HTTPS. Passwords are stored as hashes, and sensitive fields or secrets should be encrypted or kept outside source code where practical.

Application security

The platform should use framework security controls such as CSRF protection, validation, authentication middleware, file-upload checks, route permissions and tenant checks to reduce common web application risks.

Secrets and configuration

API keys, payment secrets, webhook secrets and sensitive service credentials should be stored in environment configuration or secure platform settings rather than public code or browser-visible files.

Monitoring and incident response

We record selected error, login, security and analytics events so faults and suspicious activity can be reviewed. Confirmed incidents should be contained, investigated, recorded and escalated according to the level of risk.

Vulnerability handling

If a security weakness is reported or discovered, we aim to assess the risk, prioritise a fix, test the correction and deploy it without exposing unnecessary information about live customer data.

Data access and confidentiality

Operational access to customer or shop records should be limited to authorised people who need it for support, security, maintenance or legal reasons.

Customer-side controls

Shops help protect their own data by using strong passwords, limiting staff access, avoiding shared logins, protecting exported files, keeping devices secure and telling us quickly about suspected misuse.

Fair usage controls

Usage limits protect service reliability and prevent one account from consuming disproportionate server resources.

Backups

The production roadmap includes scheduled encrypted backups, restore testing, backup logs and shop-level export controls. These controls are part of resilience, but they are not a guarantee that every record can always be restored in every incident. Shops should still keep their own independent exports of critical records.

Business continuity

Each shop should decide what records it needs outside Manage Repairs to keep operating during a service outage, security incident, data corruption event or account access problem. This may include exported customer, repair, invoice, stock, VAT, supplier and order records.

Change management

Product changes, migrations and deployments should be tested locally or in a safe environment where practical, versioned, and deployed in a way that avoids deleting live client data.

Operational controls

Updates should be versioned in GitHub, tested locally, deployed incrementally and migrated without deleting live data.