What should I expect at my first activity?

A small group of 4 to 6 women, all meeting for the first time. One thoughtfully curated activity — pottery, a themed dinner, comedy night, whatever feels right. We handle every detail. You just show up.

How does matching work?

When you take the quiz, we learn about your chapter of life, your energy, your neighbourhood, and what you’re looking for. We match you with women who share your season — same life stage, same vibe, close to you. No swiping. No random strangers.

Is this a dating app or a networking app?

Neither. Nobody comes to pitch anything or swipe on anyone. Chérie is built for one thing: real female friendship. The activities are curated, the groups are intimate, and nobody knows each other yet — that’s the whole point.

Does the membership include the activities?

Your membership gives you access to the village — the matching, the community, and the platform. Each activity is priced separately based on what it is — you’ll always see the cost before you book. Members get 15–50% off every experience.

What if I don’t click with my group?

Tell us. We’ll personally follow up and make sure your next experience feels better aligned. If after 14 days it doesn’t feel right, we’ll refund you in full. No questions asked.

Where is Chérie available?

London and San Francisco. More cities are coming. Take the questionnaire — if we’re not in your city yet, you’ll be first to know when we arrive.

Is Chérie only for women?

Yes. Studies show that close female friendships reduce cortisol levels, strengthen immune function, and significantly extend life expectancy. Women with strong female bonds make better decisions, exit bad situations sooner, and report a higher sense of self-preservation. We’re building the village women have been missing.

Back to home

Cookie Policy

Version 1.0 · Last updated: 10 August 2026

This page is the full list promised by clause 14.3 of our Privacy Policy. It covers the website at cherie.social. Section 5 covers the Chérie app, which does not use cookies but does use a device identifier, and which we describe here so that everything is in one place.

1. What these things are

A cookie is a small file a website asks your browser to keep and to send back on every later request. It is the only one of these technologies that travels back to a server automatically, which is why it is the one the law is written about.

Local storage and session storage are also stored by your browser, but they never travel anywhere on their own. Something has to read them and choose to send them. We use local storage to hold your answers to the questionnaire so that a refresh, a back button or a lost connection does not make you start again.

A device identifier is the app equivalent: a number your phone gives an app so that repeat use can be counted without knowing who you are. It is not a cookie and it is not an advertising identifier.

Strictly necessary means the thing you asked for does not work without it — staying signed in, taking a payment, keeping the site secure. Those do not need your consent. Everything else does.

2. Cookies this website sets

This is the complete list as at 10 August 2026. If it is not on this list, we do not set it.

Name	Set by	What it does	How long it lasts	Needs consent?
`__casting_admin_session`	Chérie (first party)	Keeps a Chérie administrator signed in to our internal casting console. It is only ever set after a member of staff signs in with an approved email address. Browsing the site as a member or a visitor never sets it. It is `HttpOnly` — no script on the page can read it — and `Secure`, and `SameSite=Lax`.	5 days, then it expires. Signing out deletes it immediately.	No — strictly necessary
Stripe’s own cookies	Stripe, Inc. (third party), from `js.stripe.com`	Fraud prevention and payment security. Stripe’s payment script loads on the subscription and payment steps only — not on the rest of the site — and Stripe sets its own cookies when it does. We do not set them, we cannot read them, and we do not receive them. Stripe publishes what it sets at stripe.com/legal/cookies-policy. We list them here by reference to Stripe’s own published policy rather than by name, so that this page cannot go stale the next time Stripe changes them.	Set by Stripe. See Stripe’s policy.	No — strictly necessary for taking a payment

There is no third cookie. In particular there is no analytics cookie, no advertising cookie, no social media cookie, and no cookie set by a content delivery network, an embedded video, an embedded map, or a font provider. Our two typefaces are served from cherie.social itself rather than from Google Fonts, so loading a page does not tell Google that you did.

3. Browser storage that is not a cookie

The questionnaire is long and people fill it in over more than one sitting. So it is saved as you go, on your device.

Key	Where	What is in it	How long it lasts
`seasons-quiz`	Local storage	Your answers to the first questionnaire, which step you reached, when you started, and the campaign parameters from the link you arrived on (utm_source, utm_medium, utm_campaign, utm_content) so that we can tell which of our own posts and adverts brought people to us.	Until you clear your browser storage for this site. It has no expiry of its own.
`seasons-phase2`	Local storage	Your answers to the second questionnaire, the one after you create an account, and how far through it you are.	Same — until you clear browser storage for this site.
Firebase authentication state	Browser storage, written by Google’s Firebase SDK — not a cookie	Your signed-in state, so that you are not asked to sign in again on every page. Only present once you have an account and have signed in.	Until you sign out, or until the sign-in expires.

The two keys still say seasons because that is what we were called when they were written, and renaming a storage key silently throws away the answers of everyone who is mid-questionnaire at the moment we deploy it. We would rather have an untidy name than lose your work. It holds nothing beyond what is described above.

None of this is readable by anyone else. It is on your device, in storage scoped to cherie.social, and no other website can reach it.

4. Analytics and advertising

We want to be exact about this rather than reassuring, because “we may use” is how most cookie policies avoid saying anything at all.

What we checked. On 10 August 2026 we read the source of this website and we also fetched the live homepage and read the HTML that was actually served.

What we found. The site contains code for Google Analytics 4 and for the Meta pixel. Both are switched off. Each one only loads if a configuration value holding its ID has been set, and neither ID is set — so on the live site neither script is present, neither runs, and neither sets a cookie. We confirmed that by reading the served page, not by reading the code.

What is still there. Every page does carry three network hints —preconnect to www.googletagmanager.com and to connect.facebook.net, and dns-prefetch to www.google-analytics.com. They are a leftover from when those tools were expected to be switched on. They open a connection in advance; they load no script, run no code and set no cookie. But opening a connection does disclose your IP address to Google and to Meta, and you are entitled to know that even though nothing else follows from it. They should be removed while the tools are off, and this line stays here until they are.

What happens if we turn analytics on. We will ask you first. We will not set an analytics or advertising cookie without your consent, we will update this page before we do it rather than after, and consent will be as easy to withdraw as it was to give. Until that happens there is no cookie banner on this site, for the plain reason that there is nothing to consent to.

The decision on whether to run analytics at all, and on what basis, is not yet made: [To be completed — decision on whether Google Analytics 4 and the Meta pixel are switched on, and the consent mechanism if they are]

5. In the Chérie app

The app is not a browser and does not use cookies. Clause 14.4 of the Privacy Policy describes what it does use, and this is the detail behind it.

Firebase Analytics and crash reporting, from Google. This uses a device identifier to count sessions, to see which screens are used, and to tell us when the app has crashed. You can reset the identifier at any time in your device’s own settings — on iOS, Settings, and on Android, Settings, Google, Ads — and the app will start counting again from a new one.
No advertising identifier. The iOS advertising identifier (the IDFA) was deliberately removed from the app. The app does not ask for tracking permission because it has nothing to track you with.
No advertising or attribution SDKs at all. We audited the app for them and there are none: no AdMob, no Facebook SDK, no AppsFlyer, no Adjust, no Branch, no Amplitude, no Mixpanel, no Segment.

6. How to control all of this

On the website

Clearing cookies and site data for cherie.social in your browser removes everything in sections 2 and 3 at once. You will be signed out and an unfinished questionnaire will be lost.
Every major browser lets you block or delete cookies per site — in Chrome, Safari, Firefox and Edge it is under Privacy or Site settings. Blocking the cookie in section 2 will not stop you browsing, but it will stop an administrator being able to sign in to the internal console, and blocking Stripe’s cookies will stop a payment going through.
Private or incognito browsing throws all of it away when you close the window.
Browsers cannot be used to switch off something that is not running, so there is nothing on this site you need to opt out of today.

In the app

Reset the device identifier in your device settings, as described in section 5.
iOS: Settings, Privacy & Security, Tracking and Analytics & Improvements. Android: Settings, Google, Ads.
Deleting the app removes its local data. Deleting your account is separate — see the Privacy Policy for how to do that and what we keep afterwards.

7. Changes to this page

If we add a cookie, or switch on anything described in section 4, we will update this page before the change goes live, not after. Previous versions are kept at cherie.social/legal/archive, and the date at the top of this page tells you when it last changed.

8. Contact

If something on this page does not match what you see in your own browser, tell us — that is a bug and we want to know. Email hello@cherie.social, or write to Chérie Social, Inc. at the address in our Privacy Policy.