Receipt numbers
Protected inputs block receipt-shaped values before an API, database, analytics event, email, or AI request can accept them.
GreenLight does not ask for or store your USCIS receipt number. Protected inputs reject receipt-shaped values before they can be decoded, saved, analyzed, emailed, or synced. Selected case details sync only after sign-in, and every outside processor has a named job.
Protected inputs block receipt-shaped values before an API, database, analytics event, email, or AI request can accept them.
Selected allowlisted case fields sync after sign-in. Labels and checklist completion stay on that browser/device.
Saving a status never publishes it. You choose whether to contribute an account-free milestone observation.
No mystery bucket called “case data.” These are the current fields.
Device-only: custom case labels and checklist completion state.
Receipt-free text goes through GreenLight's API. Known statuses use GreenLight's knowledge base; unknown text may use DeepSeek.
If you choose to save, GreenLight stores a fixed safe summary and classification—not your pasted text or AI prose.
A separate Timeline action can contribute account-free milestone facts. Cohorts under 5 observations stay suppressed.
GreenLight does not sell or rent customer data. These providers perform specific operating jobs.
Handles sign-in, selected signed-in case records, safe history, preferences, entitlements, and owner-scoped generated letters.
Provider policy →Delivers the app and can process request, network, cache, security, and operational log data.
Provider policy →Processes unknown receipt-free decoder input and receipt-free RFE drafting input when you request AI help. Its policy says data is stored in the People's Republic of China.
Provider policy →Processes the recipient, rendered message, delivery headers, and delivery information for enabled email.
Provider policy →Processes masked production analytics, heatmaps, session replay, product events, and error or performance signals.
Provider policy →Processes checkout, card and billing information, subscriptions, one-time purchases, refunds, and required transaction records.
Provider policy →GreenLight does not ask for or store your USCIS receipt number. Protected inputs reject receipt-shaped values before they can be decoded, saved, analyzed, emailed, or synced.
GreenLight can sync your case type, field office, filing date, optional priority date, optional visa category, optional country or chargeability area, audience or case segment, and an internal case ID. Supabase creates server timestamps. Custom labels, browser timestamps, profile-repair flags, and checklist completion stay on that device.
The receipt-free text goes through GreenLight's API. Known statuses use GreenLight's server-side knowledge base. Unknown text may be sent to DeepSeek for an explanation. GreenLight does not store the pasted text or put it in analytics. If you save a result, GreenLight stores a fixed safe summary and classification instead of your raw text or AI prose.
No. Community sharing is a separate action you choose. Sharing starts with an authenticated request that includes the owned case and history IDs so GreenLight can verify the contribution. The resulting public observation has no account, case, history, email, IP, or receipt-number field. A separate private HMAC receipt prevents repeat observations from the same case, and public cohorts with fewer than 5 observations are suppressed.
No. GreenLight does not sell or rent customer data. The service providers named in the Privacy Policy process limited data to host the app, provide AI results, deliver email, measure product use, or process payments.
No account required. Unknown receipt-free text may use the disclosed DeepSeek fallback and is not stored in your GreenLight account.
Try the Status Decoder →