Privacy
Last updated 26 October 2026. Factline (factline.dev) is the controller for the data below. Contact: hello@factline.dev.
In short. No accounts are needed, there are no tracking or advertising cookies, and we never sell data. We use what you send to answer that request. A few things are kept for a short, stated time; the table below lists each one.
What we collect, why, and for how long
| Data | Why | How long |
|---|---|---|
| Tool and API inputs: a company name or number, VAT, EORI or IBAN number, a person's name (and optional birth year) for sanctions and PEP screening, a crypto wallet, an email address, phone number or domain, a Dutch address, postcode or licence plate, or an x402 seller URL | To run the check you asked for | Not stored as such. Some answers are cached under the input so a repeat is fast: company lookups and reports 7 days, VAT and insolvency answers 1 day, Dutch address and vehicle data 1 to 30 days, email domains (not addresses) 7 days. Person names and wallets sent for screening are not cached. |
| Tool and API outputs | Returned to you; a signed receipt for paid answers | Receipts keep a hash of the answer, the route, the time and the payer (wallet or key id), not the input or the answer itself, for 7 years (bookkeeping). |
| Request counts per endpoint and per AI client name (for example claude-ai, cursor) | Usage statistics and capacity | Kept as daily totals, no IP address. |
| A hashed IP address (one-way, truncated) | Counting the 5 free paid checks a day per client | 2 days |
| IP address and request data at our host | Delivering the service, security and rate limits (Cloudflare) | Under Cloudflare's own retention |
| Page views (cookieless Cloudflare Web Analytics: page, referrer, country, browser) | Knowing which pages are used | Aggregated by Cloudflare; no cookies, no cross-site tracking |
| API key holders: name, email, company and use case you enter, and usage per month | Issuing the key, quota, service emails (welcome, usage, monthly screening log) | While the key exists; deleted on request |
| Watches: the names, companies or plates you watch, your email or webhook, and alert history | Re-checking them and telling you when something changes | Until you stop the watch (link in every email) or it expires |
| Client files (Wwft/AMLR): the company and check results you save, your decisions | Your own audit trail | Until you delete them; you control this through your key |
| Supplier onboarding links: details a supplier enters (company, country, company number, VAT, IBAN, contact name and email) | Checking the supplier for the buyer who sent the link | 12 months; unused links 60 days |
| Bidding logs for estate agents: bidder name, email, phone, company and bids | The agent's transparent bidding record | Kept with the sale for the agent; the public hash chain holds bidder numbers only |
| Emails you send us (hello@, support@, check@) and our replies | Answering you | Kept for the conversation; deleted on request |
| Invoices sent to check@factline.dev | Checking the supplier and replying | The invoice is read and discarded. We keep a count per sender per month and, per supplier, a fingerprint of the last bank account (hash and last four characters) to warn you when it changes |
| x402 payments: transaction hash, paying wallet, amount, country of the request | Bookkeeping and statements | 7 years (Dutch tax law) |
| x402 seller claims: domain, wallet, dates, optional email and webhook | Seller alerts | Until revoked |
AI assistants (ChatGPT, Claude and other MCP clients)
When an assistant uses Factline, we receive only the tool name and the arguments it sends (the inputs listed above), plus the client's name. We do not receive your conversation, your name or your account details. The answer goes back to the assistant; OpenAI's, Anthropic's or the client's own privacy policy covers what happens in the conversation. If you give the assistant your work email for a trial key (the get_trial_key tool), we store that email as an API key holder.
Who receives data
- Official sources, only with the input needed for that check: company registers (GLEIF, Companies House, CRO, KBO and other national registers), the EU VIES and EORI services, the Dutch insolvency register, Peppol directories, Dutch government open data (Kadaster/PDOK, CBS, RDW, RCE, KOOP). Sanctions and PEP screening runs on our own copy of the public lists; names are not sent anywhere.
- Service providers: Cloudflare (hosting, database, analytics), Resend (sending email), Google (our mailbox), Dodo Payments (merchant of record for card and iDEAL payments; we receive the status and what was bought, not your card details), Coinbase and other x402 facilitators (settling USDC payments on Base or Solana).
- No one else. We do not sell or rent data and do not use it for advertising.
PEP data
To answer PEP screening we keep an extract of public Wikidata data on politically exposed persons in their public role: name, birth year and public positions held in the last 10 years. Our legitimate interest is helping businesses meet anti-money-laundering duties. To have an entry corrected or removed, email hello@factline.dev.
Your controls
- Access, correction or deletion: email hello@factline.dev; we answer within 30 days, within legal retention limits (payment records).
- Every service email has an unsubscribe link; every watch email has a stop link.
- API key holders can delete client files and stop watches through the API at any time.
- You can object to processing based on legitimate interest, and complain to the Dutch data protection authority (Autoriteit Persoonsgegevens).
Insolvency data: we query the Centraal Insolventieregister only for companies; cases about private persons are discarded and never stored.
Contact. hello@factline.dev