When corporate data-rights responses stall, deflect, or contradict, DataTrace preserves original records unmodified, deterministically verifies findings against exact text segments, and grounds actionable complaint drafts.
"I hereby request the immediate deletion of all personal data and associated accounts held by Acme Corp under GDPR Article 17."
Generic language models invent quotes, state legal compliance conclusions without checking rules, and silently turn ambiguity into false certainty. They produce allegations they cannot substantiate in formal dispute.
DataTrace treats the model strictly as a proposal generator. State transitions (UNVERIFIED → AI_INFERRED → CORROBORATED → VERIFIED → CONTRADICTED) are executed exclusively by pure TypeScript rules evaluating preserved evidence bytes.
Every assertion in a DataTrace case record must ascend through distinct verification gates before entering a complaint.
RFC-822 emails, text-PDFs, and manual notes are buffered, hashed with SHA-256, and sealed in private case storage. Original bytes are never modified.
Under strict user consent and privacy minimization, models propose claims, entities, and events citing human-readable display IDs (EV-101 #03).
Pure code rules check citation validity, exact quote substrings, object/subject anchors, and hedge words. Only DIRECT claims reach VERIFIED.
The complaint draft links assertions to verified findings. Fail-closed grounding prevents unbacked assertions from being exported.
Designed specifically for individuals and compliance advocates navigating stall tactics, evasions, and contradictions.
Automatically maps each data-access or deletion demand to corporate replies. Unanswered requests are explicitly designated with verified timestamps and the spec-mandated standard phrasing:
Evaluates coverage: FULL, PARTIAL, DEFLECTED, or UNCLEAR. Flags chronologically impossible responses.
When an organization provides conflicting claims across separate emails (e.g. stating data was deleted, then later claiming retention), DataTrace displays both verified passages side-by-side with original citations:
Mechanical contradictions resolve via normalized opposite polarity; ambiguous pairs require human confirmation.
Every file upload, extraction, state transition, and report export appends to a gap-free PostgreSQL hash chain. Tampering with any historical row breaks the cryptographic chain head.