Privacy Policy
Last updated: November 13, 2026
Netli.fyi ("we," "our," or "us") is a third-party client for Netlify, built with privacy as a first principle. This policy explains exactly what the app does with your data. The short version:
- We don't track you across other apps or websites. No advertising, no ad identifiers, no device fingerprinting, no data brokers.
- We do measure how the app itself is used, so we can fix what breaks and see which features are worth the effort. That means anonymous usage events, crash reports and startup timings — described in detail in §3.5, §3.6 and §3.7. You choose when you first open the app, and can change it any time in Settings → Privacy → Share usage data.
- We don't sell, rent, or trade your data. Ever.
- Your Netlify data stays between your device and Netlify. We run a small backend only for the features that genuinely require one (push notifications and feedback), and it stores as little as possible. Your project names, site contents, build logs and environment variables are never sent to our analytics or error-reporting providers.
- We never store your Netlify access token on our servers. It is used in-memory to talk to Netlify on your behalf and is discarded.
1. Information Stored on Your Device
Most of what the app knows lives only on your device:
- Authentication token (your Netlify personal access token or OAuth token), stored in the iOS Keychain / Android Keystore via Expo SecureStore, or the macOS Keychain on a Mac (§1.1).
- Account name and Netlify user identifier, used to label and scope your session.
- Cached Netlify data (sites, builds, deploys, domains, forms, etc.), stored in an encrypted local cache so the app is fast and works offline. The encryption key is held in secure storage.
- App preferences (theme, notification choices, whether you've opted out of usage data) and local usage counters used to decide when to show an optional "rate the app" prompt. The counters themselves stay on your device; §2.5 covers the one number that doesn't.
Signing out clears this local data, including the data shared with the app's widgets and extensions.
1.1 Netli.fyi for Mac and signing in from your iPhone
The Mac app is a menu-bar companion to the iPhone app and handles data the same way, with these differences:
- Its token is stored in the Mac's own Keychain, on that Mac only. "Sign Out of This Mac" removes it, along with the Mac's cached account details.
- Signing in from your iPhone. If you turn on Sign in on my Mac automatically in the iPhone app (on by default for new sign-ins), the iPhone app saves a copy of your selected account (the Netlify token, your Netlify user ID and account name) as an item in your iCloud Keychain. iCloud Keychain is end-to-end encrypted by Apple and syncs only between your own devices; the item is never sent to us. The Mac app reads it once to sign in and then keeps its own copy. Turning the setting off, or signing out on the iPhone, deletes the synced item. Signing out on the Mac signs out only that Mac.
- Handoff. When you look at a project or deploy, the app tells your other devices (through Apple's Handoff) which one it is: its Netlify ID, name and deploy ID. This goes between your own devices through Apple and never reaches us.
- No product analytics. The Mac app doesn't use PostHog. It sends crash and error reports to Sentry as described in §3.6, and you can turn them off in Settings → Account → Share crash reports.
- Notifications reach the Mac the same way as the iPhone (§2.2): the Mac's push token is kept in RevenueCat next to your iPhone's, so watching a project on either device notifies both.
2. Our Backend (Push Notifications & Feedback)
Some features can't work purely on-device. For those, the app talks to a small backend we operate (a Cloudflare Worker). Here is everything it does and stores:
2.1 Your Netlify access token is used, never stored
When the app calls our backend, it sends your Netlify token so the backend can (a) confirm which Netlify user you are and (b) create or delete deploy/form webhooks on your own Netlify sites on your behalf. The token is held only in memory for the duration of the request (briefly cached for a few minutes to reduce repeated calls) and is never written to our database.
2.2 Push notification subscriptions
If you enable notifications for a site, we store, keyed to your Netlify user ID:
- the site's ID and name,
- which notification types you enabled,
- references to the webhooks we created on Netlify for you, and
- a per-user secret used to verify that incoming webhooks are genuinely from Netlify.
When Netlify tells us one of your builds or form submissions changed, we send you a push notification. Notification delivery uses Apple Push Notification service (APNs) on iOS and Firebase Cloud Messaging (FCM) on Android — the standard OS push infrastructure. Your device's push token is managed through RevenueCat (see §3) so we can reach the right device.
2.3 Notification history, preferences and Live Activities
To send the free weekly overview ("3 deploys, 1 failed, 5 form entries this week") and to check that notifications are actually delivered, our backend keeps a short log of the notification events it handled for you: the site ID, whether it was a deploy or a form entry, the deploy's state, and the time. It does not store build logs, commit messages, form contents or site contents. This log is deleted automatically after 90 days.
We also store your notification preferences (which events you want, the weekly overview and offer switches) and your chosen app language, keyed to your Netlify user ID, so notifications arrive the way you set them up and in your language.
If you use live deploy progress — a Live Activity on iOS, or a progress notification on Android — we store the device token Apple or Google gives us for it, keyed to your Netlify user ID, so the progress can be updated while a build runs. It is removed when you turn the feature off or sign out.
2.4 Feedback
If you send feedback from within the app, we receive your message, your app version and platform, your Netlify user ID, and — only if you choose to include it — a reply-to email address. That address is prefilled from your Netlify account for convenience, but you can edit or remove it before sending, and we only receive what you leave in the field. Feedback is stored so we can act on it and is forwarded to our support inbox via Resend (an email delivery provider) so we can reply to you.
2.5 Rating prompt statistics
When the app asks you to rate it (the card on the Projects screen, the screen after What's New, or the system rating sheet), it tells our backend which of those it showed and whether you opened the App Store from it. Each record has the step, the time, your platform and app version, the rating-prompt score from §1 at that moment, and your Netlify user ID. We use it to see whether the prompt is shown too often or too rarely, and delete it after 90 days. If you share usage data (§3), the same steps, without your rating or review, are also sent to PostHog as usage events. It never includes your rating or review, which go to Apple and which we never see.
3. Third-Party Services
3.1 Netlify
The app connects to the Netlify API (https://api.netlify.com) to read and manage your account data. Your use of Netlify is also governed by Netlify's Privacy Policy.
3.2 RevenueCat
We use RevenueCat to manage subscriptions and in-app purchases, and to hold your device push token so notifications can be delivered. RevenueCat receives your Netlify user ID (as an app-scoped identifier), purchase/subscription status, and push token. On iPhone and iPad, if you share usage data, RevenueCat also receives Apple's AdServices attribution token, which tells us whether you installed the app from one of our own Apple Search Ads campaigns and which one. It comes from Apple, contains no advertising identifier, and isn't combined with data from other companies. See RevenueCat's Privacy Policy.
3.3 Apple / Google push, and Resend
- APNs (Apple) and FCM (Google) deliver push notifications to your device.
- Resend delivers your feedback message to our support inbox, and only when you send feedback.
3.4 Lookups the app makes from your device
A few things the app shows are fetched directly from your device, not through our backend, and we receive nothing from them:
- Favicons. Site icons — and, for form submissions, the icon of the sender's email domain (for example
gmail.com) — are loaded from Google's public favicon service, which receives the domain name. - Sender logos. For form submissions, the app checks whether the sender's email domain publishes a brand logo for mail clients (BIMI) by asking Cloudflare's public DNS resolver (
cloudflare-dns.com). Only the domain is sent, never the email address. - Link previews. Share-image and page-title previews are read from your own site's public page.
- Avatars. Commit authors' avatars are loaded from GitHub (
github.com/<username>.png).
3.5 PostHog (product analytics)
We use PostHog, hosted in the European Union, to understand how the app is used — which screens people reach, which features get used, where a flow is abandoned.
What we send:
- Named events for things you do in the app: finishing onboarding, creating a project, triggering a build, retrying a deploy, opening the subscription screen, and so on. The full list lives in
src/lib/analytics.tsin the app's source. - Screen names, with any identifiers removed —
/domains/:domain, never your actual domain. - Taps on deploy and form alerts: which kind of alert, which button, and whether the deploy started, succeeded or failed — never the project, branch or message.
- Which widgets you've placed, at most once a day: how many, and their kinds and sizes — never which project they show.
- Device and app context: platform, OS version, app version, device model, locale, timezone.
- Your Netlify user ID and account slug, once you sign in, so repeat sessions from the same account can be recognised.
- Your Netli.fyi Advanced status: whether you're on the free plan, a trial, a renewing or cancelled subscription, or lifetime, and when you buy, which plan and from which screen. Never payment details, which stay with Apple or Google.
What we deliberately do not send:
- No email address or name. Analytics never receives them.
- No session recording or screen capture. It is switched off, because this app displays access tokens, environment variable values and build logs.
- No location. IP-based location lookup is disabled, so no city or region is derived or stored.
- No Netlify content. No project names, URLs, repository names, branch names, environment variable keys or values, form submissions or build logs.
- No credentials. Every outgoing event passes through a filter that strips anything shaped like an access token.
Before you sign in, events are anonymous and no profile is created for you.
3.6 Sentry (crash and error reporting)
We use Sentry, hosted in the European Union, to find out when the app crashes or throws an error, and why.
What we send: the error and its stack trace, the app version and build, device and OS version, a trail of recent in-app actions leading up to the failure, and your Netlify user ID so we can tell whether a bug hit one person or many.
Sentry's option to attach IP addresses, cookies and personal details is switched off, session replay is not enabled, and the same credential filter applies to error messages and breadcrumbs.
3.7 Expo Observe (performance and error measurement)
We use Expo Observe, hosted in the United States, to measure how long the iPhone, iPad and Android apps take to start and to move between screens, and which errors happen along the way, so a release that got slower or less stable is caught.
What we send: the timings themselves, the screen they belong to as a route pattern (for example /project, never which project), the app version and build, device model and OS version, country, language, network type, low-power and thermal state, the internet hostname of the slowest network request made while the app was starting, and a random ID generated for this install. When the app throws an error it didn't handle, the error message and its stack trace are sent too, and a native crash report is sent the next time the app opens.
That install ID is not your Netlify user ID and is not linked to it, and it resets if you reinstall the app. Everything that follows a screen in its address — project and deploy IDs, names, hostnames, URLs, email addresses — is removed on the device before anything is sent. The Mac app does not use Expo Observe.
3.8 Turning it off
Settings → Privacy → Share usage data stops PostHog, Sentry and Expo Observe. Usage events and timings stop immediately; native crash reporting stops the next time you open the app. On a Mac, Settings → Account → Share crash reports stops Sentry the next time Netli.fyi starts.
4. What We Collect, in App Store terms
For transparency, the categories of data linked to you are:
- Contact info — a reply-to email, only if you include it in feedback. App functionality.
- Identifiers — your Netlify user ID, your device push token, and an app-generated anonymous ID used before you sign in. App functionality and analytics.
- Purchases — subscription status, via RevenueCat. App functionality.
- Usage data — product interaction: which screens and features you use, and which rating prompts you saw (§2.5). Analytics.
- Diagnostics — crash logs, performance data and other diagnostic data. App functionality.
The Mac app collects nothing beyond these categories, and the account it copies from your iPhone through iCloud Keychain (§1.1) is never sent to us, so these labels cover both apps.
None of it is used for tracking as Apple defines it: nothing is linked with data from other companies' apps or websites for advertising or measurement, no advertising identifier is collected, and nothing is shared with data brokers.
5. Data Security
- Authentication tokens are stored in the device's secure keystore; the local data cache is encrypted at rest.
- All network communication uses HTTPS.
- We do not store your Netlify password; authentication uses tokens only.
6. Your Rights and Choices
- Notifications: turn any site's notifications on or off at any time in the app; disabling them removes the corresponding webhooks and stops delivery.
- Usage data and crash reports: turn them off in Settings → Privacy → Share usage data. The app works exactly the same either way.
- Feedback email: leave the reply-to field blank and we'll have no way to email you.
- Local data: sign out to clear everything stored on your device.
- Your Netlify account data: manage or delete it directly in Netlify. Deleting your Netlify account stops the app from accessing it.
7. Data Retention
- Your access token is never retained by our backend.
- Notification subscriptions and preferences are retained until you disable them or sign out.
- The notification event log (§2.3) is deleted after 90 days.
- Feedback is retained until we've acted on it.
- Rating prompt statistics (§2.5) are deleted after 90 days.
- Usage events and crash reports are retained on our providers' standard schedules — PostHog for up to 12 months, Sentry and Expo Observe for up to 90 days — and are deleted automatically after that.
- On-device data is retained until you sign out or clear the app.
8. Children's Privacy
The app is not intended for users under 13, and we do not knowingly collect information from children under 13.
9. International Users
Our backend runs on Cloudflare's global network. Analytics and error reporting are hosted in the European Union (PostHog EU Cloud and Sentry's EU region). Our other providers (Netlify, RevenueCat, Expo, Apple, Google, Resend) may process data in the United States and elsewhere. By using the app you consent to this processing.
10. Changes to This Policy
We may update this policy from time to time and will revise the "Last Updated" date above. Continued use after a change constitutes acceptance.
11. Contact
Questions about this policy? Contact us at perttu@lahteenlahti.com or via netli.fyi.
Note: Netli.fyi is an independent, third-party client and is not affiliated with or endorsed by Netlify. Your use of Netlify's services is also subject to Netlify's Terms of Service and Privacy Policy.