Privacy policy.

What docRefinery collects, what happens to the documents you send us, and the choices you have. It covers this website, the dashboard, the API and the Chrome extension.

Last updated 4 November 2026

The short version

  • We use your documents to give you the results you asked for. We do not sell your data.
  • Documents are read by our systems and by the AI and document-processing providers we work with.
  • The Chrome extension reads a page only after you turn on Auto-fill and grant access.
  • You can ask us to delete your data at any time.

What we collect

  • Account details. Your name, email address and Google account identifier when you sign in with Google, and your organization and plan.
  • Documents and results. The files you upload, the text and values read from them, and any corrections you make. Documents can contain personal, financial or identity information, depending on what you send.
  • Your setup. Workflows, field definitions, layouts, API keys and saved form mappings.
  • Usage records. Pages processed against your plan, and API request logs.
  • Contact messages. What you send through the contact form, including your name and email address.
  • Analytics. How the website and dashboard are used, as described under Cookies and analytics below.

How we use it

  • To read your documents and return the results to you.
  • To remember your layouts, corrections and form mappings, so later documents in your account go better.
  • To run your account, enforce plan limits and provide support.
  • To keep the service secure and to find and fix problems.
  • To understand how the product is used and improve it, using analytics that exclude document content.

What docRefinery remembers about your layouts, corrections and form mappings stays within your account or organization.

The Chrome extension

The extension fills web forms from documents you choose. Here is what it handles.

  • Sign-in. You sign in with Google. The extension uses this to reach your docRefinery account.
  • Files. A file is sent to docRefinery only when you choose it and press Extract.
  • Page access. Chrome asks for your permission when you turn on Auto-fill. Until then the extension does not read the pages you visit. It works on the tab you have open, and it does not track your browsing. You can withdraw access at any time from Chrome's extension settings.
  • Form details we save. To recognise a form next time, we save its site address, page path, page title and the labels and names of its inputs, along with which field goes where. This is stored in your account, so it follows you to any machine. You can delete a form's saved mapping from the side panel.
  • AI on forms. When AI helps place fields on a form, it receives the form's labels and the names of your fields, not the extracted values. If a date could be read two ways, AI may look at the text of your document to settle it.
  • Filling. Values are written into the form in your browser. The extension never submits a form. You check the page and submit it yourself.
  • Settings. Your Auto-fill switch and chosen workflow are kept in Chrome's own storage.
  • No analytics. The extension contains no analytics or advertising code.

We use the data the extension handles only to provide this feature. We do not sell it, use it for advertising, or use it to decide anyone's creditworthiness. We do not let people read it except with your permission, for security, to meet legal obligations, or to investigate a problem you report.

Who we share it with

We do not sell personal data. We share it only with the service providers that help us run docRefinery:

  • AI and document-processing providers, which read the documents you send on our managed cloud.
  • Cloud hosting and storage providers.
  • Google Firebase, for sign-in and for the website's infrastructure.
  • PostHog and Google Analytics, for product and website analytics.
  • Our email provider, to deliver contact form messages to us.

We may also disclose data when the law requires it, or to protect the service and its users. On a private VPC or air-gapped deployment, documents are read inside your own environment.

How long we keep it

  • Uploaded files are deleted automatically, 7 days after upload by default.
  • Results, corrections, workflows and form mappings stay in your account so you can use them, until they are deleted or your account is closed.
  • API request logs are kept for 90 days.

To have your data or account deleted, email [email protected]. Enterprise customers can agree custom retention terms.

Cookies and analytics

Essential storage keeps you signed in and remembers your theme and cookie choice. Analytics cookies are set only if you accept them. Until then, we count visits without cookies. We never put document content or file names in analytics events, and session recordings in the dashboard mask all text and images.

Security

Data is encrypted in transit and at rest. Each account's data is kept separate from every other account's. No system is perfectly secure, and we will tell affected customers about a breach as the law requires. See security and compliance for our current status.

Where data is processed

Our providers may process data in countries other than your own. We do not currently offer data-residency commitments on the managed cloud.

Your choices and rights

You can ask us for a copy of your personal data, or ask us to correct, delete or restrict it. You can also object to how we use it, and complain to your local data protection authority. Depending on where you live, the law may give you further rights. To use any of these, email [email protected].

If your organization gave you access to docRefinery, it decides what is uploaded and how it is used, and your request may need to go through it.

Children

docRefinery is a business service and is not meant for children.

Changes to this policy

We will update this page when our practices change, and revise the date at the top. If a change is significant, we will tell account holders.

Contact

Questions about privacy go to [email protected].