Frequently Asked Questions
Understand the public scan, evidence states, review boundaries, and next steps.
25 questions
It checks one public homepage for directly observable HTML and content signals, then returns prioritized findings and explicit method limitations.
No. It does not execute JavaScript or crawl linked pages or files.
No. The public result separates observed checks, findings, source status, and limitations instead of inventing a composite score.
No. Rankings, citations, traffic, leads, and revenue are not measured or guaranteed by the public scan.
Supported, limited, unknown, and review-required states remain separate so teams can see what still needs evidence or approval.
No. Technical, compliance, commercial, and publishing decisions remain accountable human decisions.
No. It is clearly labeled demonstration content and contains no real customer data.
No. The approved boundary is controlled assistance followed by manual review and manual application.
Email support@compasscite.ai with the workflow you want to evaluate and the responsible review roles.
Use support@compasscite.ai and include the route, locale, visible error code, and reproduction steps when possible.
An evidence gap is technical proof that is missing, unclear, outdated, conflicting, or difficult to extract and verify.
Observed, sampled, reviewed, conflicting, stale, limited, and unknown states remain visibly distinct where the workflow supports them.
Unknown means the current source scope cannot prove the value. It is a valid review state, not hidden certainty.
No. Product, region, operating condition, standard version, and validity may require an authorized source document.
It organizes authorized sources, versions, applicability, review state, conflicts, and next actions.
They keep their state and are routed for review instead of being silently collapsed into one value.
No. It organizes reviewed evidence and unknowns so qualified people can make the decision.
No. It prepares source-grounded content for human review and manual use.
It helps reconnect recorded objections with newly reviewed evidence for human-led follow-up.
It records structured non-PII outcomes as reviewable inputs for future evidence updates and rescans.
Authenticated server context determines tenant identity; client tenant headers are not a trust source.
Sensitive-data checks occur at required production boundaries, and raw PII is not written to ordinary logs.
AI calls pass through the approved control layer so inputs, outputs, and applicable evidence boundaries remain auditable.
Not yet. The visible store action remains disabled until a verified listing URL is approved.
Use support@compasscite.ai for installation, authorized connection, and manual-review questions.