Privacy

Last updated 2026-08-07

This notice covers the Recipeli website at recipeli.com and the Recipeli mobile app for iOS and Android. They do not collect the same things — the website counts pageviews and nothing else, while the app also records how it is used and reports its own crashes — so they are described separately below.

The short version

The website

What you give us

Nothing. The website is a set of static pages: no accounts, no forms, no comments, no shopping basket. There is nothing for us to ask you for and nowhere for us to put it.

Analytics

We count pageviews with PostHog, running in its cookieless mode on European servers (eu.i.posthog.com). The analytics library itself is loaded from PostHog's CDN, which is the one thing on the site not served from recipeli.com.

Cookieless mode means visitors are counted without storing anything on your device: PostHog derives a daily figure server-side from a salted hash of your IP address, browser user-agent and the site's hostname, and the salt is thrown away and replaced every day. A visitor who returns tomorrow is counted as a new one, and we cannot work backwards from the hash to you. Your IP address is discarded before any location lookup happens, so we do not know which country you read from.

Session recording, surveys, heatmaps and automatic click tracking are all switched off. A pageview — which page, in which language — is the whole of it.

Cookies and local storage

The site sets no cookies and uses no local storage, session storage or similar. Nothing is written to your browser by us or by PostHog.

Server logs

Our hosting provider records ordinary web-server logs, which include your IP address, the page requested, and your browser's user-agent string. These keep the site running and let us spot abuse. We do not combine them with anything else or use them to identify you.

The mobile app

What stays on your device

The app keeps your choices locally, on the phone, and never sends them to us: the language you picked, the ingredients you have selected, how you prefer recipes sorted, your light or dark theme preference, and the date you finished the intro screens. It also keeps a copy of the recipe and ingredient data it has downloaded so the app works offline and does not refetch what it already has. Deleting the app deletes all of it.

What the app asks our server for

The app reads recipes, ingredients and icons from our API. Those are read-only requests — the app never writes anything back, because there is no account and nothing of yours to store. The requests carry the ordinary things any network request carries, such as your IP address, and nothing we have added to identify you.

Analytics and session replay

The app uses PostHog for product analytics, on the same European servers as the website — but unlike the website, the app has session replay switched on. That records what happens on screen as you use the app, so we can see where it is confusing or broken.

Two things about those recordings are worth stating plainly. Text you type is not masked, so what you type into the ingredient search appears in the recording; and images shown on screen are not masked either. The recordings also include the app's own diagnostic logs and basic timing information about its network requests.

Alongside the recordings, PostHog receives the usual technical properties: your device model, operating system version, app version, language and time zone, and a randomly generated identifier for the installation. Because the app has no accounts, that identifier is not attached to a name, an email address or anything else that identifies you personally, and it is reset if you reinstall the app.

Crash reports

When the app crashes or hits an error, it sends a report toSentry on its European servers (ingest.de.sentry.io). A report contains the error and the stack trace, the device model, the operating system version, the app version — and your IP address, which the app is currently configured to include.

App updates

The app checks Expo's update service (u.expo.dev) for over-the-air updates. That request tells the service the platform and the app version it is asking on behalf of, so it can answer with the right update or with nothing.

What the app never asks for

The app requests no access to your location, camera, microphone, contacts, photos, calendar or health data, and sends no push notifications. It contains no advertising, reads no advertising identifier, and does not track you across other companies' apps or websites.

Who else sees any of this

Only the services named above: PostHog for analytics, Sentry for crash reports, Expo for app updates, and the companies that host the website and the API. Each is used for the one purpose described here. We do not sell data, trade it, or hand it to anyone for their own purposes. Both PostHog and Sentry are configured to use their European regions, so analytics and crash data stay in the EU.

How long it is kept

What the app stores on your phone stays there until you delete the app. Server logs are kept by our hosting provider on its own rolling schedule. Analytics events, session replays and crash reports are deleted by PostHog and Sentry at the end of the retention period configured in each service.

Your rights

If you are in the UK or the EU, data-protection law gives you the right to ask what we hold about you, to have it corrected or deleted, to object to or restrict how it is used, and to complain to your national supervisory authority.

In practice there is very little to ask for: with no accounts, we hold nothing filed under your name, and the analytics identifier is the only thread connecting one app session to another. If you want the data from your installation deleted, get in touch and say roughly when you used the app, and we will remove what can be located.

Children

Neither the website nor the app is aimed at children, and neither asks anyone for the kind of information that would identify a child — or any person — by name.

Changes

If we add a service, switch one on, or start collecting something new, this page is updated in the same change that does it, and the date at the top moves. It is not a page we revise after the fact.

Contact

Questions about this page, or a request about your data: [email protected]