Documented boundaries. No blanket claims.
This page states the access, data, and integration boundaries currently supported by product evidence. Enterprise requirements beyond them are scoped during procurement.
Scoped project access
Client access is scoped through organization, workspace, and project membership. Dashboard, report, and integration access remains subject to the user's project permissions and the features enabled for that project.
Client-safe evidence
Client-facing dashboards and reports present supported findings, evidence, actions, and neutral unavailable states. Internal methodology artifacts, staff commentary, and raw operational detail are not client-facing deliverables.
API, MCP, and webhook boundaries
Eligible paid projects can access supported CiteSurge data through the REST API and MCP. Audit-run webhooks use signed payloads. All three remain subject to plan, project permissions, and feature availability. See the API documentation, MCP documentation, and integration help.
Privacy and legal documents
Security questions
Send security, data-handling, or procurement questions to [email protected]. Requirements not documented above are assessed for the proposed scope; this page does not imply unlisted controls or commercial commitments.