Skip to content
FireeCMS

Security

Security and data handling.

Project data is commercially sensitive. These are the controls FireeCMS is built around, described plainly, without claiming certifications we do not hold.

Tenant isolation

Every authenticated request is resolved to a company. Data access is scoped by company, and services re-validate that the referenced project or entity belongs to the caller before reading or writing. A user from one company cannot address another company’s records by guessing an identifier.

  • Company-scoped queries on tenant data
  • Ownership re-validated in the service layer
  • Platform administration is a separate, restricted surface

Authentication

Passwords are hashed with bcrypt and never stored in plain text. Sessions use short-lived JWT access tokens with refresh-token rotation, delivered to the browser as httpOnly, SameSite cookies. In production, cookies are marked Secure.

  • Bcrypt password hashing
  • Short-lived access tokens + refresh rotation
  • httpOnly and Secure cookies in production

Authorisation

Permissions are enforced on the server for every protected route using database-backed roles. Hiding a button in the interface is a convenience, not the control. A request without the required permission is rejected with 403.

  • Six default roles with granular permission codes
  • Server-side checks on every protected route
  • Client accounts restricted to the read-only portal

Audit trail

Critical changes, including BOQ approvals and version updates, write an audit record with the actor, action and before/after state. This supports internal review and dispute resolution.

  • Before/after state captured as JSON
  • Actor and timestamp on each record
  • Approvals recorded separately from edits

Documents

Uploads use time-limited, signed URLs rather than public buckets. Downloads are generated on demand and expire. Storage can run on S3-compatible object storage or a local backend for development.

  • Signed upload and download URLs
  • Expiring links
  • Pluggable S3 / local storage backend

Hosting & operations

The API and database are kept on a private network; the database is not exposed to the public internet. Traffic is served over TLS. Backups, monitoring and retention are configured per deployment.

  • TLS for all public traffic
  • Database not publicly reachable
  • Backups and monitoring configured per environment

Reporting a security issue

If you believe you have found a vulnerability, email us at hello@fireecms.com with enough detail to reproduce it. Please do not test against another company’s data or disrupt live projects. We will acknowledge receipt and keep you updated.

Contact the team

See it with your own projects

Bring your projects, BOQ and site work into one place.

Book a walkthrough and we will show the workflow on a sample company, from client and project setup through BOQ approval, procurement and the client portal.