Privacy Policy

Summary

Flick is a self-hosted tool. We (the extension developers) do not collect, store, or sell any user data. All data moves directly between your browser and the server you configure yourself.

Data handled by the extension

• Document images you capture or upload are sent only to the backend server you specify in the settings (for example your-server-address). Images are never sent to us or to third parties.
• Credentials & session tokens are stored in the extension's local storage (chrome.storage) on your device, solely for authenticating against your own server.
• Settings (server address, OCR model choice, per-site selector mappings) are stored locally in your browser.

Permissions requested

• activeTab — temporary access to the active tab when you click the extension icon, used to read/fill forms and pick autofill target elements.
• scripting — injects the element picker and form-filling scripts into tabs you choose.
• storage — stores your login session, preferences, and selector mappings locally.
• sidePanel — displays the extension's main interface as a side panel.

What we do not do

• We do not sell or share data with third parties.
• We use no analytics or tracking.
• We load no remote code (all code is bundled locally).
• We read no browsing activity beyond interactions you initiate.

Data on your server

The Flick server (Go backend + OCR microservice) runs on infrastructure you control. Further data handling — including storing extraction results in PostgreSQL — is subject to your own policies as the server operator.

Contact

Privacy questions can be raised through the issue tracker of this project's repository.