Privacy policy

• Account information from GitHub sign-in: your GitHub user ID, your GitHub login and, when it is public, your email address. If you start a trial from the CLI, the email address you give.
• Organization, team and billing information. Stripe handles payment card details; we do not store them.
• Support communications.
• Email addresses of people invited to a team.
• An audit log of account and API key changes, with the IP address and browser of the person who made each change.
• Runtime data for customers who use Fallow Cloud. See the Fallow Cloud section.
• Product analytics and error reports from fallow.tools and fallow.cloud. See the product analytics section.
• Function-level JavaScript coverage from this marketing site (fallow.tools) and our dashboard (fallow.cloud). We run our own Fallow Cloud beacon on our own sites. See the section about our own beacon.
• Pseudonymous telemetry from the free Fallow CLI, only when a person turns it on.
• Technical logs needed to operate the service.

The free Fallow CLI can be used without a hosted account. It sends product telemetry only after a person turns it on with fallow telemetry enable. Telemetry is off by default.

Telemetry events describe which workflow ran and how it ended, not your code. When you turn telemetry on, the CLI creates a random install token, so we can count events per installation. The token is not derived from your machine or account, and fallow telemetry disable deletes it. We do not store your IP address with the events. We delete the raw events after 30 days and keep aggregate counts in PostHog. The network activity page lists every request the CLI, the GitHub Action and the beacon make.

When the Fallow GitHub Action asks for a Fallow-branded token, we check the GitHub token of the run and record the repository name in PostHog.

Fallow Cloud is opt-in. When a customer installs the beacon, it sends call counts per function: function names, file paths, line numbers, call counts, the commit, the project id, the environment name, a timestamp and a random ID for each upload. It does not send request data, argument values or return values. The network activity page lists every field.

Customers can also upload source maps and function inventories from their build. A source map can contain the original source code. If a customer links a repository through our GitHub App, we read files from that repository, such as source files and the CODEOWNERS file, to show them in the dashboard.

We run the Fallow Cloud beacon on this marketing site (fallow.tools) and on our dashboard (fallow.cloud). The build adds counters to each function, and the beacon sends the counts to api.fallow.cloud. On fallow.tools the beacon collects coverage from 1 in 10 visitor sessions. On fallow.cloud it collects coverage from every session.

What the beacon sends:

• File paths of our source files.
• Function names and the line where each function starts.
• Per-function hit counts and a called / never-called state.
• Project identifier (fallow-tools or fallow-cloud), environment name, runtime surface, git commit SHA, a random ID for each upload, and an ISO 8601 timestamp.

What the beacon does not send:

• Page URLs, query strings, referrers, or navigation history.
• Page content, form input, or anything you typed.
• Cookies, local storage, session storage, or tracking identifiers.
• Variable values, argument values, return values, heap contents, or stack traces.
• IP addresses. The server sees the address of each request, as any web server does, and the beacon adds none.

The beacon contract and setup instructions are documented at fallow.tools/docs/cloud/beacon. If you prefer to browse our site without the beacon, block requests to api.fallow.cloud at the network layer; the site itself still works.

We use PostHog on its EU cloud for product analytics and error reports on fallow.tools, on fallow.cloud and in our API.

• On fallow.tools, PostHog runs without cookies and stores nothing in your browser. It records page views, clicks and errors under an anonymous ID that changes every day. Session recording is off.
• For requests to the fallow.tools docs that do not come from a browser, such as the docs MCP server, the Markdown pages and the agent files, our server sends PostHog an event with the path, the status and the user agent. The event has no IP address and no stable ID.
• On fallow.cloud, PostHog sets no cookie and stores no ID in your browser. It keeps its state in memory, and a new page load starts a new ID. After you sign in, it links the events of that page load to your user ID, GitHub login, email address, role and organization.
• Session recording on fallow.cloud is off by default. It starts only after you turn it on in the dashboard under Settings, Security, and you can turn it off there at any time. A recording masks every form field, API key, invite link and teammate email. The dashboard keeps your choice in the local storage of your browser.

Signing in to fallow.cloud sets a cookie that keeps you signed in for 7 days. This cookie is needed for the service you ask for. The dashboard serves its own fonts, so your browser does not contact a font service.

• Operate the service.
• Secure the service.
• Provide support.
• Improve reliability and performance.
• Communicate important updates.

Fallow B.V. is the controller for the purposes below, except for Fallow Cloud data. The legal bases refer to article 6(1) of the General Data Protection Regulation (GDPR).

• Account and sign-in. GitHub user ID, login, public email, organization membership and the sign-in cookie. Basis: performance of the contract, article 6(1)(b).
• Billing records. Billing contact, invoices and subscription data, kept through Stripe. Basis: performance of the contract, article 6(1)(b), and our legal obligation to keep financial records for 7 years under Dutch tax law, article 6(1)(c). Stripe also acts as an independent controller for fraud prevention and its own legal duties.
• Product emails. Alerts, invitations and account notices. Basis: performance of the contract, article 6(1)(b). An invitation to a person who has no account yet relies on the legitimate interest of the team that sends it, article 6(1)(f).
• Analytics on fallow.tools. Page views, clicks and errors, without cookies. Basis: our legitimate interest in knowing which pages help visitors, article 6(1)(f).
• Analytics on fallow.cloud. Product events without cookies or stored IDs. Basis: our legitimate interest in improving the dashboard, article 6(1)(f). Session recording runs only with your consent, article 6(1)(a).
• CLI telemetry. Pseudonymous workflow events, only after a person turns telemetry on. Basis: consent, article 6(1)(a). fallow telemetry disable withdraws it.
• Fallow Cloud data. Call counts, source maps and linked repository files that a customer sends. The customer is the controller and Fallow B.V. is the processor. The data processing addendum covers this data.

We keep data only as long as needed for the service and legal obligations.

• We delete each raw coverage upload from storage after we merge it.
• We keep hourly coverage totals for 7 days. After that, only the daily and weekly totals remain.
• We delete raw CLI telemetry events after 30 days.
• We keep billing records for 7 years, as Dutch tax law requires.
• An organization owner can ask us by email to delete the organization once it has no active subscription. This deletes its coverage data, uploads, API keys, members and alert rules. We keep a record of the deletion with the Stripe customer ID for billing.

• Service providers and subprocessors.
• Legal obligations.
• Business transfers.

Fallow Cloud is hosted in the EU: the API and database run in Amsterdam, and stored files and database backups stay in the EU. Some of our vendors store or process data outside the EU. The subprocessor list names each vendor and where it processes data.

Resend sends our email from the EU (Ireland), and stores account data, email metadata and logs in the United States. Where a vendor transfers personal data outside the European Economic Area, the transfer relies on the EU-US Data Privacy Framework or on Standard Contractual Clauses.

You have the right to access, correct or delete your personal data, to restrict or object to its processing, and to receive it in a portable format. Where we rely on your consent, you can withdraw it at any time. To use these rights, email hello@fallow.tools.

You can also complain to the Dutch data protection authority, the Autoriteit Persoonsgegevens, through its complaint page. If you live or work in another EU country, you can complain to the authority there.