Hi Product Hunt - I'm Cheney, founder of Guardian Compliance. I built Guardian after a small document mismatch almost derailed my own STEM OPT. My training plan and offer letter described the same work in different language. To me, it was obvious. To a reviewer, it could look like two different jobs. The hard part was not filling one form. It was keeping the whole record straight: I-20s, I-983s, EADs, tax returns, foreign-account thresholds, entity paperwork, deadlines, and old emails that quietly contradict the next filing. Guardian is the product I wanted then: a Claude extension that turns Claude into a local compliance agent. What it does today: - Installs into Claude Desktop as guardian.dxt - Starts with /guardian - Keeps a local data room and facts source-of-truth on your machine - Parses and classifies immigration, tax, and entity documents - Cross-checks document mismatches, missing forms, and deadline risks - Generates Form 8843 and other filing guidance - Shares a data room only when you explicitly approve it The privacy point matters: immigration and tax documents are not normal SaaS data. Guardian's default direction is local-first, so the sensitive record lives on your computer and Claude works from that record. Who it is for: - International students on F-1, OPT, STEM OPT, or J-1 - H-1B workers and founders managing their own paper trail - Nonresidents with 1040-NR, FBAR, Form 3520, or Form 5472 uncertainty - Foreign-owned US entities trying to keep tax and immigration facts aligned I would love feedback on three things: 1. Does the Claude extension install flow feel simple enough? 2. What document chain should Guardian support next? 3. Would you trust a local-first compliance agent more than another web app upload flow? I'll be in the comments all day. Feedback, edge cases, and skeptical questions are all useful. - Cheney

Guardian Compliance

Check immigration and tax docs inside Claude

Check immigration and tax docs inside Claude