Privacy notice
Privacy coverage for the public site, onboarding, and workspace routing.
This notice covers the platform-owned public domain, including the landing page, workspace discovery, registration, provisioning updates, and public status surfaces. Customer tenant workspaces remain tenant-scoped environments with their own operational context.
What the public domain processes
- Workspace discovery identifiers such as workspace slug input or approved work email domains.
- Registration and provisioning details needed to create a tenant and its initial administrative account.
- Security verification and abuse-prevention signals required to protect discovery and login entry flows.
- Public-safe operational telemetry used to present status information without exposing private tenant content.
Why the data is used
Data collected on the public domain is used to route users into the correct tenant sign-in experience, provision new tenant environments, protect public entry routes, and keep a credible operational trust surface available for customers and evaluators.
How tenant data remains separated
Tenant users, tenant-local configuration, and tenant content are managed inside tenant boundaries rather than being duplicated into the public entry experience. The public domain stores only the shared platform information needed for routing, provisioning, billing coordination, and platform administration.
Cookies and browser state
The platform may store limited browser state such as a return-workspace shortcut under the platform-owned domain so returning users can be routed back to an active tenant safely. Security, session, and anti-forgery controls may also use cookies where required for normal application behavior.
Operational and legal follow-through
Public-site privacy handling works alongside the service terms, security posture, and status communication model. Customers evaluating the platform should review those pages together to understand the full public trust surface.