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: 11 August 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. Specifically:
- We do not record your IP address and we do not store the full page address or where you came from. We record only which page pattern you viewed.
- 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.
- On the marketing site only, 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". This documentation site issues no identifier at all — page views here are counted and never linked to each other or to you.
- If you arrived from a campaign link, the campaign source, medium and name. Nothing else from the address is read.
Because we write nothing to your device and cannot identify you from this, there is no cookie banner to click.
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.
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, and where people get stuck. This is counting, not profiling: we do not build a picture of you as an individual, and we do not use any of it for advertising.
- 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
| Who | What for | Where |
|---|---|---|
| PostHog | Product analytics (the counting described above) | United States |
| Amazon Web Services | Hosting the application and its database | United States |
If you are in the UK or EEA, your data is transferred to the United States. We say so plainly rather than burying it: both 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.
- Marketing-site 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.
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.