Tenant isolation
Company records are scoped through active-company membership and database access policies. Server-side functions that perform sensitive actions validate authentication, organization membership and required permissions.
Access governance
BuildCurrent supports role-based permissions and company-specific access. Platform-owner functions are separated from ordinary tenant administration, and customer-facing views are separated from internal staff workspaces.
Data handling
The Privacy Policy describes the categories of information processed and the reasons it is used. BuildCurrent uses external infrastructure and service providers where needed for hosting, authentication, email, payments and supported integrations.
Payments and integrations
Supported card payments are handled through payment-provider checkout rather than raw card entry inside BuildCurrent. Integration credentials and privileged service actions are kept on trusted server boundaries where applicable.
Product controls
Financial and subscription workflows use server-authoritative calculations and guards where required. Audit information is retained for selected administrative and financial actions. Usage limits are enforced by the service rather than only displayed in the interface.
Questions
For privacy, security, procurement or control questions, use the Contact page.