AutoFill Portal

Autofill government permit forms from your project CSV. Smart field matching, section learning, AI suggestions, and portal memory.

# AutoFill Portal — Chrome Web Store Listing (v1.5.8) --- ## Short Description (132 characters max) Autofill government permit forms from your project CSV. Smart field matching, section learning, AI suggestions, and portal memory. **Byte count: 130** ✓ --- ## Long Description (up to ~5000 characters for CWS) Upload your contractor CSV once. AutoFill Portal reads the permit form on your current page, matches every field to the right spreadsheet column, and fills it in — no copy-pasting, no hunting for the right cell. **Smart matching — five levels:** • Exact match: field name matches CSV column name directly • Normalized match: handles spaces, underscores, capitalization differences • Fuzzy semantic match: scores all columns using TF-IDF similarity + abbreviation expansion • Portal memory: applies corrections you made on a previous visit to this portal, automatically • AI suggestions: Claude Haiku fills unmatched description or scope fields using your project data **Fill permit PDFs:** • Upload any permit PDF — AcroForm fields are extracted automatically • AutoFill matches your project data to every field using the same five-level matching pipeline • AI-powered PDF form understanding — Claude AI reads permit PDFs like a human, identifying every field regardless of how the PDF was created • Smart caching — common permit forms are analyzed once and cached, so fills get faster and cheaper over time • Checkbox intelligence — yes/no permit checkboxes (licensed, insured, bonded, hazmat, flood zone, etc.) are filled automatically using rules-based defaults and project scope detection from your CSV description • Review and adjust any field before saving • Download the completed, filled PDF instantly — no server upload, no data leaves your browser • Portal memory learns from PDF fills too: the second user to fill the same PDF form gets automatic pre-fills **Contractor profile (My Info):** • Store your license number, phone, email, address, insurance certificate, and bond number once • Add unlimited custom fields with semantic label matching for jurisdiction-specific requirements • Profile fields fill contractor sections automatically on every portal and PDF — no re-entry needed • Profile data never leaves your browser and is never sent to any third party **User accounts:** • Create a free account at autofillportal.com to access the PDF Filler and manage your API key • Account dashboard shows your email, plan, API key, and profile completeness • Rotate your API key at any time from the account page • Full signup → login → PDF Filler flow — no manual key entry required **Self-learning system:** • Learns from every alt-panel correction you make — both on the current portal and across portals • Structural patterns (no user data) are extracted by Claude Haiku and applied globally • High-confidence cross-portal patterns auto-fill in the background without interrupting you • Negative feedback (user edits) reduces pattern confidence automatically • Daily clustering groups related patterns into meta-rules for stronger generalizations **Multi-entity form support:** • Contractor info (My Info): license, phone, email, address, insurance — pre-fills contractor sections • Project data (CSV): addresses, scope, permit numbers, dates — fills project sections • Owner/Client info: property owner fields routed to owner-pattern CSV columns automatically **Intelligent section classification:** • 4-level hierarchy: DB-confirmed → voted types → module-level AI cache → on-demand Claude Haiku • Section types: Contractor, Project/Site, Owner/Client, Neutral • Column restrictions per section prevent cross-contamination (contractor data never fills project fields) **Date field intelligence:** • Detects date format per field via Claude Haiku (placeholder/label analysis) • Signature-date pairs filled with today's date automatically (200px proximity rule) • Project dates (start date, completion date) pulled from CSV columns when available • Native date inputs (input[type=date]) always formatted YYYY-MM-DD with React/Vue events **Portal memory and continuity:** • Corrections saved per domain — field→column mappings reapplied on next visit • Session continuity: values from earlier in the same multi-step form are reused • Submission history: tracks what was filled for each project row over time • Form change detection: alerts you when a portal's field structure has changed since your last fill **Confidence and quality:** • Color-coded fields: green = exact/profile, light-green = today's date, yellow = fuzzy, orange = AI, purple = conflict • Confidence summary bar with per-category counts before you fill • Per-section confidence gap messages (contractor vs project sections) • CSV quality scoring: shows which CSV columns have the most gaps across portals • Anomaly detection: Claude Haiku checks selected rows for data quality issues before filling **Search and navigation:** • Token-based search with column-weighted scoring • NLP project search (Claude Haiku): type "Henderson solar job in Nashua" to find the right row • Custom row names and saved-row memory **Compatibility dashboard:** • Per-portal field detection latency and fill coverage history • Hosted viewer detection: DocuSign, OpenForms, Accela, and 20+ more — clear notice instead of spinner • Compatibility notes per domain, plus a watchlist for portals under investigation **AutoFill Vision:** • Click the gear menu → "AutoFill Vision" to open an in-page annotation overlay • Every detected form field gets a color-coded chip showing the matched column and proposed value • Click any chip to open a correction popover: swap to alternative columns or skip a field • Section banners show type classification (Contractor / Project / Owner / Neutral) with override controls **Onboarding and feedback:** • Guided first-run flow with demo data button • Feedback button sends typed messages to the admin dashboard • AI-degraded notice when API is unavailable — graceful fallback to non-AI matching **Requirements:** A running AutoFill Portal backend server (open-source Flask/Python, free to deploy on Railway). See the project README for setup instructions. --- ## Category `Productivity` ## Additional Category `Developer Tools` ## Language `English` --- ## Permission Justifications ### `activeTab` Required for `chrome.tabs.captureVisibleTab()` — used to take a screenshot of the current form page and send it to the backend's vision parsing endpoint (Claude Sonnet) for field section extraction. Without `activeTab`, the screenshot cannot be captured. ### `storage` Required for `chrome.storage.local` (contractor profile, preferences, saved row names, anonymous user ID, multi-profile data) and `chrome.storage.session` (page fields cache, edit history, self-learning signals, background preload cache, fill-success state). Storage is entirely local — no sync storage is used. ### `tabs` Required for three distinct functions: 1. `chrome.tabs.query({ active: true, currentWindow: true })` — identifies the current page URL so the popup knows which portal it is on and can load the correct cached fields. 2. `chrome.tabs.sendMessage(tabId, msg)` — sends fill commands and queries to the content script running on the permit portal page. 3. `chrome.tabs.captureVisibleTab()` — screenshot for vision form parsing (see `activeTab`). ### `scripting` Required for `chrome.scripting.executeScript()` — used exclusively to synchronize third-party rich-text editors (TinyMCE, CKEditor) with filled values when those editors are embedded in permit portal pages. The background service worker calls `executeScript` with `world: 'MAIN'` to invoke the editor's native `setContent()` API, which is only accessible in the page's main JavaScript world. This is the MV3-approved alternative to direct script element injection. Only fires when a TinyMCE or CKEditor iframe is detected in the form. ### `<all_urls>` (content_scripts matches) The extension must run on any government permit portal, utility portal, building department site, or online application form. Permit portals are operated by thousands of city, county, and state agencies across the United States and cannot be enumerated in advance. The extension's core value — reading form fields and filling them with project data — requires the content script to be present on whatever domain the user navigates to. Without broad host matching, the extension cannot function on any portal that was not pre-listed by the developer. No data is collected from pages where the user does not interact with the extension. The content script is lightweight (field extraction only) and does not monitor browsing behavior, read page content outside form elements, or transmit any page data unless the user clicks "Apply All" or opens the popup. ### Host permissions (`localhost:5000`, `127.0.0.1:5000`, `*.railway.app`) These are the only domains the extension makes fetch() requests to — your AutoFill Portal backend server. The extension never fetches from any third-party URL. The Railway host permission covers the shared production backend deployment. The localhost permissions cover local development only. --- ## Screenshots (required — capture from live use) Recommended screenshots (1280×800 or 640×400): 1. Main view — match stats bar showing exact/fuzzy/AI/learned counts with row selected 2. Review view — field checklist with pill-colored match types and "learned" teal badges visible 3. On-page fill — permit form with fields highlighted in green/light-green/yellow/orange 4. My Info profile screen — contractor profile entry with all fields 5. Alt panel — on-page dropdown showing My Info vs Project Data vs Owner/Client options 6. PDF Filler — upload zone with "Drop a PDF here" prompt and Choose PDF button 7. PDF Filler filled — PDF rendered with matched fields highlighted in green (matched) and yellow (unmatched) 8. Compatibility dashboard — per-portal detection latency and fill coverage history ## Promotional Tile (440×280 px, optional but recommended) Dark slate background, white "AutoFill Portal" title, cat icon top-right, tagline "Fill permit forms from your spreadsheet", three colored pill badges (green "Exact", yellow "Fuzzy", teal "Learned"). --- ## Privacy Practices (required during submission) | Practice | Answer | |--------------------------------|--------| | Handles user data | Yes | | Collects personal info | No (only what user voluntarily enters in My Info; stays in browser) | | Uses data for AI | Yes (optional; field names + CSV row sent to Claude API — no PII from My Info) | | Sells data to third parties | No | | Uses data for advertising | No | | Shares data with third parties | No (Anthropic and Railway are infrastructure providers, not data buyers) | Link to privacy policy: `https://autofillportal.com/privacy` --- ## Submission Checklist - [x] Privacy policy live at https://autofillportal.com/privacy (returns 200, no auth required) - [ ] Terms of use hosted at a live public URL (optional but recommended) - [ ] All screenshots captured at 1280×800 or 640×400 - [ ] Extension tested in Chrome with the production Railway backend - [ ] Visibility set to **Unlisted** on first submission (switch to Public after review) - [x] Justifications written for `activeTab`, `storage`, `tabs`, `scripting`, and `<all_urls>` host permissions - [x] Single-purpose description added (field: "Fill government permit forms from project CSV spreadsheet") - [x] config.js in zip has empty AUTOFILL_API_KEY — built via build_extension.ps1 - [x] Version is 1.5.8 in manifest.json - [x] homepage_url set to https://autofillportal.com in manifest.json (returns 200) - [x] background.js included in zip (fill-success service worker) - [x] pdfhandler.js included in zip (local file:// PDF support) - [x] build_extension.ps1 used to generate zip (never use Compress-Archive directly) - [x] Privacy policy text accurately describes scripting permission (§134 — session 68 fix)