Privacy Policy

DeepHelp AI processes the message text, URL string, document, or screenshot you submit. It also processes an opaque browser-session identifier, limited technical request data used for security and rate limiting, and an email address if you join the waitlist.

Raw submitted text, raw uploaded files, and full extracted file text are processed in memory. DeepHelp AI persists a content hash, a short redacted or generated preview, input type, timestamps, processing metadata, verdict fields, and evidence needed for current-session history.

Raw uploads and full extracted text are not written to a database, temporary files, S3, or Buckets. Upload history does not retain the original filename stem.

The browser creates an opaque random session identifier in localStorage. The API stores only its HMAC hash to scope history and prevent one browser session from viewing another session's records. Client IP addresses are normalized and immediately HMAC-hashed for abuse controls; raw IP addresses are not stored. For protected operational review, DeepHelp also stores a shortened Network ID that rotates daily, coarse country and region when locally or ingress-provided, a bounded country-source label and a conservative possible VPN, proxy, or device-timezone mismatch indicator, browser family and major version, operating-system family, and a broad device class, plus the browser-resolved bounded IANA timezone identifier for daylight-saving-aware operational timestamps. Timezone is not inferred from location or used to replace country. Browser clock readings, raw UTC offsets, the full User-Agent, precise location, device fingerprints, and durable cross-session identity are not stored. This context is available only in a protected individual check detail, not public results, history, metrics, logs, or exports.

Depending on deployment settings, our AI provider may process the current submission to support extraction, risk-signal analysis, or explanation refinement. Provider requests use storage-disabled settings, and DeepHelp does not enable browsing, tools, code execution, or external actions for this processing. When enabled, submitted URL strings may also be checked against our Web Risk reputation service provider; only the URL string is sent, reputation results can only add warnings, and DeepHelp does not persist the URL or the provider response. Local analysis remains available when optional provider features are disabled or unavailable.

Information is used to provide the requested analysis, maintain session-owned history, protect the beta from abuse, operate and debug the service using bounded metadata, and send product updates to people who join the waitlist.

Raw upload buffers and full extracted text are not retained after processing by DeepHelp AI. Analysis hashes, previews, metadata, verdicts, history records, audit metadata, and waitlist emails are persisted. The current repository does not define a public deletion schedule, so formal retention periods require product and legal review.

DeepHelp AI uses session isolation, HMAC hashing, validation, bounded processing, restrictive browser headers, and rate limits. You can clear local browser storage to replace the browser-session identifier, but doing so disconnects that browser from its prior session history.

Send privacy questions to [email protected].