A traceable correction and takedown path
DataCedar preserves source lineage so a disputed raw object, document, event revision, or entire source can be isolated, reviewed, and removed without silently rewriting history.
Submit a request
Create a free account, open Support in the dashboard, choose Question, and begin the message with DATA RIGHTS. Include the exact DataCedar event/document ID or source URL, your relationship to the material, the requested action, and a way to verify authority. Never include passwords, API keys, or payment data.
Create an account or open the dashboard.
What happens next
- The request is stored with a durable reference and reviewed for scope and authority.
- Validated requests enter the production takedown queue with a due time and audit trail.
- The worker tombstones documents, retracts event revisions, removes an owned raw R2 object when required, or suspends the source’s newest rights version.
- REST, SSE, MCP, search, timelines, clusters, and webhooks all re-check the same current rights state and fail closed.
Corrections are not erased
When a factual record changes, DataCedar normally appends a corrected revision so historical as_of queries remain reproducible. Content that must no longer be served is withheld or tombstoned; the public API cannot use a later revision to rewrite an earlier information cutoff.
Transport is not permission
Using an API, RSS feed, public page, proxy, Decodo, or archive changes acquisition reliability—not ownership or redistribution rights. Customer responses are governed by the current source-rights registry.