Section
Trust & Security
How the platform isolates, protects, and accounts for your data — written for the person evaluating us.
Security architectureThe structural guarantees: isolation, a single enforcement point, and identity that can't be spoofed.Tenant Data SecurityHow User Types, DataRoles, and Locations work together to shape an app experience and protect tenant data.User Types: menus and SaaS pagesUser Types define the menu, landing experience, and SaaS app pages each kind of person is shown.DataRoles: data and action permissionsDataRoles define what tenant data a person can see, add to, change, delete, export, or use through approved AI paths.Locations: where tenant data is assignedLocations define where records belong and whether a person works across all, one, or multiple tenant locations.EncryptionIn transit, at rest, and per-field — including tenant-specific keys.TDS 8.0 and SQL Server 2025 transport securityHow BuildWithHQ protects service-to-database traffic with SQL Server 2025, TDS 8.0, strict encryption, and layered authorization.Audit trail and data disclosureThe immutable history of what happened, and the verifiable ledger of third-party access.Tenant logging: the immutable recordA dedicated, append-only history of what happened — built so it can be verified, not just trusted.Replayable authorization: rewinding a security decisionAny past AI data access can be re-derived and re-checked — as of then, and as of now.Battle test: multiple tenants in a BuildWithHQ SaaSHow BuildWithHQ's first-class modules and APIs behaved with multiple tenants, scoped users, and hostile cross-tenant requests.Data lifecycle, residency, and portabilityHow customer data is isolated, exported, backed up to customer-owned storage, and assigned to an enterprise deployment.Business continuity and application portabilityHow applications can relocate to AWS or Azure, or be restored in a cloud or virtual machine if BuildWithHQ shuts down.