compare_consent_observations
ChatGPTCompares two supplied RegSentry runtime snapshots of the same domain, phase by phase. Marks missing controls and incomplete observations unresolved. Reports newly observed or no-longer-observed tracker attempts without claiming causation, compliance or a verified fix. Stores nothing and makes no network requests.
export_consent_report
ChatGPTFormats a supplied RegSentry runtime snapshot as a private plain-text report with its date, method, phase results and limitations. Returns file content without publishing, sharing, or storing it. Does not turn supplied evidence into a compliance certificate or legal opinion.
get_remediation_playbook
ChatGPTReturns deterministic, tracker-specific consent-gating guidance from RegSentry's maintained playbooks. It does not change a website, contact a vendor, or verify that a fix was implemented.
inspect_runtime_consent
ChatGPTVisits an authorized public homepage in three isolated browser sessions and records known tracker request attempts before consent and after exact reject-all or accept-all buttons. Blocks non-GET requests, forms, credentials and persistence; reports missing controls and incomplete runs explicitly. Changes only temporary browser consent state. Bounded observations are not proof of transmission, compliance or a violation.
inspect_site_tracking
ChatGPTPerforms a bounded, non-persisting GET of an authorized public domain's homepage and reports tracker markup, consent setup signals, and runtime-verification gaps. It does not run JavaScript, submit forms, create a RegSentry record, or make a legal determination.
interpret_consent_evidence
ChatGPTDeterministically grades a redacted set of tracker-request observations by consent phase. It computes from the supplied data only, stores nothing, and returns a technical—not legal—interpretation.
compare_consent_observations
ClaudeCompares two supplied RegSentry runtime snapshots of the same domain, phase by phase. Marks missing controls and incomplete observations unresolved. Reports newly observed or no-longer-observed tracker attempts without claiming causation, compliance or a verified fix. Stores nothing and makes no network requests.
export_consent_report
ClaudeFormats a supplied RegSentry runtime snapshot as a private plain-text report with its date, method, phase results and limitations. Returns file content without publishing, sharing, or storing it. Does not turn supplied evidence into a compliance certificate or legal opinion.
get_remediation_playbook
ClaudeReturns deterministic, tracker-specific consent-gating guidance from RegSentry's maintained playbooks. It does not change a website, contact a vendor, or verify that a fix was implemented.
inspect_runtime_consent
ClaudeVisits an authorized public homepage in three isolated browser sessions and records known tracker request attempts before consent and after exact reject-all or accept-all buttons. Uses temporary browser sessions, blocks non-GET requests, supplies no user credentials, and reports missing controls and incomplete runs. Page scripts and consent controls may make public GET requests, which can have remote effects. Bounded observations are not proof of transmission, compliance or a violation.
inspect_site_tracking
ClaudePerforms a bounded, non-persisting GET of an authorized public domain's homepage and reports tracker markup, consent setup signals, and runtime-verification gaps. It does not run JavaScript, submit forms, create a RegSentry record, or make a legal determination.
interpret_consent_evidence
ClaudeDeterministically grades a redacted set of tracker-request observations by consent phase. It computes from the supplied data only, stores nothing, and returns a technical—not legal—interpretation.