Privacy notice

What Landfall collects, why, who else sees it, and how to make us delete it. Written to describe what the product actually does today, not what we intend it to do.

Last updated: 6 October 2026

Who we are

Landfall is an incident-response platform operated by Landfall. For anything in this notice, including a request to see or delete your data, write to jhonny@landfalls.ai. A person answers; there is no ticket system to navigate.

What we collect

When you use the product

To give you an account and a war room, we store:

• Your email address and display name. Email is how you sign in and how we reach you.
• Which organizations you belong to, and your role in each.
• What you and your team put into an incident: messages, findings, uploaded files, and the timeline of what happened. This is the product working as intended, and it is your content. It can include whatever you choose to paste in, so treat it as you would any shared workspace.

When you visit our public websites

This covers the marketing site and this documentation site. Deliberately very little, and nothing is written to your device: no cookies, no local storage, no session storage. Specifically:

• Our analytics code does not add your IP address to what it sends. Your browser sends the events to PostHog directly, and like any server your browser contacts, PostHog sees your IP address as part of that request. We do not store the full address of the page you are on or of the page you came from. We record which page you viewed. On the marketing site, if you followed a link from another site, we record that site's name, such as linkedin.com, but never the page.
• There is no session recording and no heatmapping. We do not replay your visit.
• Nothing is collected automatically. Only a short, explicit list of events (a page view, a section scrolled into view, a button clicked) is sent. Each one also carries what any browser tells a website it visits: the browser and operating system, the kind of device, the screen and window size, the language and the time zone.
• A random identifier for that visit only, held in memory and gone when you close the tab. It lets us tell "one person looked at three sections" from "three people looked at one each". On the marketing site, if you go on to create an account in that same visit, the identifier is linked to your account's pseudonym (see below), so we can count how many visits become accounts. On this documentation site it is never linked to anything: not to an account, and not to you.
• If you arrived from a campaign link, we record its campaign tags: source, medium, name, content and term. Each is a short code such as reddit or paid_social, and anything else is discarded. We do not keep the rest of the address or any ad click ID.
• No advertising platform receives anything from these sites. There is no advertising pixel or tag on them, and nothing we record is passed to an advertiser.

Because we write nothing to your device, there is no cookie banner to click.

When you create an account

If you create your account in the same visit as a campaign link, the campaign tags from that link (source, medium, name, content and term) are stored with your account. We use them to count which campaigns lead to accounts and organizations, and they go with the pseudonymous events for your sign-up and for creating your organization. They are never sent to an advertising platform, and nothing else from the link is kept. Until you register, the sign-up page holds them in memory only, the same as the public websites.

When you are signed in

Product analytics identify you by a one-way pseudonym derived from your account id, not by your email or name. It cannot be reversed to identify you, and the analytics provider never receives your email address. These events do not include the address of the page you are on.

Why we collect it

• To run the product you asked for: accounts, organizations, incidents.
• To see whether it works. How many people who look at the site go on to create an account, which campaigns bring them, and where people get stuck. This is counting, not profiling: we do not build a picture of you as an individual, and nothing we collect is given to an advertising platform.
• To keep it secure and available, including logs of errors and access.

We do not sell your data. We do not share it with advertisers.

Who else processes it

If you are in the UK or EEA, your data is transferred to the United States. We say so plainly rather than burying it: all three providers above operate in the US, so using Landfall means that transfer happens. We rely on the providers' standard contractual protections for it.

How long we keep it

• Your account and your organization's incidents: for as long as the account exists. Incident timelines are deliberately append-only, because an incident record you can quietly rewrite is not worth having. Deleting your account removes your personal details from it.
• Analytics events: retained under the provider's standard retention. They are not tied to your name or email.
• Campaign tags stored with an account: for as long as the account exists.
• Public-website visit data: the visit identifier is discarded when you close the tab.

Your rights

You can ask us to show you what we hold about you, correct it, delete it, or send you a copy. Write to jhonny@landfalls.ai. That includes the campaign tags stored with your account: if you object to them being kept, tell us and we remove them.

We answer within 5 working days, and complete the request within 30 days. If you are in the UK or EEA you also have the right to complain to your data protection authority.

Changes

If we change what we collect, we change this page in the same release, and the date at the top moves. We will not quietly widen collection and update the notice later.