Rhindon Cyber logo
    Support & Documentation
    Contact Support

    Anonymous AI Concerns Channel

    The Anonymous AI Concerns Channel gives anyone — employees, contractors, customers, or the public — a safe way to raise an AI-related concern (bias, safety, privacy, transparency, accountability, or other). It implements ISO/IEC 42001:2023 Annex A.3.3 (Reporting of concerns) and is available on Professional and Enterprise tiers when the per-organization ISO 42001 toggle is enabled.

    Enabling the channel

    An OrgAdmin enables the channel from Admin → Org Settings → Anonymous Concerns. Enabling auto-mints an opaque 24-hex public token and shows the shareable URL /concerns/{token}. Distribute that URL anywhere people need to reach you (intranet page, contract clause, public website footer, QR code).

    You can rotate the token at any time. Rotation immediately revokes the previous URL (it returns 404) and mints a new one. Use rotation if a link is over-shared, leaked, or after a period you've defined for hygiene.

    Disabling the channel returns enabled=false from the public resolver instantly; the public form shows a "channel not available" notice. Existing submissions stay in the inbox for triage.

    Anonymity & abuse protection

    • True anonymity: a submitter may leave contact email blank. If they do provide a contact email, the platform forces is_anonymous=falsevia a database trigger — the UI cannot lie about anonymity.
    • hCaptcha: every submission is verified server-side against the platform hCaptcha secret before it is accepted.
    • IP rate limit: 5 submissions per hour per organization + IP. The raw IP is never stored — only a SHA-256 hash is kept for the rate-limit window.
    • No metadata leakage: anonymous submissions do not capture user-agent, referrer, or any browser fingerprint beyond the hashed-IP rate counter.

    Triage workflow

    OrgAdmin and WorkflowAdmin users see incoming concerns at /governance/concerns. Lifecycle:

    new → under_review → actioned → closed (or → dismissed at any point with reason)

    • Triage: move from new to under_review; capture internal triage notes.
    • Action: record what the organization did in response.
    • Close: terminal state with closure notes; the record remains as audit evidence.
    • Dismiss: requires a reason (spam, duplicate, out of scope). Records are never deleted.

    Only OrgAdmin can enable/disable the channel or rotate the public token. WorkflowAdmin can triage but cannot change channel configuration.

    Audit trail

    Every action emits an audit code to both the org Activity Log and the Platform Audit Log:

    • CONCERN_SUBMITTED — public form submission accepted
    • CONCERN_TRIAGED — moved to under_review
    • CONCERN_CLOSED — terminal closure with notes
    • CONCERN_DISMISSED — dismissed with reason
    • CONCERNS_CHANNEL_ENABLED / CONCERNS_CHANNEL_DISABLED — channel toggle
    • CONCERN_TOKEN_ROTATED — public token rotation

    These codes feed into the ISO 42001 Annex A.3.3 platform statement, which is automatically recognized as Full coverage on your Annex A report once the channel is enabled.