Privacy Policy

Last Updated: October 23, 2026 | Effective Date: April 11, 2026

This Privacy Policy explains how Flutta collects, uses, shares, and protects personal information across the Flutta iOS app and the Flutta websites at flutta.ms and datingwithms.com.

Flutta is the current brand name for Dating With MS. This version has been aligned to current product behavior in our codebase (app, web, and Firebase backend).

1. Who we are

Flutta is operated by Greenstone Technologies Limited.

Contact: flutta.ms/support or support@flutta.ms

2. Scope

This policy applies to:

• The Flutta iOS app.
• The Flutta web experience at flutta.ms and datingwithms.com, including onboarding, dashboard, connections, messaging, community, and profile pages.
• Backend services used by these products (Firebase, Cloud Functions, and related processors).

3. Information we collect

Category	Examples from product behavior
Account and authentication	Email address, account UID, display name, auth provider (email, Apple, Google, Facebook), verification status, created/updated timestamps.
Profile information	Name, date of birth, gender, interested-in preferences, relationship intent, bio, tagline, interests, photos, profile image index, matching preferences.
Health-related profile fields (optional)	MS type, mobility aids, openness level, and other MS journey information you choose to share.
Apple Health data (optional)	If you enable Apple Health auto-sync, we may read workout entries, workout timestamps, duration, distance, workout source names, and today's step count to support TodayWithMS fitness tracking.
Location	City/country text, privacy toggle for location, and where enabled latitude/longitude from device/browser location features. The Events screen in the app shows events near your profile town, a town or postcode you type, or, if you choose, your phone's location. Which events are near you is worked out on your phone. If you choose your phone's location there, it is used only on your phone and is never sent to Flutta or anyone else. A town or postcode you type, and your profile town, are looked up with Apple's map service to find where they are, as Apple Maps does. Apple is sent the place name and nothing about your Flutta account. Anything you search for on the Events screen stays on your phone, and the area it uses is never sent to Flutta.
Social and community activity	Likes, Priority Connects, passes, matches, daily check-ins, forum posts/replies/reactions, block/hide actions, and unlocked-liker state.
Messaging and media	Conversation metadata, message text, image attachments, VideoConnect requests and their status, read status, and conversation-level state.
VideoConnect video calls	Who asked whom, the time you picked, whether the request was accepted, declined or cancelled, when each of you was in the lobby or the call, how long you were connected, any extra time you both agreed to add, and which Flutta app and version you used. We also keep your device's time zone, so reminders show your local time, and your VideoConnect sound and full-screen settings. Flutta never records or stores the sound or picture of a call.
Safety and moderation	Reports, report reasons/descriptions, optional evidence images, moderation actions, admin logs, feature restrictions, ban fields, and blocked email hashes for abuse prevention.
Payments and allowances	Premium status, product IDs, entitlement details, usage counters for features such as Priority Connects, and your VideoConnect calls: how many you have, which are waiting on a reply, which were used or given back, and any extra calls you bought.
Appointments (optional)	The type, date and time, the clinician's name, the location, a clinic phone number if you add one, your reminder choice, your questions for the visit, and notes and next steps you write afterwards. Private to you, and not shown in Flutta's admin tools.
Technical and device data	FCM/APNs push tokens, app/web runtime metadata, diagnostic details, and operational logs needed to run and secure the service.
Local device/browser settings	Theme preference, muted groups, voice command preferences, bubble color, hidden IDs, and accepted rules flags stored locally on your device/browser.

4. How we collect information

• Directly from you when you register, complete onboarding, edit profile, message, post, report, or make purchases.
• From authentication providers and platform services when you use Apple, Google, or Facebook login.
• From Apple Health only if you turn on Apple Health auto-sync and grant HealthKit permission on your device.
• From your device/browser when you enable location, speech/microphone input, notifications, camera/photos, or related features.
• From in-app/web actions recorded to operate features (for example, likes/matches, moderation, and entitlement counters).

5. How we use your information

• Create and maintain your account.
• Deliver core connection/community features for friendship, support, and optional dating mode: profile discovery, matches, messaging, and community participation.
• Run TodayWithMS check-ins and feed privacy behavior.
• If you choose to share a motivational quote to the Community Feed, publish that quote with your check-in according to the visibility setting you selected.
• Import optional Apple Health workout and step data into TodayWithMS so exercise logs, fitness streaks, and related wellbeing features can stay up to date.
• Let you optionally share synced fitness activity in community spaces only when you choose to share it and according to the visibility setting you select.
• Generate optional appointment preparation questions using your chosen appointment type and relevant past appointment history, notes, outcomes, and next steps.
• Make an appointment summary on your phone when you ask for one, from the things you choose to put in it.
• Run VideoConnect video calls: send and answer requests, remind you before a booked call, connect you and the other person through LiveKit, keep each call to the length you both agreed, and give a call back when it doesn't happen.
• Operate Priority Connects, premium features, and usage limits.
• Deliver push notifications for matches, likes, messages, and VideoConnect requests and reminders.
• Detect abuse, process reports, and enforce moderation rules.
• Support account controls including hibernation and deletion.
• Comply with legal obligations and protect platform safety.

In the current iOS implementation, Apple Health access is read-only for workouts and step count. Flutta does not currently write workout data back into Apple Health.

6. AI and voice features

Flutta includes optional AI and voice features.

• AI profile writing and quote features send the prompt content you provide to OpenAI endpoints (directly in app/web code and/or via Cloud Functions, depending on feature).
• Appointment questions: only when you ask for suggested questions or AI prep ("Suggest questions" in the app, or AI prep on the website), the appointment's type, date, clinician's name and location, and the dates, clinicians, locations, notes, outcomes and next steps of your past appointments of that kind are sent to OpenAI via our backend to suggest questions. Your check-ins, private journal and food diary are not sent.
• Sorting your visit notes: only when you ask Flutta to sort or organise your notes ("Sort it for me" in the app, "Organise With AI" on the website), the words you typed or dictated about a visit are sent to OpenAI via our backend, with the appointment type, the clinician's name, the location and the date. In the app, your own words are always kept as you said them.
• Your appointment summary is made on your phone without AI. Nothing in it is sent to OpenAI.
• Text-to-speech voice output and some voice-related prompts use OpenAI audio APIs where enabled.
• Speech-to-text features use device/browser speech recognition services when you activate them.
• Food label reading: when you photograph a food label, the text is read on your device and only that text (never the photo) is sent to OpenAI via our backend to pick out the product name, nutrition figures and ingredients.
• Meal fill-in: when you tap "Fill in for me" on a meal you typed, only the meal name you typed is sent to OpenAI via our backend to suggest its usual ingredients and a rough estimate.
• Meal plans: when you build a meal plan, your food preferences, your allergies, the foods you have chosen to keep out, ingredients you often eat, and your saved recipes are sent to OpenAI via our backend to generate the plan. Your flare-up marks, symptoms and notes are not sent, and a food is only kept out of your plans if you have put it on your own list. Your name and account details are not included.

Use these features only if you are comfortable sharing the prompt content required for generation.

7. Purchases

• iOS purchases are processed by Apple StoreKit. We store entitlement/usage state in Firestore, not full card details.
• Product examples in code include Priority Connects and VideoConnect packs, plus premium subscriptions.
• Depending on launch configuration, some purchase-related screens may be visible while paid access remains limited or disabled.

8. Sharing and processors

We share data only as needed to provide the service, for safety, or to comply with law.

Primary processors and infrastructure

• Google Firebase (Auth, Firestore, Storage, Cloud Functions, Messaging).
• Postmark (transactional emails such as verification/reset flows).
• OpenAI (AI generation features where enabled).
• Open Food Facts, USDA FoodData Central and fatsecret (food product databases). Our servers send them only the words you search for, the barcodes you scan, the database ids of foods you open or have saved (so their details can be shown and refreshed), and whether you are in the UK or the US, which decides which database answers first. They never receive your name, your account details or anything else in your diary.
• DigitalOcean, which hosts a small relay server that Flutta runs to pass food requests to fatsecret. It handles the same search words, barcodes and food ids, and is set up not to keep a log of them.
• When the app shows a product photo from Open Food Facts (or from fatsecret, if its photos are switched on), your phone loads it directly from that database's servers. As with any website, they can see your phone's internet (IP) address when it does.
• OpenStreetMap (Nominatim). Flutta's server looks up the towns of listed events on OpenStreetMap to place them on a map, so the app can show how far away they are. Only each event's town, region and country are sent, never anything about you or other members. Distances use OpenStreetMap data, © OpenStreetMap contributors.
• Apple's map service. On the Events screen in the app, a town or postcode you type, and your profile town, are looked up with Apple's map service to find where they are. Your phone sends Apple the place name and nothing about your Flutta account. The Events screen never sends Apple your phone's location.
• LiveKit (video call infrastructure). While you are in a VideoConnect call, your camera picture and microphone sound pass through LiveKit's servers to the other person. LiveKit is given your Flutta account ID and your name for the call. Flutta never asks LiveKit to record a call, so the sound and picture are not stored.
• Apple, Google, Facebook (authentication and/or purchase platform flows you choose).

Website third-party requests

• Services used by specific web pages may include RSS aggregation, geocoding, avatar fallback images, and CDN-hosted assets.
• Those services may receive technical request data such as IP address and user-agent when your browser calls them.

Legal and safety disclosures

• We may disclose data when required by law, legal process, or to protect users and platform integrity.

Apple Health and sensitive data

• Apple Health access is optional and can be turned off at any time.
• Apple Health data is used to power TodayWithMS exercise and wellbeing features, not for marketing, profiling, or match ranking.
• We do not sell Apple Health data.
• Apple Health-derived activity is only shown to other users if you explicitly choose to share it inside the app.

Food diary and flare-up tracking

• The food diary is optional. If you use it, we store the foods and drinks you log, portions, meal times, recipes, meal plans and the food preferences, allergies and intolerances you enter.
• If you choose to mark a meal as a flare-up, we also store that mark and any symptoms or note you add. This is health information. We only process it with your explicit consent, which you give the first time you mark a flare-up, and we record when you gave it.
• We use this information only to show you your own diary (for example, the ingredients in meals you marked as a flare-up, and how many of your other meals they were in), to show you your own diary by date (for example the meals you logged in the days before you felt worse), to warn you about foods matching your allergies or triggers, and to build meal plans you ask for. It is not used for marketing, advertising, profiling, or match ranking, and it is never shown to other members.
• Your flare-up diary is private to you. It is kept in your Flutta account so it is safe and can be used in the app, and it is only shared with anyone else in a summary you choose to make and share yourself.
• Flutta staff cannot read your food diary, flare-up marks, symptoms or notes, your flare-up consent record, your appointments and visit notes, or your private journal through Flutta's admin and moderation tools. As with any cloud database, the person who runs Flutta's Firebase project has technical access to stored data. That access is not used to look at members' health information, except to fix or delete data when you ask us to, or where the law requires it.
• Patterns are based only on what you log. They are not a diagnosis or medical advice.
• You can remove any flare-up mark or delete any logged meal at any time. You can withdraw consent by removing your flare-up marks and no longer using the feature, or by contacting support@flutta.ms. Deleting your account deletes all of your food diary and flare-up data.
• If you add a product that is not in any database, its name, nutrition figures and ingredients (but not who added it) are saved so other members who scan the same barcode can use it.

Appointments and appointment summaries

• If you use Appointments, we store the appointments you add: the type, date and time, the clinician's name, the location, a clinic phone number if you add one, your reminder choice, your questions for the visit, and any notes you write about it. They are private to you.
• Reminders show the appointment type, the day and time, and the place if you added one. They appear as a notification on your phone, so they may show on your lock screen.
• If you save an event in the app, it is kept with your appointments and is private to you: the event's details from its listing (title, date and time, place, web link, description and picture link) and your reminder choice.
• Your appointment summary is made on your phone. Flutta does not upload it or keep a copy of it. It only leaves your phone if you choose to share it, print it or show it to someone (for example by email, message, AirDrop or print).
• Things you add only for a summary (for example your name, date of birth, hospital, NHS or medical record number, the "Since my last visit" ticks and the "What's changed for me" lines) stay on your phone and are not uploaded.
• If you choose to add your flare-up diary to a summary, it is shown by date, as you recorded it. If you choose to add days from your private journal, they are read on your phone only and are never uploaded or sent to AI.
• The summary is your own notes. It is not a medical assessment.

9. Hibernation mode

When you activate hibernation in app, your account is set to hidden/hibernating state and your profile is removed from normal matching visibility. Premium-only access returns to the standard launch experience while hibernating, and normal discovery features stay limited until you reactivate.

10. Account deletion

You can delete your account yourself from either the website or the iOS app. Deleting your account starts our backend deletion workflow and is designed to remove your account from our servers.

Website deletion steps

• Go to flutta.ms or datingwithms.com.
• Log in to your account.
• Click My Profile.
• Click Edit Profile.
• Select Delete Account and follow the confirmation steps.

iOS app deletion steps

• Open the Flutta iOS app and log in.
• Select your profile picture on the main page, at the top right of the screen.
• Select Edit Profile.
• Select Delete Account and follow the confirmation steps.

If you are struggling to delete your account, email support@flutta.ms and we will do what we can to support you.

• Our backend deletion workflow is designed to remove the authenticated user and related records, including authentication credentials (such as email/provider login record), user profile documents, matches, reports, daily check-ins/feed entries, user image storage paths used by the app, direct-message/forum messages authored by the deleted account, and your VideoConnect call records and call log.
• Some web deletion flows perform best-effort cleanup and user tombstoning before auth deletion.
• As with most cloud systems, backup/operational copies can persist temporarily for security, integrity, and legal reasons before final expiration.

11. Data retention

• Account/profile/messaging data is retained while your account is active.
• Food diary and flare-up data is retained while your account is active, until you delete the entries or your account.
• Appointments and your notes about them are retained while your account is active, until you delete them or your account. Appointment summaries are not kept by Flutta.
• VideoConnect call records (who took part, the times, and how long you were connected) are deleted automatically 90 days after the call or the request ends. A log of changes to your VideoConnect calls (a call set aside, used or given back) is kept for about 13 months, so questions about your calls can be answered. The sound and picture of a call are never recorded.
• Safety/moderation records can be retained longer to prevent repeat abuse and enforce platform rules.
• Entitlement and transaction-related metadata is retained as needed for service operations and dispute/financial compliance.
• Blocked email hashes and moderation references may be retained to enforce anti-abuse controls.

12. Security

We use layered security controls including Firebase security rules, authenticated access, and encryption in transit. Cloud storage providers apply encryption at rest for hosted data.

Direct one-to-one chat text and related system chat text are encrypted client-side before being saved to Firestore in current implementations. This helps protect message text in storage in addition to encryption in transit. Community/forum posts, attachments, and metadata may not use that same application-layer encryption path, and this design is not presented as end-to-end encryption. No system can guarantee absolute security.

13. International transfers

Your data may be processed in countries where our providers operate, including the United States.

14. Your rights and choices

Depending on your location, you may have rights to access, correct, delete, or restrict certain processing of your personal data.

• You can edit profile fields in-app/web.
• You can control marketing opt-in during onboarding (where offered).
• You can turn Apple Health auto-sync off in the app and revoke Health access at any time from the Health app or iOS Settings.
• You can control location, microphone/speech, camera/photos, and notification permissions at OS/browser level.
• You can request deletion or data requests via support@flutta.ms.

We do not sell personal information.

15. Children

Flutta is intended for adults 18+. We do not knowingly provide services to children under 18.

16. Changes to this policy

We may update this policy as product behavior or legal requirements change. This includes adding new consent flows or changing processors. We will update the date at the top of this page when we do.

17. Contact

Support: flutta.ms/support

Email: support@flutta.ms