How Dispel handles your data
This page describes the current product posture for uploads, reports, analytics, API access, and provider-backed analysis. It is written to match the implemented product rather than overstate maturity.
What we collect
Dispel stores the content you submit for analysis, analysis results, evidence items, share-link metadata, API key metadata, billing state, and limited product analytics when analytics storage is enabled.
Why we collect it
We use submitted content to generate trust assessments, retain investigation history, power shareable reports, secure programmatic API access, and improve product reliability.
What we do not claim
Dispel does not infer hidden intentions, mental state, or biometric truthfulness. Outputs remain calibrated product judgments based on inspected evidence, not certainty.
Retention and deletion
Uploaded files and saved analyses remain in the workspace until they are deleted or rotated by future retention controls. Public report links expose only the shared analysis summary for the specific token.
Providers and processors
When remote providers are configured, specific analysis inputs may be sent to those providers to perform OCR, transcription, or model-backed inspection. When providers are unavailable, Dispel falls back to local heuristics or returns Unknown.