What this is
A community-run tally of how H-1B extension petitions fared when the beneficiary had a prior arrest or charge on record. It exists because there is no public dataset on this, and people facing it are largely guessing.
What this is not
It is not legal advice, and it cannot tell you what will happen in your case. Adjudication turns on the specific charge, the specific disposition, the evidence filed, and the officer. Two people with the same checkbox answers can get opposite results for reasons this form cannot capture. Talk to an immigration attorney.
It is also not a random sample. Everyone here chose to report. Bad outcomes are more memorable and more likely to be submitted than routine approvals, so the approval rate shown is probably lower than the true rate. Treat every number as a rough signal about the community, not a base rate.
What is collected
Five multiple-choice answers and an optional year. That is the entire record — there is no free-text box anywhere on this site, deliberately. A comment field is the one place people accidentally identify themselves, and nothing here needs one.
Never collected:
- No name, email address, or account of any kind
- No employer name — only a broad category
- No receipt number, case number, court, or attorney
- No city, state, or service center
- No IP address is stored. Abuse limiting uses a salted hash on a salt that rotates every 24 hours, and those rows are deleted once they expire — so there is nothing to trace back to, even for us.
- No analytics, no third-party scripts, no cookies, no tracking pixels.
Small numbers are shown, not hidden
Many published statistics hide any group smaller than five. This site deliberately does not, and it is worth explaining why, because the reasoning decides how much you should trust the early numbers.
That convention exists to defeat linkage attacks — where someone joins a "anonymous" dataset against another one to work out who is who. The famous demonstration used ZIP code, date of birth and sex to re-identify most Americans from voter rolls. It works because those fields exist in both datasets.
Nothing here is like that. Employer category, charge category, disposition, outcome and year appear in no other database anyone can join against; there is no registry of "people at a big tech company with a DUI". The only thing left is someone who already knows your situation using the page to confirm it — and a threshold of five would not stop that either, since they would look at a group of five and still know you were in it.
Hiding those numbers also had a real cost: the site showed nothing at all until ten people had responded, which is precisely when a tracker most needs to look worth contributing to.
What that means for you as a reader: mind the denominator. Early on a "67%" may be two cases out of three. Every percentage is shown with the count behind it — read that first, and treat anything under about thirty responses as a hint, not a finding.
What that means for you as a submitter: with few responses, your combination of answers may show up on the results page as a count of 1. Nothing in it can name you — but if that bothers you, wait until the dataset is larger, and remember you can delete your entry at any time with your link.
What actually protects you here is the data model rather than arithmetic:
- Individual rows are never published. Only totals are ever shown on this site. The database is backed up to private storage, which is not published.
- There is nothing in a row that can identify you — no name, employer, case number, location or IP address, and no free-text box to slip into.
- Your entry is yours to delete, instantly, with no email and no questions.
- Open cases are counted apart from decided ones. A pending case adds to the response total but is excluded from every rate, so reporting early never drags the approval rate down.
Your entry stays yours
On submission you get a private link containing a random token. It is the only way to reach your entry. We store only a one-way hash of it, so we cannot recover it, look your record up, or link it to you — and neither can anyone else. Use it to update your entry as your case moves, or to delete it at any time, no questions and no email.
Deleting removes your entry from the live dataset and from every published number. To be straight with you rather than over-promise: the database is backed up privately, so a copy of an already-deleted row can persist in an old backup for a while. Nothing from it is ever published again.
Because that link is the sole key, treat it like a password: don't paste it into the group chat. Anyone holding it can edit or delete that entry.
Nothing can remind you to come back. With no email address and no account, there is no way to reach you — that is the cost of real anonymity, and it is deliberate. The one thing this site can do is remember the link in your own browser, so returning on the same device offers it back to you. Clear your site data or switch devices and that goes away. Save the link yourself; it is the only durable copy.
Where it runs
On Cloudflare Workers and a Cloudflare D1 database. Cloudflare, as the network carrying the request, necessarily sees your IP address in transit the way any website's host does — this application simply never writes it down.