Client context and account access
The application uses authenticated workspaces and client project boundaries. Account and project routes are not public SEO pages. Authentication and authorization protect those records; robots.txt and search directives are not security controls.
Review the product workflow to understand where questions, answer evidence and reports are used. Only give a project the information needed for its intended task.
Provider collection and observation scope
A live run may send its approved question and the required collection context to the configured provider. Website collection and a direct model API study are separate observation surfaces. Current adapter and integration statuses appear in platform readiness; their presence in code does not establish production acceptance.
Review the quoted operation and available allowance before starting collection. The measurement method explains evidence boundaries, and privacy records provider and data-processing information under review.
Public tools use supplied inputs
The public HTML checker, robots rule reviewer, question builder, saved-answer utility and template editors process their form inputs in your browser. They do not transmit those inputs to a model or create a project. Copy and download actions are initiated by you.
A local tool result is not a certification of live network access, search indexing or provider behavior. The separate authenticated project workflow has its own collection and evidence handling.
Policies and commitments
Do not infer a certification, residency guarantee, retention period or service-level commitment from this overview. Final legal and data-processing terms remain part of production readiness.
Privacy, terms and plan availability are maintained separately. Confirm the relevant terms before using sensitive client information.