Transport security
Public pages and application endpoints use HTTPS. That keeps requests encrypted while they travel between the browser, the app, and backend services.
This page explains the public-facing security and trust posture of the service so visitors can understand how their data is handled and how the platform is accessed.
Public pages and application endpoints use HTTPS. That keeps requests encrypted while they travel between the browser, the app, and backend services.
Sign-in relies on managed identity flows. The site and app separate public browsing from authenticated actions, which helps keep account operations predictable.
Team data is shown according to the permissions attached to the account. Shared links and downloads are tied to the relevant subscription and access rules.
Security is not only a feature; it is part of how the service is operated.
Only the data needed to provide the service should be collected. The privacy policy explains the kinds of account, roster, analytics, and billing data that may be processed.
The platform is designed so that maintenance, deployment, and backend changes do not require the entire site to go dark. Public pages remain available even when app state is changing.
Security works best when visitors and customers have clear actions.