Privacy notice: pilotless.nl
This notice takes effect on the date of publication: 23 October 2026.
This notice explains what personal data pilotless.nl and the Pilotless GitHub App collect, why, and what you can do about it.
1. Who we are
Pilotless is run by Kadima Technology, a sole proprietorship (eenmanszaak) owned by Jacobus Meulen, Van den Boetzelaarstraat 42, 6081 BT Haelen, Netherlands. KvK 80033105, VAT ID NL003387340B46. Kadima Technology is the controller of the personal data in this notice, except where section 2 says we act as a processor.
Questions or requests: jacobus@kadima-tech.com.
2. What we collect, why, and on what basis
Pilot form. The form on the home page asks for your email address and, optionally, your team size (1–5, 6–15, 16–30, 31+). We store your email address, team size, the time you applied and the src source label (see pl_src below). Nobody is notified automatically. We use it only to follow up with you about the pilot.
Lawful basis: taking steps you asked for before entering into a contract (GDPR art. 6(1)(b)). You can delete your application at any time at pilotless.nl/forget, which deletes it immediately, or by emailing us.
Waitlist (older sign-ups). We used to run a waitlist. If you joined it, we hold your email address, your team size, the src source label (see pl_src below), your free-text answer, the time of your first and your most recent sign-up, and how many times you submitted the form. Nothing links it to your visits. We keep it for 12 months after your most recent sign-up, or until you delete it at pilotless.nl/forget, whichever comes first. You can delete it any time at pilotless.nl/forget.
Lawful basis: your consent (art. 6(1)(a)).
Visit records (pl_vid cookie). The pl_vid cookie holds a random ID. When you visit, we store a short record with:
that ID
the page path
the
srcsource labelthe host name of the referring site (not the full address)
whether it is your first visit or a returning one
a flag for whether the visit came from a bot or a browser
a timestamp
We do not store your IP address or your browser's full user agent in these records, and we never link them to an email address. For each ID we also keep a visitor record (when it was first seen, its first src and path, and whether the visit was confirmed). Visit and visitor records are deleted after 90 days by our weekly purge, which runs on Mondays. We also keep daily aggregate counters (visits per source label, App events per type) with no visitor ID, login, email or repository. We use them only to count visitors and see which pages and links bring people in. They are never shared and never used for advertising. See section 4.
Lawful basis: our legitimate interest in knowing how many people visit and which links bring them (art. 6(1)(f)).
Where you came from (pl_src cookie). When you arrive on any page through one of our links that carries a src value (for example ?src=landing), we store that value in a first-party cookie named pl_src. If you arrive without one, we set it from the referring site's host name instead, as a label such as the site's name or referral. Each new arrival like this resets the cookie. We save this source label with visit records, pilot applications and App installs, so we can count which sources lead to visits, sign-ups and installs. It holds only the label, nothing about you. It is never shared or used for advertising. See section 4.
Lawful basis: legitimate interest (art. 6(1)(f)).
Server and CDN logs. Our hosting (Google Cloud Run) logs each request: your IP address, the URL, your browser's user agent and the referring page. These logs are kept for 30 days. Our application does not log requests, email addresses or account details. If the server hits an unexpected error, our hosting provider's error logs may contain technical details such as an IP address and an error trace; these logs are kept for 30 days. Google Cloud also keeps admin-activity and system audit logs for 400 days, a period Google sets and we can't shorten; these record actions by our own accounts and service accounts on the infrastructure, not site visitors. Our CDN (Bunny) keeps no request logs for our site. It still passes each request through, so it handles your IP address in transit. We use these logs only to run the site, find faults and stop abuse.
Lawful basis: legitimate interest in a working, secure site (art. 6(1)(f)).
The Pilotless GitHub App. If you install the App, you choose the repositories on GitHub's install screen. The App asks GitHub for:
write access to issues
read access to pull requests, contents and metadata
notifications of pull request, issue, issue comment and push events
Once a week it reads recent commits, pull requests and issues and writes one digest issue per repository. The digest lists stalled pull requests and unassigned issues, plus a per-person line of merged work. We do not store your code or the digest text.
We do store:
the GitHub account the App is installed on, and its type (user or organisation)
the GitHub login of the person who installed it
which repositories are selected, and their names
the
srcsource labelinstallation status and timestamps
references to the digest issues
roadmap items: the organisation login, a title and summary written by the editor (up to 4,000 characters), an optional owner login, the login of whoever last updated the item, links, and a derived status
for each issue or pull request linked to a roadmap item, a snapshot of its state, last-updated time, merged flag and assignee logins, including items in private repositories the installation can see
daily counts of events
We don't store issue or pull request bodies, comments, GitHub titles, labels or milestones.
For the account the App is installed on, its type, and the installer's GitHub login, we are the controller. We use them to run and support the installation and to contact you about it. Lawful basis: to provide the service you installed (art. 6(1)(b)). Where you install for an organisation, our legitimate interest in running that installation (art. 6(1)(f)).
You can uninstall the App at any time from your GitHub settings. A weekly scheduled purge deletes the stored installation data 30 days after you uninstall. The digest issue stays in your repository as ordinary text.
For the repository data we process on your behalf, a data processing agreement (DPA) is available on request, and we sign it with any installing customer who asks: https://pilotless.nl/dpa.
GitHub handles in the digest. The per-person line shows GitHub handles. The digest is posted only inside the installing customer's own repository, and the handles in it are already visible there to the same people. For this data we act as a processor on the customer's behalf; the customer, as controller, decides the lawful basis. We don't show GitHub handles anywhere public except in our own repositories.
3. How long we keep it
| Data | Kept for |
|---|---|
| Pilot applications (email, team size, time, src) | 12 months, or until you withdraw (pilotless.nl/forget or email us) |
| Waitlist sign-ups (email, team size, src, free text, first and most recent sign-up time, submit count) | 12 months after your most recent sign-up, or until you delete it at pilotless.nl/forget, whichever comes first |
| pl_vid cookie in your browser | 90 days from when it was first set; not renewed on later visits |
| pl_src cookie in your browser | 90 days; reset each time you arrive through one of our links with a src value, or from another site |
| Visit records and visitor records | 90 days (weekly purge, Mondays) |
| Daily aggregate counters (visits per source label, App events per type) | No visitor ID, login, email or repository; not personal data |
| Google Cloud Run request logs | 30 days |
| Google Cloud admin-activity and system audit logs (actions by our own accounts and service accounts, not site visitors) | 400 days, set by Google; we can't shorten it |
| Bunny CDN logs | None: Bunny keeps no request logs for our site |
| GitHub App installation data | While installed; deleted 30 days after uninstall (weekly scheduled purge) |
| Backups | Copies are kept for 7 days |
Deleted data can remain in our backups for up to 7 days before it is overwritten. You can ask us to delete your waitlist or pilot data at any time at pilotless.nl/forget.
4. Cookies
We set two cookies, both first-party, and no others. They are used only for counting visitors and where they came from. They are never linked to an email address, never shared with third parties and never used for advertising.
| Name | Purpose | Lifetime | First-party |
|---|---|---|---|
| pl_vid | Holds a random ID (UUID) so we count each visitor once (visit records, section 2) | 90 days; not renewed on later visits | Yes |
| pl_src | Remembers where you came from, for source counts: the src value of the link you arrived through (e.g. landing), or otherwise a label from the referring site's host name | 90 days; reset each time you arrive through one of our links with a src value, or from another site | Yes |
Technical attributes: pl_vid is HttpOnly, Secure and SameSite=Lax. pl_src is Secure and SameSite=Lax, and not HttpOnly.
Under the Dutch Telecommunicatiewet (art. 11.7a), cookies used only for analytics with little or no impact on your privacy don't need your consent, as long as we tell you about them. Ours are that kind, so we don't show a cookie banner.
You can delete or block these cookies in your browser at any time. The site works without them.
5. Who else handles your data
We use these service providers (processors) to run Pilotless:
Google Cloud hosts our server (Cloud Run, europe-west1 region, Belgium) and our database (Firestore, location: EU (Google Cloud multi-region eur3, Belgium and the Netherlands)). It also keeps our request logs.
Bunny CDN (BunnyWay d.o.o., Ljubljana, Slovenia) delivers our web pages and passes GitHub App traffic through, from servers in the EU. It handles your IP address and requests as they pass through.
GitHub is not our processor or sub-processor. It is a platform you already use; your use of it is covered by your own agreement with GitHub and GitHub's privacy statement.
We store this data in the EU. Our server runs in Google Cloud's europe-west1 region (Belgium), and our database location is EU (Google Cloud multi-region eur3, Belgium and the Netherlands). Our CDN is run by BunnyWay d.o.o., an EU company based in Slovenia, and serves our site only from EU locations.
Where Google's US entities can access data, we rely on the Google Cloud Data Processing Addendum, which includes the EU Standard Contractual Clauses, and on Google's certification under the EU-US Data Privacy Framework.
6. What we don't do
No third-party trackers, analytics scripts or advertising pixels.
We don't sell your data, and we don't share it for anyone else's marketing.
We don't make automated decisions about you that have legal or similarly significant effects.
7. Your rights
Under the GDPR you can ask us to:
show you the data we hold about you (access)
correct it
delete it
limit how we use it
give it to you in a portable format
stop using it where we rely on legitimate interest (objection)
stop using it where we rely on consent (withdrawal, which does not affect earlier use)
Email jacobus@kadima-tech.com. We reply within one month. To delete a waitlist or pilot email address straight away, use pilotless.nl/forget.
8. Complaints
If you think we handle your data wrongly, tell us first and we will try to fix it. You also have the right to complain to the Dutch data protection authority, the Autoriteit Persoonsgegevens: https://autoriteitpersoonsgegevens.nl
9. Changes
If we change this notice, we update the effective date at the top. If a change matters, we will say so on the site.