Filler — Chrome Extension

Privacy Policy

What Filler handles, where it goes, and why — in plain terms, before you install it.

Last updated: August 23, 2026

In short

Filler is a Chrome extension that helps you apply to jobs faster: it extracts job posting details from the page you're viewing, drafts a tailored cover letter using your own OpenAI API key, and autofills that information plus your saved profile into application forms.

This policy explains what data the extension handles, where it goes, and why.

What data the extension handles

DataWhat it isWhere it's stored
Profile information Name, email, phone, address, city, postal code, LinkedIn, GitHub, personal website, expected salary — fields you fill in yourself Locally (chrome.storage.local), synced to your own Google Drive appDataFolder
Résumé / CV The PDF, Word (.docx) or LaTeX project (.zip / .tex) you upload, plus, for a LaTeX CV, its compiled PDF, plus text extracted from it locally, and the {{placeholder}} settings you define for adapting it per job posting Locally, synced to your own Google Drive appDataFolder
OpenAI API key The key you paste in during setup Locally only (chrome.storage.local) — never transmitted anywhere except directly to api.openai.com as part of your own requests
Google OAuth token Issued by Google when you click "Connect Google" Managed by Chrome's chrome.identity API; used only to call the Google Drive API on your behalf
Job posting content Text/structured data extracted from the job page you're viewing Processed locally; sent to api.openai.com (with your key) only when you generate or extract with AI assistance
Generated cover letters Text drafted from your profile and the job posting Stored locally and in your Google Drive appDataFolder, only when you use the extension
Adapted CVs The PDF of your CV as adapted for a specific job posting (the one you last previewed, attached or downloaded for it), plus the values it was filled with Your Google Drive appDataFolder, next to that posting's application; deleted together with it

Filler's Google Drive access is limited to the drive.appdata OAuth scope — a private, hidden storage area only this extension can read or write, not visible in your regular Drive file list.

Only if you export an adapted Word CV as PDF, Filler asks once for one more narrow scope, drive.file (access only to files Filler itself creates, never to your other Drive files). It uses it to upload that adapted CV as a temporary Google Doc, let Google Docs convert it to PDF, and delete the temporary file immediately afterwards — whether or not the conversion succeeded. If you never export a Word CV as PDF, this scope is never requested.

Who receives data, and why

Filler talks to exactly two external services, both initiated by you and authenticated with your own credentials:

No data is ever sent to a server operated by the developer of this extension — there isn't one.

Permissions

Filler requests the following Chrome permissions, each used only for its stated purpose:

Host permissions are limited to api.openai.com, www.googleapis.com, and latex.ytotech.com — the three services described above.

Data retention and control

Changes to this policy

If this policy changes, the "Last updated" date above will be revised. Material changes will be reflected here before they take effect.

Contact

Questions about this policy can be sent to msk.vitaly@gmail.com.