Legal
Cookie policy
What skyfare.co stores on your device, and why. Last updated 24 September 2026.
1. Measuring visits and adverts, only if you say yes
We count page views so we can see which pages actually help people claim, and we want to know which of our adverts brought you here, so we stop paying for the ones that do not work. Neither is strictly necessary for anything you asked us to do, so under the Privacy and Electronic Communications Regulations 2003 we ask first. Until you accept, nothing is stored on your device, no page view is counted and nothing is shared with anyone. If you reject, it stays that way.
When you accept: our server counts the visit against a key made from your IP address, browser and the date, hashed with a secret that changes every day; your browser keeps a session id in session storage for the visit; we set the cookies marked Measurement and advertising below; and Meta's Pixel loads on our pages. If you then make a claim, our server tells Meta that a claim was made (and later whether it won and was paid), so Meta can tell which advert worked. The privacy notice says exactly what goes to Meta. You can change your mind at any time with Cookie settings at the bottom of any page; rejecting then deletes our measurement cookies and Meta's.
One thing happens without any cookie: if you arrived from one of our adverts, the advert's tags stay in the page address as you move around the site, and are saved with your claim if you make one. Nothing is stored on your device for that, and nothing is sent to Meta unless you accepted.
2. Cookies we set
| Cookie | Purpose | Set when | Lasts | Type |
|---|---|---|---|---|
fc_consent | Remembers whether you accepted or rejected measurement, so we stop asking | You answer the banner | Until you clear it | Strictly necessary |
sf_portal | Keeps you signed in to your claim page | You open your claim with your reference and email | 30 days | Strictly necessary |
sf_gate | Remembers that you entered the pre-launch site password | Before public launch only | 30 days | Strictly necessary |
sf_ops | Signs in Skyfare staff to the admin | Staff only | 12 hours | Strictly necessary |
sf_c | Remembers your answer on the banner on our server, so we only measure and tell Meta if you said yes | You answer the banner | 6 months | Strictly necessary |
sf_ft | The first page you arrived on and the link or advert that brought you | You accept | 6 months | Measurement and advertising |
sf_lt | The most recent advert or tagged link that brought you back | You accept and arrive from an advert or tagged link | 6 months | Measurement and advertising |
_fbp | Meta's browser id, used to tell which Meta advert led to a claim | You accept | 90 days | Measurement and advertising (Meta) |
_fbc | The id of the Meta advert click that brought you | You accept and arrived from a Meta advert | 90 days | Measurement and advertising (Meta) |
Meta's Pixel may also set its own cookies on our pages after you accept, covered by Meta's cookie policy. Nothing marked Measurement and advertising is set before you accept.
3. Managing cookies
You can delete or block cookies in your browser settings. Blocking sf_portal means you will need to sign in to your claim page each time; blocking the others has no effect on your claim.
4. Session storage in the claim form
While you fill in a claim, your browser keeps your answers, the page you arrived from and a key to your draft in session storage, so a refresh does not lose your place. It is wiped when you close the tab. Your draft itself is saved to our servers as you go, so that we can help if you get stuck; unsubmitted drafts are deleted after 6 months (see the privacy notice).