CaseStatusTracker resources

Privacy & Data Handling

Updated 2026-10-15 · Editorial review pending

How the local case reader handles your JSON and how account and support services differ.

Local analysis

The case reader parses pasted text or a selected file in browser memory. Its analysis does not send your JSON to our server, an AI provider, or analytics. The output includes a masked receipt suffix and allowlisted case fields. Clear removes input and results from this page; it does not delete your original local file or erase browser-level history.

Accounts and external services

Signing in is optional for the free tools. If you choose to sign in, the existing Google or email verification service processes authentication data. Google One Tap may load a Google script when configured. Account sessions and support submissions are separate from local case analysis.

Support and sensitive information

The contact form sends the details you explicitly enter to our support service, which may use an external messaging provider. Never submit USCIS credentials, tokens, complete case JSON, A-Numbers, or identity documents. Send a general description of the issue instead.

Storage, deletion and release review

Where case saving is enabled, only your chosen alias, form, receipt suffix, record date, event codes/dates and storage consent are sent to our database. Saved cases remain until you delete them. Deleting a case removes its events and consent record. Report purchases are not enabled. Account data deletion, retention terms, service providers, and the final operator identity must be finalized before production launch. This page describes the development implementation and is pending privacy review.

Independent service. Not affiliated with USCIS or the U.S. government.

Read your JSON locally →