Your project data deserves serious protection.
A construction project record holds your drawings, your costs, your correspondence and your people. System 1 Build is built so that record stays in the right hands, stays private, and is kept with production backups on redundant infrastructure.
Access is controlled around the project. Files are private and delivered only to people authorized to have them. Production data is backed up, and the service runs on redundant infrastructure. Changes are tested and released deliberately, by people.
Project information stays in the right hands
Most information risk on a construction project is not an attack — it is the wrong person seeing the wrong thing. Access is decided around the job, every time a page is requested.
Your organization's records are yours
Every request is resolved against your organization. Records belonging to another organization are never served, and a lookup across that boundary comes back as not found rather than confirming that something exists.
Project by project, person by person
Being part of the organization is not enough. Someone sees a project when they have been given membership on that project — and when their access is suspended or removed, it stops working immediately.
Outside companies stay in their lane
Subcontractors, designers and other external companies work inside your project under company-scoped access: they see their own company's records on the projects you invited them to. Administrative, directory and commercial surfaces stay closed to them.
People can do what you gave them
What each person can do is governed by what they have been given, and anything not classified for access is refused rather than allowed by default.
The project record stays private
Drawings, photos, contracts and correspondence are the project. They are treated as records to be released deliberately, not as files sitting on a web server.
Files are not public objects
Uploaded files are stored privately, outside any public web path, and are never served directly by the web server.
Every download is authorized
Each download is checked at the moment it is requested, against your project access and against the record the file belongs to. There are no public file links and no unauthenticated file URLs to leak or forward.
What arrived is recorded
A SHA-256 checksum is recorded for every uploaded file at upload time.
Files download rather than execute
Downloads are delivered as attachments by default; only a small allow-list of image and PDF types may render in the browser when you ask for that.
Built for resilience
Production backups and redundant infrastructure are part of how we operate System 1 Build. The work that protects a project record on an ordinary day is the work that counts on a bad one.
Production data is backed up
We maintain production backups as part of our operating practices.
Operated with redundancy
System 1 Build runs on infrastructure Tradeforce operates across US East and US West, with redundancy built into that infrastructure.
Security is built into the product
The protections above are not a policy document bolted on afterwards. They are how the application is built, tested and released.
Accounts exist by invitation
There is no open registration. People join your organization and your projects because someone with the authority to invite them did.
Sessions are held server-side
Sign-in sessions live on the server with protected cookies, and changing or resetting a password signs out every other session on that account.
The browser is kept in bounds
The application controls what is allowed to run in the browser and blocks cross-site request forgery on every state-changing request, with no exclusions.
Abuse runs into limits
Sign-in, password reset, invitations, uploads and exports are all rate-limited, so guessing and flooding run out of room quickly.
Administrative changes leave a trail
Membership changes, invitations, permission changes and ownership transfers are written to an append-only record showing who acted and what changed — visible to your organization's administrators.
Built and hardened deliberately
System 1 Build is developed against an extensive automated test suite, and the platform has been through a dedicated security-hardening programme covering tenancy, authorization, file handling, sessions and browser security. That is engineering work we have done and accepted internally — not a certification or a third-party audit, and we do not present it as one.
Released by people, on purpose
Releases are built from tagged, tested artifacts with dependency audits recorded, and production changes are promoted deliberately by people following a release process — never pushed out automatically.
Privacy, terms and reporting
How information is handled — your organization's role and ours, the data in a project record, the providers involved and your privacy choices — is set out in the Privacy Notice. The Terms of Service govern the website and the service.
To report a security concern about System 1 Build, email security@buildwithtfs.com. It reaches a monitored mailbox.