Overview
A form filler sees sensitive data by definition: passports, addresses, client records. FillWise is built around one rule: process, fill, forget. Your input is used to complete the form in front of you and is not kept afterwards.
This page says exactly what leaves your browser, where it goes, what is stored and for how long. If your compliance team needs it in writing, a data processing agreement is available on request.
What leaves your browser during a fill
| Sent | Not sent |
|---|---|
| The text you paste and the files you attach for this fill | Your browsing history, cookies, other tabs |
| The form itself: field labels, types and options | Values already typed into the page by you |
| For fillable PDFs: the list of fields, never the file | Passwords or anything from your password manager |
| For flat PDFs: page images, so the layout can be read | The finished PDF: it is assembled in your browser |
Every request travels over encrypted HTTPS.
Where it is processed
Your request goes to our server and from there to the AI provider, Anthropic (Claude), which reads the text or the document and matches it to the form. The answer comes back through our server to the extension, which writes the values into the fields. Neither the input nor the answer is written to our database.
Under Anthropic's commercial API terms, customer data is not used to train their models.
What FillWise keeps
| Data | Why | For how long |
|---|---|---|
| Account: name and email from Google, or the email you sign in with | To know whose account it is | Until you delete the account |
| Plan and payment status | Billing. Cards are handled by Stripe; we never see them | While the subscription exists |
| Templates you save: text and an optional attachment | You chose to reuse them | Until you delete them |
| Per-fill usage record: date, website domain, number of fields, whether a fill was spent | Billing and quality statistics | Kept as billing history; no field values inside |
| Form maps: which field of a known form takes which kind of data | So a known form fills again without AI | Shared structure, no values |
| Input patterns: the shape of how you write your data, for example "name, surname, email" | So your pasted text is recognised next time | The shape only, never the values |
| Corrections: which fields you edited after a fill | To improve fills on that form | Field names only, never the values |
What FillWise never keeps
The pasted text, the attached photos and PDFs, the page images of flat PDFs, and the answers the AI returned. Once the form is filled, they are gone from our side.
Bulk fill works the same way. Your client spreadsheet is read in your browser and never uploaded as a file: each client's details are sent only to fill that client's documents and are not stored. The filled documents of a batch stay in your own browser for 24 hours so you can download or review them, then they are deleted; you can clear them earlier with one click.
Subprocessors
| Company | Role |
|---|---|
| Anthropic | AI processing of text and documents |
| DigitalOcean | Hosting of our server and database |
| Stripe | Payments and subscriptions |
| Sign-in with a Google account | |
| Resend | Sending one-time sign-in codes by email |
Your controls
- Delete any template from the extension or the account page at any time.
- Revoke the extension's access from your Google account settings at any moment.
- Ask for account deletion, a full data deletion or a data processing agreement at hello@fillwise.ai.
Use Cases
| Who | Why it matters |
|---|---|
| Travel & visa agencies | Client passports are read once for the fill, not copied to a third-party server |
| Legal and immigration teams | Confidential client details used only for the form at hand; a DPA on request |
| Insurance and licensing services | Hundreds of applications a month without a growing pile of stored personal data |
| Privacy-conscious users | Convenience without a stored profile of personal data |