Legal

Privacy

Closed beta. Version of 19 November 2026. Filings is in a closed beta, by invitation. In the beta you sign in with Google only, no payment is taken and we do not yet measure use with PostHog: what this notice says about email links, payments and PostHog holds from the day each is switched on, which we announce by email.

1. Who is responsible

Filings, an initiative of Pascal Batelaan, in the Netherlands, is the controller for the personal data described here. Questions and requests: filingsdata@gmail.com or Support. The company name, the address and the Chamber of Commerce number are added here when the company is registered, before the beta ends.

2. What we keep about you

  • Your account: your email address, how you signed in (Google or an email link), your plan and the date the account was made. When you sign in with Google we get your email address from Google and nothing else.
  • Your keys: only a hash of each API key and of each connector token, the first characters of a key so you can tell your keys apart, and a label if you gave one. We cannot read a key back.
  • Your address on the network: when an account is made we keep a hash of the IP address, to count new accounts per address. We do not keep the address itself with your account. Our hosting provider keeps ordinary access logs for a short time.
  • Your use: per call the time, your account, which key, which tool, how many credits it cost and whether it came through MCP or REST; and totals per day and per month. This is what the credits and the invoices are based on.
  • Payments, once you pay: your plan, your spending limit and the references Stripe gives us for your customer record, invoices and payments. Card details stay with Stripe.

3. What we do not keep

We do not keep the content of your questions or of the answers. A call is counted, not recorded.

There is one exception, and it holds a company name only: when a company name you typed could not be matched to one employer, we log that name as typed (at most 120 characters), the date, what the outcome was, how many candidates we offered, whether it came through MCP or REST, and a short hash that stands for your account (not your address or your key). We use this log to improve the matching of company names. Each line is deleted after 90 days. Do not type personal data in a company-name field.

4. Why, and on what ground

  • To give you the service, count your credits and send invoices: to carry out our agreement with you.
  • To keep the free credits fair and the service safe (limits per account, per email domain and per IP address, and signals when accounts that belong together empty their credits): our legitimate interest in preventing misuse.
  • To improve the matching of company names, and to measure how the service is used in totals: our legitimate interest in a service that works.
  • To keep invoices and payment records: a legal duty.

5. Measuring use

Not in the beta; from the day it is switched on: our server sends events to PostHog when an account is made, when a call is made and when a limit is reached: the event, your account id, the tool, the credits and how long the call took. No question, no answer and no company name is sent. We set no tracking cookies for this and the pages load no analytics script.

Cookies. We set one cookie when you sign in on the site: it keeps you signed in for 30 days and holds a signed reference to your account, nothing else. The sign-in and connect pages set a short-lived cookie that protects the form. There are no advertising or tracking cookies.

6. Who gets data

We do not sell personal data. These processors work for us now: Fly.io (hosting, in the United States), and Google when you sign in with Google. From the day each is switched on, and named here before that day: Stripe (payments), PostHog (measuring use) and a mail provider (sign-in links and messages about payments). Where data goes outside the European Economic Area this is covered by the EU standard contractual clauses or an adequacy decision.

7. How long

  • Account and keys: until you close the account, then deleted within 30 days.
  • Use per call and the totals per day: 13 months. Totals per month: as long as the account exists.
  • Log of unmatched company names: 90 days.
  • Invoices and payment records: 7 years, as Dutch tax law asks.

Copies in backups. What we delete can stay for a time in two kinds of copies, which we use only to restore the service after a failure. So what we delete is gone from every copy after at most 35 days:

  • the backup we make on the disk at each release: the copies of the account data, the keys and the tokens are removed from a backup when it is 30 days old;
  • the snapshot our hosting provider makes of the whole disk every day: each snapshot is kept for 5 days.

8. The public data

The disclosure rows are public records of the U.S. Department of Labor. They are about employers and positions. We do not expose names of attorneys or contact persons from those files, nor phone numbers or email addresses.

9. Your rights

You can ask us to show, correct or delete your data, to limit its use, or to hand it to you in a common format, and you can object to use on the ground of our legitimate interest. Write through Support; we answer within one month. You can also complain to the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).

10. Keys

A key belongs in the configuration of your MCP client or in an environment variable, not in a prompt or a public chat.