Cookies
Last updated 28 September 2026
The short version. This website sets no cookies at all. The app
sets one, and it holds the value 1. Nothing on this page is used
to profile you, to advertise to you, or to watch you move around the app, which is why there is no
cookie banner. The app keeps one further marker, for the paid subscription, and that one goes to
another company — it is set out below. Of the three markers in the table below, the cookie also
leaves your device, because your browser attaches it to requests to the app; our servers ignore
it.
This website
These pages — the ones you are reading now — set no cookies and load no third-party scripts or trackers. There is nothing to consent to.
If that ever changes we will say so here and in our privacy policy before anything is set, and a consent banner will appear.
The app
The app keeps three small markers that say you have used it before, so that if your data goes missing it can tell you rather than silently starting you from scratch. One of the three is a cookie.
| Marker | Where it lives |
|---|---|
gymislife.init | The app's ordinary storage — the same place as your training data, so it goes when that goes. Kept only because it is the one that works if you block cookies |
gilinit | The one cookie. First-party, set by the app, never read by this website. It holds the value 1 and nothing else — no identifier, nothing about you. Expires after 2 years, though Safari shortens cookies set this way to 7 days |
gil-init.txt | A file in the installed app's own storage, outside the browser part entirely. Only exists when you install the app from the App Store or Google Play |
What this does and does not do for you. In the installed iPhone or Android app the third marker survives almost anything, so the app can reliably tell a first run from a loss. In the browser version it cannot: clearing your site data removes both of the markers a browser has, and on Safari the cookie lapses after seven days of not opening the app, so a later visit may look like a first run. Either way, noticing is all this does. We hold no copy of your training data — other than anything you send us yourself, in a bug report or an email — and we cannot get it back for you. If you have exported a backup the app can offer to import it, and if you have not, it is gone. Our terms and our privacy policy say the same.
None of the three needs your consent. Their only purpose is to notice that the app's own data has gone, so it can tell you and offer to import a backup you exported yourself, rather than silently starting you from empty. Paragraph 4 of Schedule A1 to the Privacy and Electronic Communications Regulations permits this without consent, on the same basis set out in our privacy policy.
The subscription marker
The app keeps one more marker for the paid subscription: a random identifier for that installation, made the first time the app runs, so the subscription check asks about the same installation each time. It is not a cookie. Unlike the three above, this one goes to another company — to RevenueCat, which checks your subscription is genuine. It is cleared when you delete the app, but if you then restore or re-buy the subscription, RevenueCat joins the new installation back to the record it already had, so a reinstall is not a clean break. That is set out under Subscriptions in the privacy policy.
It needs no consent either, on the same basis as the three above: without it the subscription check cannot tell one installation from another, so the app cannot give you what you have paid for. What RevenueCat receives with it, and how long that is kept, are set out under Subscriptions in the privacy policy.
Everything else the app stores
The markers are the smallest part of it. Your training data, your plan, your records and the exercise cache all live on your device too — set out in full under what stays on your device in the privacy policy.
This page covers cookies and markers only. It is not the whole third-party picture — demonstration videos stream directly from MuscleWiki, bug reports pass through a spam filter, the launch-list emails go out through a mailing provider, and the paid subscription is checked through RevenueCat. All four are set out in the privacy policy.
Email tracking. An open-tracking pixel in a marketing email is covered by the same regulation as a cookie, and it needs consent in the same way. We turn open tracking, click tracking and link tagging off on every email we send, so there is nothing of that kind in our emails and nothing to consent to. The privacy policy says what is left, which is the delivery record the sending provider keeps whether we like it or not.