Privacy Policy

Last updated: 6 November 2026

In plain English: we collect the minimum needed to make the app work (an anonymous account so your progress isn't lost, and — if you enable it — your email via Apple / Google Sign-in). In CycleSync you also enter cycle and symptom information, which is health data — we treat it as sensitive, use it only to run the app for you, and never use it for advertising. In PistePath, your location stays on your phone unless you choose to share it with friends or to help improve our maps — both are off until you turn them on. In SnackHack, your body measurements, goals and food preferences stay on your phone, encrypted, and are never sent to us. In BargainBite, your household, budget and food answers stay on your phone unless you choose to share a plan with your family. When you open one of our app links, we count the visit without cookies and without storing your IP address. Usage analytics are off unless you allow them, and never include your health information or anything you type. We don't sell your data.

Who we are

This Privacy Policy applies to the mobile applications and websites operated by Deep Blue ("Deep Blue", "we", "us", or "our"). Deep Blue is a trading name of SwiftBee Ltd, a company registered in the United Kingdom. Our current apps include Walking Tai Chi for Seniors, Military Calisthenics: Women, Women’s Workout Pro, CycleSync, PistePath, SnackHack, and BargainBite. This policy applies to all of them collectively (the "Services").

Information we collect

We only collect what the app needs to function:

Account identifier. When you first open the app we create an anonymous account for you (a random ID) so we can save your plan progress without asking you to sign up. If you choose to sign in with Apple or Google, we also store the email address they return so you can restore your progress on another device. In apps that offer phone sign-in, we store your phone number instead.
Plan questions. To build your plan, the first-run questions ask about things like your age, height, weight and goal weight, activity level, sleep, and any body areas to avoid. In Walking Tai Chi for Seniors your answers are saved to your account so your plan can be rebuilt on another device; in Military Calisthenics: Women they stay on your phone. We use them only to personalise your plan — never for advertising, and they are never sent to analytics.
Practice data. Sessions you complete, day of your plan, duration, and general playback events (so we know videos are loading correctly). In Women’s Workout Pro, feedback you give after a workout (how it felt, the minutes and estimated calories, and any note you write) is saved to your account. Our exercise apps don't read sensor or heart-rate data. Cycle tracking in CycleSync is covered separately below.
Subscription status. Whether you have an active subscription, as reported by the App Store or Google Play. We do not receive your payment card details — those stay with Apple / Google.
Diagnostic data. Basic crash and error logs, which help us find bugs. These do not identify you personally. In Women’s Workout Pro they come from Firebase Crashlytics: a crash report holds where in the app the error happened, your device model, operating system and app version, and a random installation ID. Crash reports are sent only if you allow analytics (see App analytics); until you answer they stay on your phone, and if you say no they are deleted.

Cycle and health data (CycleSync only)

CycleSync is a cycle tracking app, so it necessarily handles information about your health. This section applies only to CycleSync, and it takes precedence over the general description above wherever the two differ.

What you enter. Period start and end dates, cycle length, flow, symptoms, moods, notes, and any other entries you choose to log. You decide what to record — every field is optional, and the app works with only the dates you give it.
What we derive. Predicted period, fertile window, and cycle-phase estimates, calculated from the entries above so the app can show them back to you and send the reminders you have switched on.
Apple Health / Google Fit. We read or write cycle data to these services only if you explicitly turn that on, and only the categories you grant. You can revoke that permission at any time in your device settings without affecting the rest of the app.

Legal basis. Under UK and EU GDPR, cycle and symptom entries are special-category data concerning health (Article 9). We process them on the basis of your explicit consent, which you give when you choose to log them and can withdraw at any time by deleting the entries or your account. Withdrawing consent does not affect processing carried out before you withdrew it.

What we never do with it. We do not sell cycle data, share it with advertisers or data brokers, use it for advertising, profiling, or marketing, or disclose it to employers, insurers, or any other third party for their own purposes. It is not used to train machine learning models. The only parties that touch it are the infrastructure providers listed below, acting on our instructions, and only so the app can store and sync your entries.

Disclosure to authorities. We will disclose cycle data in response to a legal demand only where we are satisfied it is valid and binding on us in the United Kingdom, and we will narrow, challenge, or resist any demand we consider overbroad or unlawful. Where we are legally permitted to tell you about a demand for your data, we will.

Deleting it. You can delete individual entries in the app at any time. Deleting your account removes your cycle history from our live systems; encrypted backups are overwritten on their normal rotation within 30 days. See Data retention below.

Location data (PistePath only)

PistePath is a ski-resort navigation app, so it uses your device's location. This section applies only to PistePath, and it takes precedence over the general description above wherever the two differ. PistePath doesn't make you sign up: it starts with an anonymous account (a random ID). If you choose to sign in with Google or Apple, we also store the name and email address they return, so you can keep your ski groups and referrals on another phone. It never asks for your contacts. You can delete a signed-in account in the app (Settings → Account → Delete account); see Delete your PistePath account.

Navigation (always on your phone)

Your position is used on your device to show you on the map, plan routes, and give turn-by-turn instructions. Routing, search, and offline maps run on the phone, and your position is not sent to us for any of this. When you are online, map imagery is downloaded from Google Maps Platform, which receives your IP address and the area of the map you are viewing (not your GPS position). The emergency screen works entirely on your phone, and its use is never logged.

Sharing your location with friends (Ski Groups)

Off unless you start it. You choose when to share and when the sharing session ends (at most 14 hours ahead, by default when the lifts close). You can pause or stop at any time, and a "Sharing location" indicator is shown on the map while it is on.
What is shared. Your position rounded to about 11 m, its accuracy, your speed, and when it was recorded, plus the display name you choose for the group. Members can also share a meeting point.
Who sees it. Only the members of that group. Our security rules refuse everyone else, including people with an invite who have not joined.
No history. We keep only your latest position, which is overwritten each time. It is deleted when you stop sharing and, if anything is left over, automatically within about an hour of the session ending. Group membership (the group name and members' display names) is kept until you leave or the group is closed.
Legal basis. We process this to provide the feature you have asked for (UK/EU GDPR Article 6(1)(b)). It is stored in Google Firebase in London.

Help Improve PistePath (optional GPS contributions)

Off unless you turn it on. If you agree, PistePath records GPS movement while you are navigating inside a ski area, to find where our maps, routes, and instructions are wrong. Navigation works the same whether or not you take part.
What is collected. GPS positions with their time, altitude, accuracy, speed, and direction; the piste or lift you were matched to; the instructions you were given and when you left the route; the resort, your route settings, and the app version. Nothing is recorded when you are not navigating, in the background, or outside the ski area, and the first and last 150 m of each session are removed.
How it is identified. Sessions carry a random contributor ID, not your account, name, or advertising ID. Location traces can still identify people, so we treat them as personal data: they are sent only over an encrypted connection, access is restricted, and they are analysed in aggregate — an issue needs several different contributors before anyone looks at it. GPS traces are evidence for a person to review: they never change routes on their own.
Legal basis. Your consent (Article 6(1)(a)), which you can withdraw at any time in Settings. Withdrawing does not affect processing carried out before you withdrew it.
Where and how long. On your phone until uploaded, and never more than 14 days. On our servers (Cloudflare, stored in the European Union), raw GPS sessions are deleted after 90 days. Map fixes and averages worked out from many skiers may be kept longer; they contain no individual journeys.
Deleting it. "Delete my GPS data" in Settings removes every session linked to your contributor ID from our servers, and your phone gets a new ID. We never sell this data, use it for advertising, or share it with anyone other than the providers listed below.

Referrals and subscriptions

If you join through a friend's invite, we record who invited whom so the referral programme can reward them. To decide whether a referral qualifies, our servers receive subscription status from the App Store (never your payment details), linked to your anonymous account. Referral records are kept while you use the app; email us to have them deleted.

Your plan and food preferences (SnackHack only)

SnackHack helps you choose restaurant orders that fit your goal. This section applies only to SnackHack, and it takes precedence over the general description above wherever the two differ.

Your account. SnackHack starts with an anonymous account (a random ID). If you choose to sign in with Google or Apple, we also store the name and email address they return; if you sign in with your phone number, we store that number, and Firebase sends the sign-in code to it by text message.
Your plan answers stay on your phone. To work out your daily calorie and protein targets, the first-run questions ask about things like your sex, date of birth, height, current and goal weight, how fast you'd like to get there, activity level, eating style, foods you like and dislike, and your favourite restaurants. These answers are stored only on your phone, encrypted, and your targets are calculated there. They are never sent to us or to analytics, so we can't see them, and they don't move to a new phone. Deleting the app or your account erases them.
Location (optional). If you allow it, SnackHack uses your location while you are using the app, to show restaurants near you and how far away they are. On Android it asks only for your approximate location. To find places to eat around you and work out distances, the app sends your location (or the town, neighbourhood or postcode you search for) straight from your phone to Google Maps Platform (the Places API), which returns nearby restaurants. Google processes these requests under its own privacy policy. We don't store your location on our servers, and it is never sent to analytics. Your phone keeps only the restaurants' place IDs and positions for up to a week, as Google's terms require. You can turn location off at any time in your phone's settings and search for an area instead; the rest of the app still works.
Restaurant menus. Chains' menus come from their own published nutrition information. For independent restaurants, the app sends the restaurant's Google place ID, name and address to our servers. Our servers then look for the restaurant's menu online and have it read by Claude, an AI model from Anthropic, which estimates each dish. The estimated menu is saved under the restaurant, not under you, and anyone who looks at that restaurant can see it. Nothing about you is sent to Anthropic.
Menu photos (optional). If you photograph a menu, the photos go to our servers and are read by Anthropic's Claude to estimate the dishes. The photos aren't kept by us, and under our agreement with Anthropic they aren't used to train its models. The estimated dishes are added to that restaurant's shared menu, with no name or contact details. Only photograph the menu, not people.
Daily limits. To keep the service fair, our servers count how many restaurant searches and menu scans each account makes per day. The count is linked to your account ID, holds only the date and the two numbers, and is deleted with your account.
Referrals and subscriptions. If you join through a friend's invite, we record who invited whom so the referral programme can reward them. To decide whether a referral qualifies, our servers receive subscription status from the App Store or Google Play (never your payment details), linked to your account. This is deleted with your account.
Deleting your account. In the app, go to Settings → Delete Account. This deletes your account, referral record and daily usage count from our servers and erases everything SnackHack stored on your phone; see Delete your SnackHack account.

Your meal plan and food preferences (BargainBite only)

BargainBite plans a week of dinners for your budget and makes the shopping list. This section applies only to BargainBite, and it takes precedence over the general description above wherever the two differ.

Your account. BargainBite starts with an anonymous account (a random ID). If you choose to sign in with Google or Apple, we also store the name and email address they return; if you sign in with your phone number, we store that number, and Firebase sends the sign-in code to it by text message.
Your plan answers stay on your phone. The first-run questions and Settings ask about your household (how many adults and children), weekly budget, supermarkets, eating style, allergies, foods you like and dislike, cooking time and, if you choose, details used to size portions (such as sex, date of birth, height, weight and goal). These answers, your weekly plans, shopping list, pantry and what the app learns about your tastes are stored only on your phone, encrypted where they include personal details. They are never sent to analytics, and unless you use Family sharing (below) we can't see them. Deleting the app or your account erases them.
Learning your tastes. When you rate a dinner or swap one out, the app can ask what you didn't like (for example "too sweet" or an ingredient to leave out) and uses your answers to plan future weeks. This is worked out and kept on your phone. You can see it and reset it in Settings.
Dinner ratings. If you rate a dinner, the stars, the reasons you tick, any review you write, the recipe, your app version, language and shop country are saved on our servers under your account's random ID, so we can fix or replace recipes people don't like. We don't show your ratings to other people, and we only look at them together across many people. Please don't put personal details in a review.
Family sharing (Premium, optional). If you create or join a household, the name you give and your food needs (allergies, eating style, likes and dislikes) are shared with the other members, up to six people, and stored on our servers with the household's week, shopping-list ticks and pantry, so everyone sees the same plan. Members join only with the household's invite code. Leaving the household, or deleting your account, takes your entry out; if you created the household, deleting your account ends it for everyone.
Import a recipe (Premium, optional). If you share a video link, recipe web page or screenshots into the app, they go to our servers, which fetch the page or video and have it read by Gemini, an AI model from Google, to write the recipe card. We don't store the link, screenshots or the recipe on our servers; the card is saved only on your phone. Google processes the request as our service provider under its terms for paid API customers, which don't allow it to use the content to train its models. We count how many imports each account makes per day (the date and a number, linked to your account ID) to keep the service fair; this is deleted with your account.
Prices and supermarkets. Prices shown in the app are estimates built into the app. Opening a supermarket's app or website from BargainBite takes you to that supermarket, whose own privacy policy then applies; we don't send it anything about you.
Subscriptions. Premium is billed by Google Play or the App Store. Our servers receive the purchase and subscription status from the store to unlock Premium (never your payment details), linked to your account.
Deleting your account. In the app, go to Settings → Account → Delete account. This deletes your account, your Family sharing entry (or the household you created) and your daily import count from our servers, and erases everything BargainBite stored on your phone; see Delete your BargainBite account.

App analytics (only with your permission)

The first time you open one of our apps we ask whether you're happy for it to send usage events to Google Analytics for Firebase. Nothing is sent unless you say yes, and you can change your answer any time in Settings. The legal basis is your consent.

The events tell us where an app is confusing or where people give up: which first-run screen was reached (for example "question 4 of 31"), whether the subscription screen was shown or closed, whether a purchase was started, failed (only the kind of failure, such as "cancelled") or went through, and whether a first session was completed. Each event carries a random app-instance ID, your device model and operating system, the app version, and an approximate location (city or country) that Google works out from your IP address. If an app asks how you found it, the event says which option you picked (for example "TikTok"), never anything you typed under "Other". Apart from that, we never send your answers to the first-run questions, health or cycle information, your name, email address or precise location, and our apps don't use the advertising identifier. Turning analytics off also deletes the app-instance ID from your phone.

In Women’s Workout Pro, events also show how a free trial goes: when your first workout starts, finishes or is left part-way (and how far through), when a second workout starts, whether you open the app on the first and second day after starting a trial, how long you spend in the app each time you open it, which first-run screen you left from, and whether a trial was cancelled or became a paid subscription, with the hours since the trial started. On iPhone, Apple tells our server when a trial is cancelled or converts, and our server passes that on to Google Analytics with your app-instance ID, only if you allowed analytics.

In PistePath, events also include things like a route being started or a map being downloaded. Coordinates and other location details are removed before any event is sent, searches record only how long the query was, and emergency-screen use is never logged.

Purchase records. When you start a trial, buy or restore a subscription, our server checks it with Apple or Google and keeps a record of the store transaction (product, offer, date and the store's transaction ID), along with the stores' later notices of renewals, cancellations, expiries and refunds. These records contain no name, email or payment details. If you allowed analytics, the record also holds your app-instance ID so we can see which steps lead to a subscription. We keep purchase records for accounting and to prevent fraud.

Which of our posts you came from (Android). Our social media posts link to the app with a short code that identifies the post (for example "f3hnfms"), not you. If you install one of our apps from Google Play through such a link, the app reads that code once from Google Play and keeps it on your phone. When you buy a subscription, the code is attached to the purchase in Google Play, together with a random ID that the app creates for this purpose, and to our purchase record. This tells us which posts lead to subscriptions. It contains nothing about you, and on iPhone there is no such code. The legal basis is our legitimate interest in knowing which of our marketing works.

DeepBlue All Access (membership bought at deepblue.org.uk)

If you buy DeepBlue All Access, you create a DeepBlue account by signing in with Google, Apple or your mobile number. We keep that sign-in (your name, email address or phone number, as the provider gives us) in Firebase Authentication, in a DeepBlue project separate from the individual apps.

Payments are handled by Stripe. Stripe receives your card details, billing name, email and country; we never see your full card number. We keep your Stripe customer ID and your membership status (plan, renewal date, whether it's active, cancelled or refunded).
Unlocking apps: when you sign in to a participating app with your DeepBlue account, the app asks the DeepBlue server whether your membership is active. Nothing from inside the apps (workouts, cycle or health data, location, food preferences) is shared with DeepBlue or with other apps.
Where you came from: if you arrive from one of our social media links, we record the app and platform the link came from (for example "Walking Tai Chi, Instagram") with your membership, to understand which posts work. We don't use cookies or tracking pixels for this.

Our app links

Our social media profiles and posts link to a short page for each app (for example mcwapp.web.app or walkingtaichi.web.app) with buttons for the App Store, Google Play and DeepBlue All Access. When you open one of these pages, or tap one of its buttons, we record: the time, which app's page it was, which of our posts or profiles the link came from (a short post code such as "t3hnfms", or the platform name), which button you tapped, the type of device (iPhone, Android or computer), the app you opened the link in (for example TikTok), and your country. The All Access page on deepblue.org.uk records the same when it is opened and when its checkout button is pressed.

Counting unique visitors without cookies. To count how many different people visit, rather than how many visits there were, our server briefly combines your IP address and your browser's description with a random value that changes every day, and turns them into a short code that can't be reversed. The same browser gets the same code for the rest of that day (UTC), so repeat visits that day count once. Your IP address and browser description are not stored, and each day's random value is deleted shortly after the day ends, so a code can't be traced back to you or matched with your visits on other days. Nothing is stored on your device for this: the app link pages set no cookies and use no local storage.

These records are stored with Cloudflare, and copies are sent to Google Analytics, which keeps them for two months and never receives your IP address from us. We keep the records for up to 400 days on Cloudflare, and in our own reports for as long as we need them, to see which of our posts bring people to our apps. They don't include your name, contact details or any account, and we don't use them to identify you or to advertise to you. The legal basis is our legitimate interest in knowing how our marketing performs. You can object by emailing us; because we can't link a record to you, simply not using our links is the most effective way to avoid being counted.

How we use it

To run and improve the Services.
To save your plan progress and streaks across devices you sign into.
To respond to your support emails.
To comply with legal obligations (for example, tax records).

We do not sell your personal information, and we do not use it for third-party advertising.

Service providers we rely on

The Services are built on a small number of trusted infrastructure providers who process data on our behalf under written contracts:

Google Firebase — authentication, database, hosting, crash reporting, push messaging and, only if you allow it, usage analytics (stored for reporting in Google BigQuery).
Mux — video streaming for the exercise clips.
Cloudflare — counts visits to our app links (see Our app links), and receives and stores PistePath GPS contributions (Help Improve PistePath) in the European Union.
Google Analytics — reports on visits to our app links, without your IP address.
Google Maps Platform — map imagery in PistePath, and finding nearby restaurants and distances in SnackHack.
Anthropic — reads restaurant menus and menu photos in SnackHack to estimate dishes. It receives no account or contact details.
Apple & Google — for authentication and in-app subscription billing on their respective platforms.
Stripe — payments and billing for DeepBlue All Access.

Data retention

We keep your account, practice data, and — in CycleSync — your cycle history for as long as you use the app, so your records and predictions stay available to you. If you'd like your data deleted, email us at admin@swiftbee.co.uk from the email associated with the account and we'll erase it within 30 days, subject to any legal record-keeping obligations.

Your rights

Depending on where you live (UK GDPR, EU GDPR, California CCPA, and similar laws) you have the right to access, correct, delete, or receive a copy of your personal information, and to object to certain processing. To exercise any of these rights, email us at admin@swiftbee.co.uk.

Children

The Services are not directed to children under 13, and we do not knowingly collect information from anyone under 13. If you believe a child has provided us with data, please contact us and we will delete it.

International transfers

Our providers may process data in countries other than the one you live in (including the United States). PistePath's shared locations and ski-group data are stored in London, and its GPS contributions in the European Union; analytics may be processed in the United States. Where required, we rely on standard contractual clauses or equivalent safeguards.

Changes to this policy

We'll post any changes to this page and update the "Last updated" date at the top. Material changes will also be surfaced in the app.

Contact us

Questions about this policy? Email admin@swiftbee.co.uk.