Crowdseek Ltd

Version 3.20 • Effective 7 September 2026 • Supersedes v3.19 (26 August 2026)

This Privacy Policy explains how Crowdseek Ltd ("we", "us", "our", "Crowdseek") collects, uses, shares and protects your personal information when you use 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 related services (together, the "Service").

It applies to all users in the United Kingdom and EEA. Crowdseek's pilot programme is currently restricted to UK residents.

1. Who we are (Data Controller)

Controller: Crowdseek Ltd

Registered in England & Wales No. 09560574

Registered address: 23 Westfield Park, Redland, Bristol, BS6 6LT, United Kingdom

Privacy contact: privacy@crowdseek.com

General contact: support@crowdseek.com

Where we use advertising tools that involve a joint-controller relationship (for example Meta Pixel and Google Ads), the essence of those arrangements is summarised in Section 7 below.

Our services are provided through crowdseek.com, sleep.crowdseek.com and beta.crowdseek.com.

2. The information we collect

We collect information in four ways: (a) information you provide when you create an account, (b) information you provide as part of your personalised plan, (c) information collected automatically when you use the Service, and (d) information from third-party services where you choose to use them.

A) Account and contact details (collected on sign-up)

  • Email address (required) — used to send your one-time sign-in code and the pilot email programme and other service communications. Lawful basis: contract (UK GDPR Art. 6(1)(b)).
  • First and last name (required) — used to personalise your plan and emails. Lawful basis: contract.
  • Gender (optional) — used in aggregate to improve our recommendations and to understand the breadth of our pilot audience. Lawful basis: consent (UK GDPR Art. 6(1)(a)). You can leave this blank.
  • Phone number (optional) — used only if you ask us to reach you about your pilot participation, or for account recovery. Lawful basis: consent. You can leave this blank.
  • Postcode (optional) — used at coarse area level only to understand the UK regional reach of the pilot. We do not use full postcodes for any individual targeting. Lawful basis: consent. You can leave this blank.
  • "How did you hear about Crowdseek?" (optional) — used to measure which referral and marketing channels are working. Lawful basis: consent. You can leave this blank.
  • UK-residency attestation (required) — a single confirmation that you are a UK resident. Captured at sign-up; required to access the pilot. Lawful basis: contract / legitimate interest in operating a UK-scoped pilot.
  • Marketing preference (optional opt-in) — separate toggle to receive product news, promotions and offers from Crowdseek by email. This is distinct from the pilot email programme, which is part of the Service (see Section 10). Lawful basis: consent. You can withdraw at any time using the unsubscribe link in any marketing email, by replying “stop” to any email, or by emailing privacy@crowdseek.com.

You can update or remove any optional field at any time from your account settings, or by emailing privacy@crowdseek.com.

B) Your personalised plan content (wellbeing data — special category)

To build and adapt your personalised plan, the Service asks you to share information about your wellbeing. This typically includes:

  • The goals you choose (for example: sleep, stress, movement).
  • The outcomes you want to achieve (for example: "Switch off fast at bedtime", "Wake up ready — no sleep hangover").
  • The reasons that matter to you (for example: "Show up sharp for work", "Have patience and bandwidth for family").
  • Your progress entries, reflections, and any free-text inputs you choose to add.
  • Your interactions with daily tips, situational tips and your plan.
  • The actions that are in your plan, the ones you remove, and a coded reason for removing each one — you choose from a fixed list (it didn't fit my day, it didn't help, it was too hard right now, I kept forgetting). We store the code, never anything you write in your own words.

This information can reveal data about your health and wellbeing, which is special-category personal data under UK GDPR Article 9. Because of this, we ask for your explicit, separate consent before you provide any of it. The consent moment is presented before goal, outcome and reason selection, with a clear description of what you are agreeing to and an unticked confirmation tick. You can withdraw your consent at any time — see Section 9.

Lawful basis: explicit consent (UK GDPR Art. 9(2)(a)).

How we keep your wellbeing data inside Crowdseek. Your wellbeing data (goals, outcomes, reasons, reflections, plan content) is stored only inside Crowdseek's own systems. We do not send this data to our email service provider, our analytics provider, or any other third-party processor — not as text, and not as codes. Our emails are not personalised using your wellbeing data: the only personal detail used to personalise them is your first name. The effect is that your Article 9 wellbeing data never leaves Crowdseek's own controlled environment.

C) Information collected automatically

  • Usage and device data: pages and screens viewed, clicks and taps, session timing, referrer, approximate location (derived from IP at country/region level), device and browser type, operating system, and language.
  • Log data: IP address, timestamps, error logs and diagnostic data.
  • Cookies and similar technologies: see Section 8.

Lawful basis for essential analytics needed to operate the Service: legitimate interest. For non-essential analytics and advertising: consent, via our cookie banner (see Section 8).

D) Information from third-party services

If you connect a third-party service (for example an authentication provider), we may receive basic identifiers needed to enable that connection. Inviting someone you know to see how you are doing is not part of the service today; if we introduce it, we will update this policy and ask for your consent first.

When you create a plan, we store the information needed to rebuild it: your first name, email address, the outcome you chose, the reason you gave for it, an optional indication of how you would like to be pictured, the times you usually wake up and go to bed, the time you usually wind down, the everyday cues you attach to your actions, and whether you want check-in emails.

What we work out from how you use it. Alongside what you tell us, we derive a small amount of information from how you use the app: which actions you keep, change or drop, and a short running description of the direction your choices suggest. We keep the history of that description so the app can show you how it has changed over time. It is worked out from your own entries, it is never shared with anyone, and you can ask us for a copy of it or ask us to delete it in the same way as anything else in this policy.

3. Why we use your information (purposes)

We use your information to:

  • Provide the Service — create your account, save and adapt your personalised plan, deliver the features you request.
  • Personalise your experience — recommend tips, outcomes and pathways that fit your goals and reasons.
  • Communicate with you — service messages, support replies, security and account notices, the pilot email programme that forms part of the Service, and, if you opt in, marketing (promotions, offers and product news).
  • Improve and protect the Service — analytics, debugging, performance monitoring, abuse and fraud prevention.
  • Meet legal and regulatory obligations — compliance, lawful requests, record keeping.
  • Operate and evaluate the pilot — understand which referral channels are working, the UK regional reach of the pilot, and the engagement of pilot participants in aggregate.

4. Our legal bases (UK GDPR / EU GDPR)

We only process personal data where we have a lawful basis. We rely on:

  • Contract — to provide the Service you request (account creation, signing in, storing your plan, sending service messages such as security and account notices, and sending the pilot email programme that forms part of the Service).
  • Consent — for the optional sign-up fields (Gender, Phone, Postcode, “How did you hear about Crowdseek?”), for marketing communications (promotions, offers and product news), for non-essential cookies, and for special-category wellbeing data (Article 9 explicit consent).
  • Legitimate interests — to operate, secure and improve the Service, balanced against your rights.
  • Legal obligation — where we must comply with applicable law (for example, tax, security, lawful requests).

You can withdraw any consent at any time, without affecting the lawfulness of processing before withdrawal. See Section 9.

5. Special-category (Article 9) wellbeing data

The wellbeing information you share to personalise your plan (Section 2B) is special-category data under UK GDPR Article 9. We process it only:

  • With your explicit, granular consent, captured before you provide the data.
  • For the specific purpose of building, adapting and supporting your personalised plan, and — in aggregate and anonymised form — for understanding pilot outcomes.
  • With safeguards: restricted access, encryption in transit (TLS), held only inside our own systems, and deletion on request.

If you withdraw your Article 9 consent, your wellbeing data is deleted from your account; we retain only the account identifiers needed to manage the account itself.

Your night log — how a night felt, and anything you write about it — is health-related information. Today it is stored only on the device you wrote it on. It is not sent to our servers, and we cannot read it. If you clear your browser data or remove the app from your home screen, that log is deleted and cannot be recovered by us.

Words you write to label your own plan. You can name a moment in your plan after something you already do, such as your first coffee or the television going off. You can pick from a list we offer, or write your own words. If you write your own, those words are stored only on the device you wrote them on. They are not sent to our servers, we hold no copy, and we cannot read them. They are treated in exactly the same way as your night log.

Ticking a moment off during the day. If you tick a moment off as you go, that tick is stored on your device for the rest of that day and is then cleared. It is there so that you can see your own progress through the day. It is not a score, it is not kept, and it is not sent to our servers. What you actually did is recorded when you complete your morning review.

Some of your answers stay on your phone.

The app remembers a few things you tell it, so it does not have to ask you twice:

  • which habits get in the way, like smoking or drinking
  • the habit you are working on this week, and the ones before it
  • the line you picked on your Identity page
  • which safety notices you have already read

None of it reaches us. We hold no copy and we cannot read any of it.

One exception, and it is a small one. The three lines on your Identity page are our words, not yours. We record which one you picked, so we can tell which wording helps. Nothing else about that choice leaves your phone.

Where we record how the product is used, we record only codes, counts and yes/no values — for example that a night was logged and roughly how long the note was, never the words you wrote.

The one exception is the feedback box. If you choose to write to us about the app — from the "Tell us what you think" card in your Crowd — what you write is sent to us and stored so that we can read it and act on it. That box is for feedback about Crowdseek itself, not about your health, and it is the only place in the app where anything you type reaches us. We keep it while we are still working on what you told us, and you can ask us to delete it at any time. If you tick "You can quote me", we may use your words publicly — never alongside your name unless we ask you first.

6. How we share information

We do not sell your personal data. We share information only in the limited circumstances below.

A) Service providers (processors)

We use vetted providers to host, maintain and operate the Service. They process data on our instructions under written contracts that include UK GDPR Article 28 terms (and, where relevant, the UK International Data Transfer Addendum and the EU Standard Contractual Clauses). Categories include:

  • Cloud hosting and infrastructure.
  • Web app development and hosting (Rocketmakers Ltd).
  • Landing-page hosting and paid-media operations (Amplify Growth Ltd).
  • Customer relationship management and email service provision — our email service provider sends our service messages, sign-in emails, the pilot email programme, and (where you opt in) marketing. As explained in Section 2B, we do not transfer your Article 9 wellbeing data to this provider in any form; only your first name, email address, sign-up date and your consent and engagement details are shared. The identity of our current email service provider is maintained in our Processors Register, available from the footer of this page. We may change providers from time to time; this Policy does not need to be amended each time the provider changes.
  • Privacy-focused analytics, error monitoring and performance tools.
  • Email delivery and customer support tools.

B) Joint controllers (advertising)

Where we run advertising through Meta (Facebook / Instagram) and Google Ads, those services may set the Meta Pixel and Google Ads tags on our landing pages and web app. Meta and Google act as independent or joint controllers for that processing under UK GDPR Article 26. In summary:

  • Crowdseek decides which audiences are targeted and which conversions are measured.
  • Meta and Google decide how the advertising platform operates and how data is processed on their infrastructure.
  • Both parties are responsible for the lawfulness of the processing within their respective roles.

These tags only fire if you have given consent via our cookie banner (see Section 8). Full details of Meta and Google's processing are available in their own privacy notices.

Where you have accepted advertising cookies, we also tell Meta from our own server when a sign-up happens, so that we can see which adverts work. We send a scrambled (hashed) version of your email address, a scrambled version of your account number, and the click identifier Meta itself placed in the link you followed. We do not send your outcome, your reason, your plan, your night log, or anything you have written. We began doing this on 1 September 2026.

C) Aggregated or anonymised data

We may share aggregated or anonymised insights (for example, pilot engagement trends) that cannot reasonably identify you.

D) Legal and safety

We may disclose information if required by law, or to protect rights, safety and security (for example, to prevent fraud or abuse).

E) Business changes

If we are involved in a merger, acquisition, financing or sale of assets, data may be transferred as part of that transaction. If that happens, we will take steps to protect your data and notify you where required.

We use the following providers to run the service: Supabase (database and sign-in, EU), Railway (application hosting, United States), Resend (sign-in codes and check-in emails), Klaviyo (our email programme), GoDaddy (this website), Google Analytics and Google BigQuery (website measurement, and storage of that measurement in a UK or European region) and Cookiebot (consent management on our landing pages, which we are replacing with our own consent tool).

7. International data transfers

Some of our service providers (including our email service provider) are based outside the UK or EEA. Where personal data is transferred outside the UK or EEA, we use appropriate safeguards, including:

  • Adequacy regulations where applicable (for example, the UK-US Data Bridge for US providers covered by it).
  • The Standard Contractual Clauses (SCCs) and the UK International Data Transfer Addendum.
  • Other lawful mechanisms recognised by UK GDPR and EU GDPR.

As explained in Section 2B, we do not transfer your Article 9 wellbeing data to providers located outside the UK or EEA — this data is held only inside our own controlled environment.

Some of the providers we use process information outside the UK; our application hosting is in the United States. Where information leaves the UK we rely on the safeguards required by UK data protection law, including standard contractual clauses with the providers concerned.

8. Cookies and analytics

We use cookies and similar technologies to keep the Service working (strictly necessary cookies, always on), to understand usage and improve the Service (analytics cookies, opt-in), to remember your preferences (preferences cookies, opt-in), and to measure and serve advertising (advertising cookies, opt-in).

We run our own consent banner on crowdseek.com. Our landing pages at sleep.crowdseek.com and pilot.crowdseek.com still use Cookiebot by Usercentrics, and we are moving them to our own banner as well. On both, “Reject all” is presented with equal prominence to “Accept all”, and you can change your choice at any time via the “Cookie preferences” link in the footer of those pages. The app at beta.crowdseek.com shows no banner of its own. It applies the choice you made on our website, and you can see or change that choice from the account section of the app.

When you make a choice on our banner we keep a record of it: a random consent identifier, the 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. An earlier version of this policy said that crowdseek.com set only strictly necessary cookies and therefore needed no consent banner. That was wrong. A banner has run on that site throughout, and what it holds back is described in our Cookies Policy.

Our programme and marketing emails contain small tracking pixels that record whether an email has been opened and whether you have clicked a link inside it. For the pilot email programme we use this to operate the Service — for example, the cadence and the suppression described in this Section. For marketing we use it to understand, in aggregate, whether a campaign is working. If you would rather not have this measured, you can unsubscribe from marketing emails at any time, or disable image loading in your email client.

For a full list of the cookies we use and their purposes, see our Cookie Policy.

Analytics identifier. With your consent to statistics cookies, we set a randomly generated identifier (cs_aid) on your device, shared across crowdseek.com and its subdomains. We use it to understand how people move between our website and our app — for example, whether someone who used the 3am Reset later created an account. The identifier does not contain your name, email or any other detail about you, but once you create an account it becomes linked to your record and is treated as personal data from that point. On some browsers it is reset after about a week. You can withdraw consent at any time through the settings link on our site.

Campaign parameters. If you reach us from an advertisement, an email or another website, the link you arrive on may carry campaign tags in its address (utm_source, utm_medium, utm_campaign, utm_content and utm_term). If you then give us your email address, we store those tags against your record, so we can tell which advertisement or channel brought you here and what it cost us. They describe the link you clicked, not you, and we do not use them to build a picture of your interests or to show you different content. We keep them for up to 24 months alongside email engagement data, then delete or anonymise them.

Where our website analytics is stored. Our website analytics is exported once a day from Google Analytics into BigQuery, a Google Cloud service, held in a project we control in a UK or European region. We do this so we can keep and analyse our own measurement — for example, which routes and campaigns lead to someone creating an account — rather than only what the Google Analytics screens will show us. What goes there is website analytics only: the pages you viewed, what you did on them, roughly where you were, the device and browser you used, how you arrived, and the analytics identifiers described above. Nothing from the app goes there — not your night log, not the outcome or reason you chose, not your email address. It is kept for 14 months and then deleted, and it exists at all only where you consented to statistics cookies.

9. Your rights

Depending on where you are, your rights include:

  • Access — request a copy of your data.
  • Rectification — correct inaccurate data.
  • Erasure — request deletion ("right to be forgotten").
  • Restriction — limit processing in certain cases.
  • Portability — receive your data in a usable format where applicable.
  • Objection — object to processing based on legitimate interests.
  • Withdraw consent — at any time, where processing is based on consent. Withdrawal does not affect the lawfulness of processing before withdrawal.

To exercise any of these rights, email privacy@crowdseek.com. One important exception: your night log (the line you write about each night, what your crew replied, and every use of Help Now), any words you write to label a moment in your plan, and your ticks for the current day are stored only on your own device and we hold no copy, so we cannot produce them for you on request. For that data the route is in the app itself: Your Crowd → Download a copy gives you the whole of it as a file, built on your device. That is also how you take it with you, and it is the only way to keep it if you clear your browser data. We may need to verify your identity before we can complete your request.

Complaints. If you are in the UK, you can complain to the Information Commissioner's Office (ICO) at ico.org.uk. If you are in the EEA, you can complain to your local supervisory authority.

10. The pilot email programme and marketing communications

When you create an account you join the Crowdseek pilot email programme. These programme emails are part of the Service itself — they carry your plan, prompts and guidance, and (when you have been inactive) a short restart sequence to help you ease back in — so we send them on the basis of our contract with you (UK GDPR Art. 6(1)(b)), not on marketing consent. They are separate from marketing (promotions, offers and general product news), which we send only if you separately opt in. The programme is built around the following method:

  • Cadence: more frequent in the first week to help you find your rhythm, then less frequent. Typically: daily for the first seven days, every three days for weeks two to five, and weekly or as needed thereafter.
  • Restart / ease back in: if you stop using Crowdseek for a while, the programme includes a short restart sequence to help you re-establish your routine. This is part of the Service, not a marketing campaign.
  • Reply-friendly: every email comes from a monitored inbox. A human reads replies (the founder during the pilot). If you reply to any email, the automated sequence is paused for at least 72 hours so the conversation can land without an interruption.
  • Self-serve “less”: if a programme email ever feels too much, replying with “less” switches you to a less-frequent cadence. Every programme email also includes a one-click unsubscribe button: pressing it, replying “stop”, or using the unsubscribe link stops the programme emails. Closing your account stops them too. Marketing emails (promotions, offers and product news) have their own separate unsubscribe (see below).
  • Suppression: if you don't open or interact with the emails for a sustained period (typically seven days), we suppress further sends until you re-engage with the Service.
  • Personalisation: as described in Section 2B, the only personal detail used to personalise a programme email is your first name. Your wellbeing data — including the outcome and the reason you chose — is never sent to our email service provider and is never used to personalise these emails.

Although the programme emails are part of the Service, every one includes a one-click unsubscribe button, so you can stop them at any time — by pressing it, replying “stop”, or closing your account. Separately, you can unsubscribe from marketing (promotions, offers and product news) at any time using the link in any marketing email, by toggling the preference in your account, by replying “stop”, or by emailing privacy@crowdseek.com — without leaving the pilot. We will still send essential service and account messages (for example, security or account notices) when necessary; these are based on the contract between us and our obligation to keep your account secure, not on marketing consent.

If you turn them on, we send two check-in emails a day: a short prompt around the time you said you wind down, and a note the next morning inviting you to log the night. These are part of the service you asked for rather than marketing, and you can turn them off at any time in the app.

11. Data retention

We keep personal data only as long as needed for the purposes set out above:

  • Account and plan data: kept while your account is active.
  • Wellbeing data (Article 9): deleted on withdrawal of consent or on account closure.
  • Email engagement data (open / click signals): kept for up to 24 months to measure the email series, then deleted or anonymised.
  • In-app activity records (screens opened, actions logged, session timing): kept for up to 24 months, then deleted or anonymised.
  • Deletion requests: we delete or anonymise within a reasonable period (typically 30 days), unless we must retain certain records for legal or security reasons.
  • Backups: may persist for a limited period before being overwritten.

12. Security

We use appropriate technical and organisational measures to protect personal data, including access controls, encryption in transit (TLS), and monitoring for abuse. No transmission or storage method is 100% secure, but we work to protect your data responsibly. We will notify you and the ICO of a personal data breach where the law requires it.

13. Children

The Service is not intended for children under the age at which they can lawfully consent to data processing in their country. The Crowdseek pilot is restricted to UK residents aged 18 or over. If you believe a child has provided personal data, contact privacy@crowdseek.com and we will take appropriate steps.

The service is for adults aged 18 and over. We ask you to confirm that you are 18 or over when you create an account.

14. Changes to this policy

We may update this policy from time to time. We will update the "Effective" date and, where appropriate, notify you of significant changes. Material changes affecting consent will require fresh consent.

Our record of your choices. When you create an account we store a record of exactly what you were shown and what you agreed to, with the date and time. We keep this so we can answer the question “what did I agree to?” accurately, including if you ask us later.

15. Contact

Privacy questions or requests: privacy@crowdseek.com.

General contact: support@crowdseek.com.

Postal: Crowdseek Ltd, 23 Westfield Park, Redland, Bristol, BS6 6LT, United Kingdom.

Document version: v3.20. Effective 7 September 2026; supersedes v3.19 (26 August 2026). v3.20 records three things. First, from 7 September 2026 crowdseek.com and the app use our own consent banner rather than Cookiebot, and Section 8 now describes the record we keep of the choice you make. Second, it corrects a statement in Section 8 that crowdseek.com set only strictly necessary cookies and needed no banner. That was wrong, a banner had been running there throughout, and our Cookies Policy corrected the same statement on 28 August 2026. Third, it discloses that where you have accepted advertising cookies we also tell Meta from our own server when a sign-up happens, sending a scrambled email address, a scrambled account number and Meta’s own click identifier, and nothing you have written. That began on 1 September 2026. It also records that the visit identifier cs_vid is now kept only for the current browsing session unless you have accepted statistics cookies. Document version: v3.19. Effective 26 August 2026; supersedes v3.18 (11 August 2026). v3.19 discloses four more things the app keeps on your own device and nowhere else: the everyday habits you say are getting in the way, including smoking and alcohol; the habit you choose to work on in a given week, and the record of previous weeks; the line you pick on your Identity page; and which safety notices you have already read. None of them is sent to us and we hold no copy of any of them. It also records that where you pick one of three statements we wrote, we log which one as a code in our activity records. Document version: v3.18. Effective 11 August 2026; supersedes v3.17 (7 August 2026). v3.18 discloses the campaign tags we store when you arrive from an advertisement, names the times you wake and go to bed rather than only the time you wind down, describes what we work out from how you use the app, and sets a retention period for in-app activity records. v3.17 discloses two things the app keeps on your own device and nowhere else: the words you write to label a moment in your plan, and the ticks you make during the day. Neither is sent to us and we hold no copy of either. Section 5 describes both, and Section 9 now lists them alongside your night log as data we cannot produce on request. v3.16 corrects an incomplete statement in Section 9: it directed every rights request to privacy@crowdseek.com, but we hold no copy of your night log and therefore cannot answer an access or portability request for it that way. Section 9 now names the in-app download, which is the only mechanism that can. Nothing about how the log is stored has changed. v3.15 removes the last description of inviting a supporter to your Crowd as a current data flow — that feature is not part of the service today — and states plainly that it is not. This aligns the policy with the website, which as of 1 August no longer refers to the feature anywhere. Nothing about how we handle your night log has changed: it is still stored only on the device you wrote it on. v3.14 records that your plan is now saved to your account on our servers (previously it was described as living only in your browser's local storage), and describes the plan-change records added on 31 July 2026 — which actions you keep or remove, and a coded reason for each removal. Your night log is unchanged: it remains on your device only. v3.13 discloses that our website analytics is exported daily into BigQuery (Google Cloud), what that export does and does not contain, the UK/European region it is held in, and the 14-month retention period. Earlier changes: v3.12 discloses the in-app feedback box added on 31 July 2026 — the one place in the app where words you type are sent to us — in Section 5; v3.11 discloses the visit identifier (cs_vid) that the app itself creates in local storage, introduced on 30 July 2026; v3.10 removes the description of send-time email personalisation from Sections 2B, 6A and 10 — Crowdseek does not send wellbeing data to its email service provider in any form, and email personalisation uses first name only; and corrects Section 2A to describe one-time sign-in codes rather than magic links. Hosted on Crowdseek pilot landing pages (sleep.crowdseek.com, pilot.crowdseek.com) during the pilot; canonical version may move to crowdseek.com post-pilot.

The Crowdseek app at beta.crowdseek.com does not set non-essential cookies of its own. It keeps your sign-in in your browser's local storage, and a copy of your plan on your device so it opens instantly. Your plan is also saved to your account on our servers, so it survives a new phone or a cleared browser — your night log is not, and stays only on the device you wrote it on (see Section 5). 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 contains nothing about you, is never combined with anything you write in your night log, and is used only to count visits and measure how far people get before creating an account. Unless you have accepted statistics 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.