Company-scoped data
Application records are scoped to the active company. Database row-level security and server-side authorization checks are used to help prevent one company from reading or changing another company’s records.
Roles and permissions
Owners, administrators, managers and crew members can be given different access. Sensitive actions are protected by server-side permission and membership checks; hiding a button in the interface is not treated as the security boundary.
Authentication and account access
BuildCurrent uses authenticated sessions and secure one-time account setup links. Users are expected to protect credentials and companies should remove access promptly when a person no longer requires it.
Customer-facing access
Customer portal and share links are designed to expose only the records relevant to the intended customer experience. Payment-card entry is delegated to supported payment providers rather than collected directly by BuildCurrent.
Audit and operational safeguards
Selected administrative and financial workflows maintain audit information and use authoritative server-side functions for sensitive state changes. Integrations and service credentials remain on trusted server boundaries where applicable.
Report a concern
If you believe you have found a security issue, use the Contact page and identify it as a security report. Do not include passwords, secret keys or unnecessary customer data.