Operational context is used to serve the organization that supplied it.

Account identity and organization membership come from Clerk. Organizations may provide client identifiers, locations, service dependencies, watchlists, and notification configuration. SphynxOC also records security and authorization audit events, delivery outcomes, and operational health telemetry.

Public upstream incident and advisory data is collected from identified provider and government sources and is kept separate from tenant-supplied inventory.

Organization data is used to match upstream conditions to relevant dependencies, produce exposure views, route requested notifications, secure the service, and provide support.

SphynxOC does not sell tenant information. Privacy-safe product measurements may count actions such as onboarding completion or feature use, but should not contain client names, dependency notes, webhook contents, or other sensitive inventory.

Members can access only the active organizations to which they belong. Owners and administrators manage their organization according to role; platform administration is limited to operating and securing SphynxOC and does not create unrestricted tenant-inventory access.

Cloudflare supplies DNS, edge runtime, security, and structured storage. Clerk supplies identity and organization authentication. Slack or another destination receives only notifications an authorized organization or platform administrator configures. Official source operators provide the public incident data SphynxOC monitors.

Requests are handled through the participant’s onboarding contact or authenticated Support control and require identity and organization-ownership verification where appropriate. Some security and recovery records may remain for a limited operational or backup period before expiration.