Crowdseek Ltd

Version 1.8 • Effective 7 September 2026 • Supersedes v1.7 (29 August 2026)

This Cookie Policy explains how Crowdseek Ltd ("we", "us", "our", "Crowdseek") uses cookies and similar technologies on our website (crowdseek.com), pilot landing pages (sleep.crowdseek.com, pilot.crowdseek.com), web app (beta.crowdseek.com; our earlier app at app.crowdseek.com has been retired), and in our emails. It should be read alongside our Privacy Policy.

1. What cookies and similar technologies are

Cookies are small text files placed on your device when you visit a website. "Similar technologies" includes web pixels, software development kit (SDK) trackers in mobile contexts, browser local storage, and device identifiers. They help websites work, remember preferences, understand how a site is used, and (where permitted) support marketing and advertising.

2. Where we use cookies and where we do not

Crowdseek runs on several domains and each is treated differently.

crowdseek.com (our brand site)

We run our own consent banner on this site. It appears the first time you visit and lets you accept all, reject all, or choose category by category, and it gives “Reject all” the same prominence as “Accept all”. You can change your choice at any time using the “Cookie preferences” link in the footer. Until you accept them we set only strictly necessary cookies. Our analytics and advertising tags, and the traffic-measurement script our hosting platform adds to every page, are held back and do not load. If you decline, they do not load at all. Until 7 September 2026 this site used Cookiebot by Usercentrics to ask for your consent. We now do it ourselves.

sleep.crowdseek.com and pilot.crowdseek.com (pilot landing pages)

These pages do set non-essential cookies — for example, analytics cookies to understand how the page is performing, and advertising cookies to measure the effectiveness of our paid campaigns. We use Cookiebot by Usercentrics to run a consent banner on these pages. The banner appears the first time you visit, lets you accept all, reject all, or choose category by category, and presents "Reject all" with equal prominence to "Accept all". You can change your choice at any time via the "Cookie preferences" link in the footer.

We are moving these pages to our own banner as well. Until we do, the banner you see there is Cookiebot’s.

beta.crowdseek.com (the Crowdseek app)

The app does not show a cookie banner of its own and sets no non-essential cookies of its own. It reads the choice you made on crowdseek.com or on one of our landing pages and applies it. You can see or change that choice at any time from the account section of the app. An earlier version of this policy said the app showed a banner of its own. It did not, and this paragraph corrects that.

Our app at beta.crowdseek.com keeps your plan, your sign-in and your night log in your browser’s local storage rather than in these technologies. This is what the app needs in order to work and is not used to track you. Clearing your browser data will sign you out and delete your night log from that device.

3. The categories of cookies we use (and let you choose from)

On the pages where our banner runs, you can choose between the following categories.

Strictly necessary (always on)

Cookies required for the page or app to function — for example, security cookies, session cookies, and cookies that remember your consent choice itself. These cookies are not switched off because the page would not work without them.

On crowdseek.com the strictly necessary cookies are __cf_bm, set by Cloudflare to tell people apart from automated traffic and lasting about 30 minutes, and cs_consent, which records the choice you made on the banner. We set cs_consent on .crowdseek.com and it lasts 12 months, so that the choice you make on our website also applies in the app. It replaced a cookie named CookieConsent, set by Cookiebot, on 7 September 2026.

When you make a choice we keep a record of it: a random consent identifier, which categories you chose, how you chose them, the version of the wording you were shown, the site and page you were on, the date and time, and the user agent string your browser sends. We do not keep your name or email address with that record. We keep it so that we can show what you were asked and what you chose.

Our hosting platform, GoDaddy, puts its own traffic-measurement script on every page of crowdseek.com. That is analytics rather than strictly necessary, so our banner holds it back and it does not run unless you accept analytics cookies. If you have been here before you may still see cookies named _tccl_visitor, _tccl_visit and _scc_session in your browser, left from a visit made before this holding-back was in place, or from a visit where you accepted analytics. Section 7 explains how to clear them.

Preferences (opt-in)

Cookies that remember choices you have made (for example, language, layout, or which information panels you have already closed) so the experience is more consistent next time you visit.

Analytics (opt-in)

Cookies that help us understand how the page or app is being used in aggregate — which pages are viewed, how long visitors stay, where they drop off — so we can improve the Service. We use these signals at population level, not to single out individual users.

Advertising (opt-in)

Cookies and tags from advertising platforms — currently the Meta Pixel (Facebook / Instagram) and Google Ads — that help us measure the effectiveness of our paid campaigns and reach people who are likely to be interested in Crowdseek. Where these tags are set, Meta and Google may act as independent or joint controllers; see Section 6B of our Privacy Policy. If you reject this category, the tags do not fire.

cs_aid — connects your visit to our website with your use of our app, so we can understand the journey. Contains no personal details on its own, but becomes linked to your record once you create an account. Set by Crowdseek on .crowdseek.com. Lasts up to 12 months; some browsers reset it after about a week. Statistics category — only set if you consent.

cs_entry_durable_v1 — remembers which link first brought you to our website (for example an ad, an email cue, or a friend’s share), so that if you come back a day or two later and then sign up, we can still tell where you originally came from. It holds only campaign labels — never your name, email address or anything you have written. Stored in your browser’s local storage by Crowdseek on crowdseek.com. Kept for up to 30 days, then deleted automatically. Statistics category — only stored if you consent; if you decline, or later withdraw, it is removed and we fall back to remembering this only for the current browsing tab.

4. Email tracking pixels

Our service emails (for example, magic-link sign-in emails) do not contain tracking pixels.

Our marketing emails — including the new-user email series sent to people who opt in at sign-up — contain small tracking pixels that record whether the email has been opened and whether you have clicked a link inside it. We use these signals to understand whether the series is working, to suppress further sends when an email has gone unread for a sustained period, and to time the next email in the sequence sensibly. We do not use these signals to single you out for profiling beyond what is needed to run the email series itself.

Where the links go. When you click a link in one of our marketing emails, it passes first through trk.marketing.crowdseek.com, a subdomain we control, which records the click and then sends you straight on to the page you asked for. We moved to our own subdomain in August 2026 because the shared address our email provider used before was on some ad blocker lists, which stopped the links working for anyone running a blocker.

You can stop email tracking by:

  • Unsubscribing from marketing emails using the link in any email, by replying "stop", or by emailing privacy@crowdseek.com.
  • Replying "less" — this reduces the cadence of the series; you can stop fully at any time afterwards.
  • Disabling automatic image loading in your email client. Tracking pixels rely on images loading; if you block images, the tracking does not fire.

5. Third-party cookies

Some of the cookies set on the pilot landing pages and the web app come from third parties rather than from Crowdseek. The third parties we currently work with are:

  • Meta (Facebook / Instagram) — Meta Pixel, in the Advertising category.
  • Google — Google Ads tags and (subject to consent) Google Analytics, in the Advertising and Analytics categories.
  • Cookiebot by Usercentrics — the consent banner on sleep.crowdseek.com and pilot.crowdseek.com, in the Strictly Necessary category. It is no longer used on crowdseek.com or in the app.

Each of these has its own privacy notice, available from the provider's own website. We list these specifically because we want you to be able to follow up directly if you want more detail on how they process data.

6. How long cookies last

Cookies fall into two broad lifetime categories:

  • Session cookies — deleted when you close the browser.
  • Persistent cookies — remain on your device for a set period (commonly anywhere from a few days to two years) so that the site can remember your choices on the next visit. Where we set persistent cookies, the lifetime is set to the shortest period reasonable for the purpose.

You can clear cookies at any time from your browser settings.

7. Managing your choices

You can:

  • Change your consent choices at any time on crowdseek.com, sleep.crowdseek.com or pilot.crowdseek.com via the "Cookie preferences" link in the footer.
  • Block or delete cookies via your browser settings. Browsers usually let you accept all, accept only first-party, block third-party, or block all. Note that blocking strictly necessary cookies may break parts of the Service.
  • Stop email tracking as described in Section 4.

8. Changes to this Policy

We may update this Policy when we add or remove cookies, change provider, or refine the categories shown on the banner. We will update the "Effective" date and, where the change is significant, we will surface a notice on the relevant page.

9. Contact

Questions about this Policy: privacy@crowdseek.com.

Crowdseek Ltd, registered in England & Wales no. 09560574. Registered address: 23 Westfield Park, Redland, Bristol, BS6 6LT, United Kingdom.

Document version: v1.8. Effective 7 September 2026; supersedes v1.7 (29 August 2026). v1.8 records that crowdseek.com and the app now use our own consent banner instead of Cookiebot, names the cs_consent cookie that replaces CookieConsent, and describes the record we keep of the choice you make. It corrects two things earlier versions said. The first is that the app showed a cookie banner of its own, which it did not. The second is the statement that our hosting platform’s traffic-measurement script was held back until you accepted analytics cookies. That was not true when it was written, because the script ran before any choice was made. From 7 September 2026 it is held back, and we tested that on the live site before publishing this. v1.8 also records that the visit identifier cs_vid is now kept only for the current browsing session unless you have accepted analytics cookies. Document version: v1.7. Effective 29 August 2026; supersedes v1.6 (28 August 2026). v1.7 names the two strictly necessary cookies crowdseek.com actually sets, explains the GoDaddy traffic cookies some visitors will find in their browser, and identifies Crowdseek Ltd on this page as the other policies already did. Document version: v1.6. Effective 28 August 2026; supersedes v1.5 (26 August 2026). v1.6 corrects what this policy said about crowdseek.com. The earlier version said that site ran no consent banner and set no non-essential cookies. That was wrong. The banner has been running there, and the section above now describes it. Document version: v1.5. Effective 26 August 2026; supersedes v1.4 (11 August 2026). v1.5 records that the app keeps a few of your own answers in your browser local storage, such as the habits you said get in the way and the line you picked on your Identity page. None of them is sent to us and we hold no copy of any of them. Document version: v1.4. Effective 11 August 2026; supersedes v1.3 (3 August 2026). v1.4 names the tracking domain that marketing email links pass through. v1.3 discloses the entry record (cs_entry_durable_v1) the app keeps in local storage for up to 30 days. v1.2 discloses the visit identifier (cs_vid) that the app itself creates in local storage, introduced on 30 July 2026. First publication 27 May 2026.

The Crowdseek app at beta.crowdseek.com does not set non-essential cookies of its own. It keeps your sign-in and your plan in your browser's local storage, along with a few of your own answers, like the habits you said get in the way. None of those reach us. It reads the analytics identifier only where you have already consented to statistics cookies on crowdseek.com or one of our landing pages. The app also creates a random visit identifier (cs_vid) the first time you open it. It is not a cookie and it contains nothing about you: it is used only to count visits and measure how far people get before creating an account, and it is never combined with anything you write in your night log. Unless you have accepted analytics cookies it is kept only for the current browsing session and disappears when you close the tab. Where you have accepted them it is kept in your browser’s local storage, and clearing your browser data removes it.