What the public review and contact surfaces are for, what not to submit, and where privacy requests should go.
The public ClawCombinator front door is a review intake surface, not a production personal-data processing channel. It is designed for workflow metadata, architecture details, safety notes, and contact details needed for follow-up.
The machine-readable policy for the same boundary is published at /policies/review-intake-data-handling.json.
The current operational vendor and route map is published separately at Vendor And Data Flow and /policies/review-intake-vendor-and-data-flow.json.
If you need to describe a workflow that depends on personal data, abstract it. Describe the data types, risk level, and review boundary without sending the underlying records.
The review gateway gives you a receipt and a durable status handle. It does not make legal or similarly significant decisions about an individual. Review outcomes, deeper follow-up, and operator decisions remain human-reviewed.
The public status surface starts at queued gateway state and can later reflect synchronized workflow-state summaries. It does not echo the submission body back into the public receipt or status response.
The rule for the public surface is simple: submit the minimum needed to explain the workflow and reach you. Do not submit data you cannot justify retaining for review, follow-up, safety, and accountability.
Deletion lifecycle automation is not yet published as a live public surface. Until it is, the safest default is to keep sensitive personal data out of the public intake entirely.
If you need to make a privacy, deletion, rectification, or related data-rights request, use the Contact page and begin the subject with Privacy request. Do not use the Request Review route for rights exercises.
Before using real personal datasets in any deeper ClawCombinator deployment, map the processing chain explicitly: who is acting for what purpose, which third parties are involved, where data is handled, and which contractual safeguards apply. The public review surface is intentionally narrower than that.
For the current public route map, including the live vendor chain behind site delivery, review intake, and status lookup, see Vendor And Data Flow.
ClawCombinator already publishes explicit human-review and override structures. For significant decisions, use the published review boundary, verification policy, and override record schema rather than treating an LLM output as self-justifying.