Privacy Policy

Effective date: 16 April 2026

Settle is designed to do as little with your data as possible. Most of what the app does happens on your phone and never leaves it. This policy explains, in plain English, exactly what is collected, who sees it, and why.

1. Who we are

Settle is published by Chris Jackson, an individual sole developer based in England, United Kingdom. For the purposes of UK GDPR, Chris Jackson is the data controller.

Contact: settle@cyber-jack.uk

2. Data stored on your device

Your recipes and plans live on your phone in local storage. This includes:

• Recipes you have imported (title, ingredients, instructions, source URL, image URL, FODMAP flags)
• Weekly plans you have built (which recipe is assigned to which day)
• The FODMAP database used to flag ingredients
• A small log of import timestamps so the free-tier 3-per-week cap can be enforced locally
• App settings, including your Pro entitlement flag (cached from the store)

None of this is transmitted anywhere unless you choose to join or host a household (see below). Uninstalling Settle deletes the local database and all of this data.

3. Data sent off your device

Recipe URL fetches

When you paste a recipe URL into Settle, your phone fetches that URL directly from the site that hosts the recipe (BBC Good Food, NYT Cooking, whichever blog, etc.) so that Settle can read the page’s structured recipe data. We do not proxy or log these fetches. The recipe site sees a normal browser request from your phone with a generic user-agent header; we do not send any identifier or your IP to a Settle-controlled server during this fetch.

For safety, Settle blocks fetches to local-network and loopback addresses (e.g. 127.0.0.1, 192.168.x.x) so a malicious URL cannot make the app probe your home network.

Lawful basis: performance of a contract (UK GDPR Article 6(1)(b)) - you have asked us to read the recipe URL you provided.

Optional household sharing (Supabase)

If you create a household or join one, the following data is sent to and stored on Supabase, which hosts the realtime sync backend:

• Household ID and the join code
• An anonymous Supabase user ID (no email, no name)
• Recipes shared with the household (title, ingredients, instructions, source URL, FODMAP flags)
• Weekly plans shared with the household (which recipe is assigned to which day)

This data is visible to other members of your household so you can plan meals together. It is not shared with anyone else, is not used for advertising, and is not sold. Supabase acts as a data processor on our behalf.

Lawful basis: performance of a contract (UK GDPR Article 6(1)(b)) - you have asked us to sync your data with your household.

If you leave a household or delete it from the host device, your contribution to the household data can be removed on request by emailing us. Uninstalling the app also stops any further data being sent.

One-tap shopping export to ListLedger

When you tap “Send to ListLedger”, Settle hands the aggregated ingredient list to ListLedger via a local deeplink on the same device (settle:// scheme). Nothing is sent off your phone during this step - it is purely an inter-app handoff between two apps you have installed.

Pro purchases (Apple App Store / Google Play Billing)

If you buy Pro, the purchase is handled by the Apple App Store (on iOS) or Google Play Billing (on Android). Settle does not see or store your payment details - we only receive a signal from Apple or Google that your purchase succeeded. Your purchase is tied to whichever store account made it. The relevant store’s own privacy policy applies to the billing transaction.

4. Data we don’t collect or use

Settle does not use any of the following:

• Advertising SDKs or ad networks
• Analytics SDKs (no Firebase Analytics, no Mixpanel, no Google Analytics inside the app)
• Advertising IDs (Google Advertising ID is never read)
• Location data (neither GPS nor approximate)
• Contacts, SMS, call logs, microphone, or calendar
• Third-party crash reporting SDKs that send stack traces off-device

5. Website analytics

This website (settle.cyber-jack.uk) uses Google Analytics 4 (measurement ID G-F1XNJSPNDP) to count anonymous page views and geography. GA4 drops its standard cookies when you visit. The app itself does not use Google Analytics.

6. Children

Settle is not directed at children under 13 and we do not knowingly collect data from under-13s.

7. How long we keep data

Local data is kept on your device until you delete it or uninstall the app. Household data on Supabase is kept for as long as the household exists. Deleting a household on the host device removes its data from Supabase. Leaving a household removes your future edits from it.

8. Your rights

Under UK GDPR you have the right to:

• Access the data we hold about you - all of your data lives on your device. For household data on Supabase, email us.
• Erase your data - Settings → Clear all data wipes everything locally. Uninstalling the app does the same. Leave or delete the household for server data, or email us.
• Object to processing, restrict processing, or withdraw consent for household sharing - leave the household.
• Complain to a supervisory authority. In the UK that’s the Information Commissioner’s Office: ico.org.uk.

9. FODMAP database attribution

Settle’s FODMAP flagging uses a database derived from the Monash University Low FODMAP Diet research, refined over time with corrections. We do not redistribute the underlying Monash data; we flag ingredients against a public-domain mapping of food names to FODMAP categories. For authoritative, portion-aware FODMAP guidance, consult the official Monash University FODMAP app and the published research.

10. Changes to this policy

If this policy changes we’ll update the effective date at the top of the page and, where the change is significant, surface a notice in the app the next time you open it.

11. Contact

Questions, requests, or complaints about this policy or your data: settle@cyber-jack.uk.