Privacy Policy

2.1 Data You Provide Directly

When you use FormAI, you may voluntarily provide the following personal information by entering it into the Extension's Data tab or by importing it from a resume PDF:

• Full Name
• Email Address
• Phone Number
• Location (city/state/country — typed by you, not derived from device GPS)
• LinkedIn Profile URL
• Work Experience (job titles, company names, dates, descriptions)
• Education (schools, degrees, dates)
• Skills (comma-separated list)
• Additional Information (free-form text)

You choose what to enter. All fields are optional. You can delete all data at any time using the "Reset" function.

2.2 API Keys (Authentication Credentials)

If you choose a cloud-based AI provider (OpenAI or Google Gemini), you provide your own API key. This key is:

• Encrypted using AES-256-GCM via the Web Crypto API before storage
• Encrypted with a unique 256-bit key generated at installation time
• Encrypted with a random 12-byte initialization vector (IV) per encryption operation
• Stored only in chrome.storage.local (browser-local, not synced)
• Decrypted only at the moment of an API call, then immediately discarded from memory
• Never logged, never displayed in plain text in the UI, and never transmitted to any party other than the AI provider you configured

If you choose WebLLM (Local AI) or Ollama, no API key is needed.

2.3 Form Fill History

When you use the "Fill This Page" feature, the Extension records:

• The domain name (e.g., "boards.greenhouse.io")
• The full page URL
• The timestamp
• The number of form fields detected
• The number of fields successfully filled

This is stored locally (last 50 entries) so you can see where you've previously used FormAI. No fill history is transmitted externally.

2.4 Form Field Labels (Transient — Not Stored)

When you click "Fill This Page," the Extension reads form field labels from the current page (e.g., "First Name," "Email Address," "Years of Experience"). These labels are:

• Processed in memory to match against your saved data
• Sent to your configured AI provider (if using a cloud provider) as part of the form-filling prompt
• Not stored persistently — they exist only during the active fill operation

2.5 Resume PDF Text (Transient — Not Stored)

When you use "Import from Resume," the Extension extracts text from your uploaded PDF file using the pdf.js library running locally in your browser. The extracted text is:

• Processed locally to extract structured fields (name, email, phone via regex; experience, education, skills via AI)
• Sent to your configured AI provider for parsing (if using a cloud provider)
• Not stored after parsing is complete — only the extracted structured fields are saved to your profile

2.6 Data We Do NOT Collect

FormAI does NOT collect:

• Browsing history or web history
• Keystrokes, mouse movements, scroll activity, or clicks (outside the explicit picker mode)
• Device geolocation (GPS, IP-based location, etc.)
• Health information
• Financial or payment information
• Personal communications (emails, messages, chats)
• Cookies or tracking identifiers
• Device fingerprints or hardware identifiers
• Network traffic or monitoring data
• Screenshots or page content (other than form field labels)
• Any data when the Extension is not actively being used by you

4.1 Local Storage Only

All user data is stored exclusively within your browser using:

• chrome.storage.local: Your personal information, encrypted API key, provider settings, fill history
• chrome.storage.sync: Theme preference (dark/light) and onboarding completion flag only — synced across your Chrome profile
• IndexedDB (via EntityDB library): Vector embeddings of your profile data for semantic search during form filling. The embedding model (Xenova/all-MiniLM-L6-v2) runs locally in your browser

4.2 No External Servers

4.3 Encryption

API keys are encrypted before storage using:

• Algorithm: AES-256-GCM (authenticated encryption)
• Key derivation: A 256-bit random key generated via crypto.getRandomValues() at Extension installation, stored in chrome.storage.local
• IV: A fresh random 12-byte IV is generated for each encryption operation
• Implementation: The Web Crypto API (crypto.subtle), which is the browser's native cryptographic library

5.1 Cloud AI Providers (User-Configured)

If you choose to use a cloud-based AI provider, the following data is sent to that provider's API when you initiate a form fill or cover letter generation:

5.2 Model Weight Downloads

• WebLLM: The Gemma 2 2B model weights (~1.5 GB) are downloaded from Hugging Face's CDN (huggingface.co) the first time you activate local AI. This is a one-time download of model data files, cached in your browser. No personal data is sent to Hugging Face during this download.
• Embedding model: The all-MiniLM-L6-v2 ONNX model is downloaded from Hugging Face via the transformers.js library. Same as above — no personal data is transmitted.

5.3 No Other Third Parties

FormAI does NOT share data with:

• Advertising networks or platforms
• Data brokers or information resellers
• Analytics services (no Google Analytics, no Mixpanel, no telemetry)
• Social media platforms
• The extension developer or any affiliated entity
• Any other third party not listed above

6.1 Retention

Your data persists in local browser storage for as long as the Extension is installed. There is no time-based expiration. Fill history is automatically trimmed to the most recent 50 entries.

6.2 Deletion

You can delete your data at any time through:

1. Reset button in the Extension's Data tab: Deletes all personal information and fill history from chrome.storage.local and clears the IndexedDB vector database
2. Uninstalling the Extension: Chrome automatically removes all data in chrome.storage.local, chrome.storage.sync, and IndexedDB associated with the Extension
3. Browser data clearing: Using Chrome's "Clear browsing data" → "Cookies and other site data" will clear IndexedDB. Storage data can be cleared via Developer Tools → Application → Storage

6.3 Export and Import

FormAI includes a data export feature that downloads a JSON file containing your profile data, fill history, and settings. This file is saved to your local device. You can import this file to restore your data (e.g., after reinstalling or on a new device). The export file does not include your API key for security reasons.