Skip to main content
Request access
Menu

Documentation / security

Public security boundary

The security controls that keep public content, browser state, credentials, and secure handoffs separated.

AudienceSecurity reviewers, Developers, Enterprise buyersStatusapprovedSections2

Documentation section

Browser-safe by default

The public static bundle contains reviewed content, no production credentials, and no live AI provider path. Forms prepare local handoffs and do not transmit or store submissions.

  • No secrets in browser code.
  • No authenticated execution in the public shell.
  • External handoffs use approved origins.

Documentation section

Review the controls

Security guidance covers URL validation, content boundaries, replay resistance, request limits, safe error behavior, and the separation between public and internal routes.

  • Read the Trust Centre.
  • Review the developer security page.
  • Escalate a concern through Contact.

Continue reading

Use the next-level routes

Documentation links are registry-backed and stay within reviewed public destinations. Use Search to combine this page with APIs, domains, applications, blogs, research, resources, and FAQs.

Related routes

/trust/security//developers/security//contact/
Open developer securityOpen the Trust CentreBack to security

Search CINTENT.tech

Search reviewed public content. Hosted search is not connected.

Voice is optional and requires explicit consent.
Enter a term to search reviewed public content.

Open full Search

Voice input is optional and requires explicit consent. Your browser may process audio using its own speech service. CINTENT.tech does not store raw audio; the transcript is placed in the editable question field and is not submitted automatically.