Who we are and what this covers
Infinitic AI Ltd. (“Infinitic”, “we”) operates FormAgent: a local-first browser form automation product. This policy covers:
- the Infinitic FormAgent Chrome extension
- the local FormAgent runtime, CLI, and product shell on your computer
- this FormAgent private beta website
- sign-in and credits metering when you use Infinitic’s customer services
FormAgent’s single purpose is human-supervised form workflow control: map source data to web forms, fill and submit with local approval, and keep the assigned browser workspace in sync.
Chrome extension
The extension is a bridge between your browser and the FormAgent runtime running on your machine. It does not call Infinitic cloud APIs and does not load remote JavaScript or Wasm.
Permissions
- alarms — periodically retry pairing and reconnect to the local runtime if the connection drops
- nativeMessaging — obtain a pairing token from the installed local native host (
com.infinitic.formagent) - scripting — inject the packaged content script into the assigned workspace tab when needed
- sidePanel — show the FormAgent side panel for local connection and workspace status
- storage — store local-only pairing and UI state
- tabs — open, focus, update, and monitor the assigned workspace tab
- host access — operate on the https/http pages you choose as form targets (not a general crawl of the web)
What is stored in the browser
Only in chrome.storage.local on your device:
- a pairing token used to authenticate to the local runtime
- UI and workspace status (for example assigned tab id, URL, title, and workflow status labels)
Form field values are not written to extension storage.
What is read from web pages
On the assigned workspace page, the extension can read form structure (labels, types, options, and related metadata), page title and URL, and a short visible-text excerpt with input values removed. Page scans do not export existing field values. Password and file inputs are ignored for fill; submission is blocked when password fields are in scope. Fill values are supplied by your local runtime over a loopback connection, not fetched from Infinitic servers.
Local connections only
The extension connects to ws://127.0.0.1:17331 / ws://localhost:17331 and to the local native messaging host. It does not include analytics or third-party tracking SDKs. All scripts are packaged with the extension (script-src 'self'); we do not use remote code.
Local runtime and source data
Source files (CSV, spreadsheets, JSON, and similar), record values, durable task state, fill and submit execution, and human approvals stay on your computer. Audit reports are written locally with restricted file permissions.
The Chrome extension and runtime talk over loopback interfaces. Record values are not uploaded by the extension.
What may leave your device
When you use FormAgent model features (for example advisory mapping help, recovery guidance, or agent tooling), privacy-minimized metadata may be sent through the Infinitic AI Gateway to the configured model provider. That path is intended to include structural information such as:
- source column names (not cell values)
- form field labels, types, and similar structure
- privacy-preserving value shapes (kind and length bucket), not raw record contents
- task or status metadata
- sanitized page URLs (origin and path; query fragments are masked for model context)
- short visible page-text excerpts and recovery categories when those tools are used
Model requests are made with provider retention disabled where FormAgent controls the call (store: false). Your raw spreadsheet or source record values are not included in those tool results.
If you do not use model features, that off-device metadata path is not required for basic local operation of the extension bridge.
Authentication and credits
Product sign-in may use Google or GitHub OAuth. A local session on your machine may store identifiers such as user id, email, and provider. Credits metering tracks identity and usage against your Infinitic account. That is separate from uploading source records: credits and auth are for access and billing, not for exporting your form data.
This website
The private beta landing page does not run a server-side waitlist. “Request access” opens your email client to hammadbaba96@gmail.com with the address you typed. The rate estimator runs entirely in your browser. Buying credits happens in the customer console, not on this page.
This site loads fonts from Google Fonts. Your browser may contact Google’s servers to fetch those fonts (which can expose your IP address to Google under their terms).
Limited use and what we do not do
- We do not sell or transfer user data to third parties outside approved use cases needed to operate FormAgent.
- We do not use or transfer user data for purposes unrelated to FormAgent’s single purpose above.
- We do not use or transfer user data to determine creditworthiness or for lending.
- FormAgent does not autofill password fields, does not solve CAPTCHAs, and does not execute arbitrary remote JavaScript on web pages.
Retention and your controls
- Extension: uninstall FormAgent or clear the extension’s site data / storage in Chrome to remove local pairing and UI state.
- Local product data: FormAgent stores runtime and session artifacts on your machine (for example under a FormAgent data directory). Delete those local files or uninstall the product to remove them.
- Beta email: messages you send to hammadbaba96@gmail.com are handled as ordinary correspondence for access and support.
- Account: for account or credits questions, contact us at the address below.
Contact and changes
Questions about this policy: hammadbaba96@gmail.com.
We may update this page as FormAgent evolves. The “Last updated” date at the top will change when we do. Continued use of the extension or related services after an update means you should review the revised policy.