Privacy Policy
Who we are
FilliQ fills in business forms: you upload a form, FilliQ reads it, fills what it knows from details you have saved, asks for the rest, and gives you back the completed document. FilliQ is software made and distributed by Aventuri Holdings Pte. Ltd. (Singapore, UEN 202601804G). Aventuri Holdings Pte. Ltd. is the organisation responsible for the account data FilliQ holds about you (your sign-in, your organisation and its billing), and it handles the data an organisation puts into FilliQ on that organisation's behalf, as its data intermediary.
Questions about this policy, or requests about your data: support@filliq.co.
Where a business (your "organisation") puts its own or its clients' details into FilliQ, the organisation decides what goes in and how long it stays, and FilliQ handles that data on its behalf and only to fill that organisation's forms. If you are a client who filled in a form from an intake link, the organisation that sent it is the one to ask first; we will help them answer you.
What FilliQ holds
- Your account: the email address you sign in with and the name you give.
- Your organisation: its name, its members and their roles, its plan and the usage counted against it.
- Profiles: the details you or your team save so forms can be filled from them (company and personal details, which can include identity numbers, passport numbers and bank details).
- Forms: the blank forms you upload and train, the completed forms, and the answers given while filling.
- Intake: what a client types or attaches on an intake link you send them, such as an identity-document scan.
- Signatures: when a form is signed in FilliQ, the signature picture, the name typed with it, the signer's email address when signing on a client link, the time, and the IP address and browser details of the device that signed, kept as the audit trail of that signing. The audit trail holds no form answers.
- Access records: who opened, filled, exported or changed a form, and when. This record holds no field values, by design. An organization's owners and admins on the Business plan can download it as a CSV, and each download is itself recorded (who, and the date range).
- API keys and assistant connections: a key's secret is shown once and only a one-way hash of it is stored.
- Billing: handled by Stripe. FilliQ stores which plan you are on and Stripe's identifiers for your subscription, never a card number.
How AI is used with your data
To read a form and fill it, FilliQ sends the form's pages (as images or text) and the saved details or answers needed to fill it to Anthropic's API, and uses what comes back. When you train a form and ask for key suggestions, FilliQ also sends Anthropic the labels printed on the form's fields and the labels next to them, the names of your saved keys, the words you have told FilliQ mean a key, and your workspace's rule phrases. That request never contains a value: not a profile's details, not a fill's answers. Those are the only uses of your data by an AI model.
- We do not train models on your data, and we do not use one customer's data to improve another's. Anthropic's commercial terms, under which we use its API, do not allow it to train on inputs or outputs.
- We do not combine data across organisations, build a database of identities, or analyse your data for any purpose other than filling your forms.
- Anthropic may keep API inputs and outputs for a limited time under its own policies, for example to detect abuse. See Anthropic's documentation for its current terms.
- An Enterprise organisation can give FilliQ its own Anthropic API key. While one is set, that organisation's requests to Anthropic are made with its key, so Anthropic handles them under the organisation's own agreement with Anthropic and not under FilliQ's account. FilliQ's servers still send the same content and receive the answer, and do not fall back to FilliQ's key if the organisation's is refused. The key is kept encrypted, is used only for that organisation, and is never shown again, even to its owner. How Anthropic treats data under an organisation's own agreement is between the two of them and is not described here. Without a key of its own, an organisation's requests go through FilliQ's account as described above.
- FilliQ never submits a form to anyone on your behalf, and never fills a signature, a witness or a certification field. A person does those.
Connecting an AI assistant
An owner or admin can let an assistant such as Claude or ChatGPT use FilliQ, with an API key or by signing in and approving the connection. The assistant acts as that person, for their organisation, and can only do what the connection allows: fill forms and make the completed PDF. It cannot read the organisation's members or its access records, change billing or settings, or sign or submit anything.
What FilliQ sends the assistant is the names of forms and fields, the questions still to be answered, and a link to the completed PDF that works for five minutes. If you ask the assistant to read your profile back, or it reads one to check a detail with you, the details in that profile (your name, address, company details and the like) are sent to the assistant, and so pass to the company that provides it. FilliQ records each such read (which profile, and whether through a connection or a key; never what it held). ID, passport, tax, licence, card and account numbers are sent only masked (first character and last four), the assistant is never given one in full to carry or save, and you type those in FilliQ. What the assistant's provider does with what it receives is governed by that provider's terms and policy, not ours. Every form an assistant fills counts against your plan like one filled in the browser.
How it is protected
- Everything travels over HTTPS.
- Each organisation's data is separated in the database by row-level security: a signed-in person can only read rows their organisation, team and role allow, and the rules are enforced by the database itself, not only by the application.
- Identity numbers, passport numbers, bank and card-like values are encrypted a second time before they are stored (AES-256-GCM), with a key derived separately for each organisation from a secret that is not kept in the database. A copy of the database alone does not reveal them.
- Uploaded forms, scans and completed documents are kept in private storage and are reached only through short-lived signed links.
- The keys that unlock the database and the AI are held on the server and are never sent to a browser.
- FilliQ does not currently hold a security certification such as SOC 2 or ISO 27001, and does not claim one. Our providers (below) publish their own. The Security page (/security) describes what is built in more detail.
How long it is kept, and how it is deleted
Retention is set by the organisation, in its settings, and a client on an intake link is shown the period before they type anything. A retention job removes what is due, deletes the stored files as well as the rows, and checks afterwards that both are gone.
| What | Default | The organisation can |
|---|---|---|
| Answers given while filling, and the uploaded form they were filled from | 30 days | set any period from 1 day to 10 years |
| A client's supporting documents (intake attachments) | With the answers: 30 days | follow the answers' period |
| The completed form | Kept until the organisation deletes it | keep it, delete it once delivered, or delete it after a number of days |
| Remembered client details, so a returning client's next form is prefilled | Off. Nothing is remembered unless the organisation turns it on | turn it on, with a period of its own |
| Signatures: the signature pictures and a sealed copy of a signed form | With the uploaded form: 30 days | follow the uploaded form's period |
| The record of each signing (who, when, IP address, browser details, email) and the fingerprint of a sealed form | For the life of the fill: kept as the audit trail, and deleted with the fill | delete the fill |
| A trained form's blank, kept so the form can be filled again without uploading it | Until the form is deleted | delete the form, which removes the blank |
A legal hold placed by an organisation keeps what it covers past these dates, and the retention job reports what it held rather than skipping it silently.
Deleted data can remain for a while in our database provider's encrypted backups until those roll off in the provider's normal cycle. It is not restored into the service.
Deleting your account or someone's data
- You can delete your own account in the app when you are the only person in your organisation. The organisation goes with it, with everything in it: profiles, forms, fills, answers, stored files and API keys, and its subscription is cancelled first.
- In an organisation with other people, an owner or admin removes a member, and can delete that member's account if it belongs to no other organisation.
- Anyone can ask us to delete or correct data we hold about them by writing to the address above; if it is held for an organisation we will pass the request to them.
- Stripe keeps the payment records the law requires it to keep.
Who else handles data for us
These companies process data on our behalf. We use no advertising or analytics service, and sell no data.
An AI assistant you connect to FilliQ (Claude, ChatGPT or another) is not one of them: it is yours, and you choose it. When it reads one of your profiles, those details pass to the company that provides it, under that company's terms and not ours.
| Provider | What it does for FilliQ | What it receives |
|---|---|---|
| Supabase | Database, sign-in, and private file storage | Everything stored in FilliQ (identity values encrypted as described above) |
| Anthropic | The AI that reads forms and fills them | A form's pages and the details needed to fill it, while it is being filled. While a form is trained and key suggestions are asked for: the field labels, the names of your saved keys, your aliases and rule phrases, never a value. For an Enterprise organisation that has set its own Anthropic key, the same requests are made with that key, under its own agreement with Anthropic |
| Stripe | Payments and subscriptions | Your email address and billing details you give Stripe; never form data |
| Resend | Sending email: sign-in codes for clients on intake links, and a welcome email | The recipient's email address and the message |
| Render | Hosting the FilliQ application | Requests to the application, in transit |
Your rights
You can ask what we hold about you, ask us to correct it, and ask us to delete it, and you can withdraw consent to the processing that depends on it. Write to the address above. We handle personal data in line with Singapore's Personal Data Protection Act; where another law gives you rights, tell us which and we will deal with the request under it.
Changes to this policy
If we change how data is handled in a way that matters to you, we will say so in the app or by email before it takes effect, and the date at the top of this page will change.
How it is protected: Security. Questions: support@filliq.co