Security

Buziness OS runs on managed cloud infrastructure with a managed Postgres database. Data in transit between your browser and our servers is encrypted with HTTPS. We don't run our own data centers or hand-roll the pieces that are better handled by our infrastructure providers.

Every workspace member has a role — admin, sales, marketing or read-only viewer — and the product enforces what each role can see and change. A viewer can browse the pipeline and reporting but can't send outreach, place calls or edit records. Workspace admins control who's invited and what role they hold.

Buziness OS is early-stage software. Sign-in currently uses a shared workspace password rather than per-user authentication, and single sign-on is offered as part of a Scale plan build-out rather than a self-serve toggle today. If your team has specific authentication, audit-log or access-control requirements, tell us before onboarding — we build against real requirements rather than shipping checkbox compliance.

If you find a security issue, please tell us before disclosing it publicly, and give us a reasonable window to fix it. Tell your Buziness OS account manager, or the admin of your workspace what you found and how to reproduce it. We don't currently run a paid bug bounty, but we credit researchers who report responsibly.

Customers on Growth and Scale plans can request a signed Data Processing Addendum covering our role as a processor of the personal data in your workspace, subprocessors we use, and data-residency terms. Ask your account manager and we'll send one over.