Last updated: 11 October 2026

Effective date: 3 October 2026

FlurFit ("we", "us", "our") is operated by FlurFit ("the Company"), based in Lagos, Nigeria. This Privacy Policy explains what personal data we collect, why we collect it, how we use and protect it, and your rights under applicable data-protection laws — including the Nigeria Data Protection Regulation (NDPR), the Nigeria Data Protection Act 2023 (NDPA), the EU General Data Protection Regulation (GDPR) where it applies, and any other relevant legislation.

FlurFit is a calorie-deficit weight-management app for mobile devices (iOS and Android). FlurFit does not provide medical advice. It gives general wellness information based on practical experience with calorie control, portion management and discipline. It does not replace a doctor or registered dietitian.


1. Data controller

FlurFit is the data controller for the purposes of the NDPR/NDPA, and where applicable, the GDPR.

Contact: [email protected]


2. What data we collect

2.1 Data you provide directly

Category Examples Purpose
Body and profile data Name, sex, age, height, current weight, target weight Calculate your personalised calorie budget using the Mifflin–St Jeor equation and plan a safe weight-loss timeline
Health screening responses Whether you are pregnant, have diabetes, high blood pressure, heart/kidney/liver conditions, a history of disordered eating, or take regular medication Determine whether to advise you to consult a doctor before starting. We do not store diagnosis details — only a yes/no flag per condition
Food preferences Favourite meals, snacks, drinks, dietary habits Build your personalised meal plan and power the AI Kitchen feature
Food diary entries Meals logged, quantities, calorie estimates Track daily intake against your calorie budget
Weight history Weigh-in entries with dates Recalculate your budget and show your progress
Activity data Step count — read from Google Health Connect (Android), Apple Core Motion (iOS), or entered manually. Activity level selection. Factor activity into your calorie calculation and maintain your step streak. We read only the Steps data type from Health Connect, read-only — FlurFit never writes to Health Connect.
App preferences Theme choice, reminder settings, weigh-in frequency, step goal Personalise the app experience

2.2 Data collected automatically

Category Details Purpose
Analytics (PostHog) Anonymous or pseudonymous usage events: screens viewed, features used, button taps, session duration, streak retention, logging completion rates, plan adherence. Device type, OS version, app version, screen size. We do not send your name, food diary contents, weight entries or health screening answers to PostHog. Understand how the app is used so we can improve it. Measure feature adoption and retention. PostHog may process data on servers located outside Nigeria; see Section 7.
Error and crash reporting (Sentry) Crash logs, stack traces, device model, OS version, app version, breadcrumb events leading to an error. We strip personally identifiable information (PII) before transmission — Sentry receives no names, emails, food logs or weight data. Detect, diagnose and fix bugs and crashes quickly. Sentry may process data on servers located outside Nigeria; see Section 7.
AI Kitchen requests When you use the AI Kitchen, the dish name and your calorie budget are sent to our AI proxy server, which calls a third-party large language model (currently Anthropic Claude). The request does not include your name, weight, or health data — only the dish and budget context needed to generate a lighter recipe. Generate personalised lighter-cooking suggestions. See Section 5 for AI-specific details.

2.3 Data we do NOT collect

We do not collect: email addresses or phone numbers (until accounts are introduced), precise GPS location, contacts, photos, microphone or camera input, financial or payment information, government-issued IDs, or biometric identifiers. When reading from Health Connect, we access only the Steps data type — we do not read heart rate, sleep, blood pressure, nutrition, body measurements or any other Health Connect data type.


3. Legal basis for processing

Activity Legal basis (NDPR/NDPA) Legal basis (GDPR, where applicable)
Providing the core app features (calorie plan, meal plan, food log, streaks) Consent (given at onboarding) and performance of the service you requested Performance of a contract (Art. 6(1)(b)) and consent for health-adjacent data (Art. 9(2)(a))
Analytics via PostHog Legitimate interest (product improvement) with PII minimisation Legitimate interest (Art. 6(1)(f)) — balanced against your rights via data minimisation and pseudonymisation
Error reporting via Sentry Legitimate interest (maintaining app stability and security) Legitimate interest (Art. 6(1)(f))
AI Kitchen dish remake Consent (you initiate each request) Consent (Art. 6(1)(a))
Reading step data from Health Connect Consent (you grant the Health Connect permission when prompted) Consent (Art. 6(1)(a))