Cookie Policy
Fit Fit City uses the cookies and storage needed to run the site, plus one small first-party note of which advert or link brought you here. If you choose Accept in our cookie banner, we also use the Meta Pixel to measure our adverts. If you choose Reject, or don’t choose, the Meta Pixel isn’t loaded and no advertising cookies are set.
Essential cookies we set
- ffc_session: keeps you logged in to the member area. It’s set when you log in or sign up, is secure and can’t be read by scripts on the page, and lasts up to 30 days or until you log out.
- ffc_consent: remembers whether you accepted or rejected advertising cookies, so we don’t ask on every page. It holds only “granted” or “denied” and lasts 6 months, after which we ask again. The same choice and the date you made it are also kept in local storage under the same name.
Advertising cookies (only if you accept)
If you choose Accept, we load the Meta Pixel, a script from Meta Platforms Ireland Limited, so we can see which of our Facebook and Instagram adverts lead to people visiting, joining and paying. It isn’t used to show adverts on our site: there are none. It sets these first-party cookies on fitfitcity.com:
- _fbp: a random identifier for this browser, so Meta can tell visits from the same browser apart. Lasts 3 months.
- _fbc: set only if you arrive from a Facebook or Instagram link that carries Meta’s click identifier; it stores that identifier so Meta can link the visit to the advert. Lasts 3 months.
With those cookies, the Pixel tells Meta when a page is viewed, when an account is created, when a checkout is started and when a membership or gift is paid for (with the price: £79, or £9.99 for the monthly plan). Meta also receives your IP address, your browser and device details and the address of the page. We don’t send your name, email address, training, food or progress data, we don’t use Meta’s “advanced matching”, and we turn off its automatic collection of button clicks. Pages whose address contains a password-reset link, a checkout reference or a gift code are reported to Meta without that part of the address. If you’re logged in to Facebook or Instagram in the same browser, Meta may also link these events to your Meta account using its own cookies, under Meta’s Privacy Policy.
After you accept, we also keep a short list of checkout references already reported (ffc_px_buy, in local and session storage) so a payment isn’t counted twice if the page is reloaded. It stays on your device.
Settings saved on your device
The member area saves a few choices in your browser’s local storage so they’re remembered next time: your chosen plan (ffc_plan), your chosen cuisine (ffc_cuisine), whether you use metric or imperial units (ffc_metric), whether you train at the gym or at home (ffc_mode), the personal best you last looked at (ffc_pb_sel), the week you’re on in each monthly programme (ffc_prog_week_…), shopping-list ticks (ffc_shop_…), how many people a meal plan is for (ffc_serves), the recipes you’ve saved as favourites (ffc_fav_recipes), kg or lb in the workout log (ffc_wl_unit), your rest-timer length (ffc_rest_secs), whether calorie numbers are hidden (ffc_hide_kcal), your weekly training goal (ffc_week_goal) and whether you’ve answered the plan quiz (ffc_quiz_done; your answers aren’t stored, apart from anything you tick for us to work around, such as knees or lower back (ffc_limits), which stays on this device so we can show tips and easier options).
It also remembers: the date you saw the readiness check before starting a plan (ffc_ready_…; your answers are never stored), the plan you follow and today’s log (ffc_follow_…, ffc_daylog_…), workout day swaps (ffc_swaps_…), your plan filters (ffc_plan_prefs), home-plan weeks (ffc_p12_…), a copy of where you are in each training plan and programme, kept until it has been saved to your account (ffc_pp_…, ffc_pp_dirty_…), habits, habit targets and weekly check-ins (ffc_habits_…, ffc_habit_targets, ffc_habits_off, ffc_checkins_…, ffc_pairs_…, ffc_lighter_…), timer, calendar and plate-calculator settings (ffc_timer_prefs, ffc_timer_custom, ffc_hf_voice, ffc_cal_prefs, ffc_plates, ffc_plates_last), whether set details are shown (ffc_set_detail), the progress photos you’re comparing (ffc_photo_cmp), the lift shown in your strength chart (ffc_wp_lift), which reminders, nudges and extras you’ve chosen to see (ffc_prefs), set ticks (ffc_ticks_…), the “New to the gym?” checklist (ffc_starter_…), whether you’ve seen the “welcome back” message after a break (ffc_break_seen_…) the food diary (ffc_fd_…) and, if you save the diary to your account, a note of which changes have been sent to it (ffc_fdsync_…). Progress photos are kept in your browser’s own database (IndexedDB) on this device.
So the workout log works with a poor signal, it also keeps some of your own training data on this device: routines you save (ffc_routines_…), a session you’re part-way through (ffc_ses_…), exercises logged while you were offline until they’ve been sent to your account (ffc_queue_…) and an account reference so the app can tell whose they are (ffc_last_uid). These are removed when you delete your account on this device, and the account reference is removed when you log out. If you install the app on your phone, your browser also keeps a copy of the site’s public files (pages, styles, fonts and images) so it opens quickly and works offline. Your account details, payments and member content are never stored in that copy.
On the public site we remember whether you’ve already seen or closed the free-week pop-up (ffc_fw_seen, in local storage), so it never shows more than once, and, while you’re signing up for it, that you chose to claim it (ffc_fw_pending, in session storage, cleared when you close the tab). Neither is used for tracking or advertising.
Which link brought you here (ffc_attr). If you arrive from one of our adverts or another link we’ve tagged, we note the campaign details in the link (such as the campaign name), the page you landed on, the date, and whether the link came from Facebook or Instagram (yes or no only, never the click identifier). We only keep this note if you choose Accept on our cookie banner. Until you choose, it stays in the open page’s memory and isn’t stored on your device or sent anywhere; after Accept it is kept in local storage for 30 days. Nothing is sent on page views: it is only sent to us if you create an account, claim a free week or start a checkout, as our Privacy Policy explains. This note itself isn’t sent to Meta or any other advertising network. (If you accept advertising cookies, the Meta Pixel reads Meta’s own click identifier from the link, as explained under “Advertising cookies”.) If you choose Reject, or withdraw later with Cookie settings, we don’t keep it and we delete any note already on your device. To delete a copy kept with your account, email us.
Short-lived items go in session storage, which your browser clears when you close the tab: a gift code you’re part-way through redeeming (ffc_gift_code), the reference for a payment you’ve just made, so we can confirm it if you need to log in first (ffc_paid_session), and whether you chose to view the public site while logged in (ffc_public_home).
Apart from the link note above, none of these settings are used for advertising, and none are used to track you. They stay on your device and you can clear them in your browser settings.
Third parties
- Stripe: when you go to checkout, you’re on Stripe’s own site, which uses its own cookies for payments and fraud prevention under Stripe’s cookie policy.
- Cloudflare: our hosting provider may set essential security cookies to protect the site from attacks. Cloudflare’s visitor statistics don’t use cookies.
- Meta: only if you accept advertising cookies, as explained above. Meta Platforms Ireland Limited receives the data and may share it with Meta Platforms, Inc. in the United States, under the transfer safeguards in our Privacy Policy.
Your choice and how to change it
The law (the Privacy and Electronic Communications Regulations, regulation 6) lets us use cookies and storage that are strictly necessary for a service you’ve asked for without asking, and that covers everything above apart from the link note (ffc_attr) and the advertising cookies. The link note is first-party, holds no name or contact details, isn’t used to follow you around other sites and isn’t sent to advertising networks, but we still only keep it with your consent.
For the advertising cookies and the link note we ask first. Our banner gives you Accept and Reject as equal choices, nothing is ticked for you, and the Meta Pixel doesn’t load, and the link note isn’t stored, until you choose Accept. Our lawful basis for both is your consent (UK GDPR Article 6(1)(a) and PECR regulation 6).
You can change your mind at any time with Cookie settings in the footer of every page, or with the button below. If you reject or withdraw, we stop the Meta Pixel and delete the _fbp and _fbc cookies and the link note (ffc_attr) from this site. Withdrawing doesn’t affect what was sent while you had agreed; to manage data Meta already holds, see Meta’s Privacy Policy or your Facebook or Instagram settings.
Managing cookies
You can also block or delete cookies in your browser settings. If you block the session cookie you won’t be able to log in to the member area. If you clear this site’s cookies and storage, we’ll ask for your cookie choice again.