Anything you do with other people. A coffee, a run, a walk, a picnic, a pub night, a book club. If it's a real-world plan, it's a Happening.

How does LetsLoop know what to show me?

Your Home feed mixes Happenings from communities you've joined, interests you've picked, and people you've previously looped with. Your Map view shows whatever's nearby right now.

Is LetsLoop actually free?

Yes, forever. No subscription, no premium tier, no paywall. Future revenue comes from ads, event sponsorships, and optional in-app extras — none of which gate the core product.

Where does LetsLoop work?

London first, then expanding. We seed each new area with real, recurring Happenings before launching so the feed isn't empty when you arrive.

Identity is real, not anonymous. You see hosts' history and attendance before joining. Privacy zones hide your home and work. You can mute, block, and report in one tap. Per-Happening filters (e.g. women-only) are organiser-set.

Can I post my own Happening?

Yes. Three taps to create. No event-management overhead. People you'd want there see it; people you wouldn't, don't.

Last updated: 2026-05-25 · Version 2.0

Cookie Policy

Last updated: 2026-05-25

Version: 2.0

1. What Cookies Are

Cookies are small text files placed on your device (computer, phone, tablet) when you visit a website or use a web app. Similar technologies — such as local storage, SDK identifiers, pixels, and session-replay scripts — work in comparable ways. In this Policy we use "cookies" to refer to all of these technologies.

This Cookie Policy explains which cookies LetsLoop Ltd ("LetsLoop", "we", "us") uses on letsloop.app and within our web application, why we use them, and how you can control them.

This Policy should be read alongside our Privacy Policy.

2. Why We Use Cookies

We use cookies to:

keep you signed in and your session secure;
remember your preferences (for example your cookie-consent choices);
understand how people use the Service so we can improve it (with your consent);
detect and prevent fraud and abuse.

We do not use any advertising or retargeting cookies. We do not currently run paid advertising and we do not share device identifiers with advertising networks.

3. Categories of Cookies We Use

We group cookies into three categories, consistent with ICO guidance.

3.1 Strictly necessary

These are required for the Service to function. Without them, core features like signing in or submitting a form will not work. They do not require your consent.

Examples:

Authentication and session cookies (set by our application)
CSRF and security cookies
Consent-state cookie — remembers your cookie choices so we do not ask you again on every visit

3.2 Functional

These remember choices you make to give you a better experience (for example interface state). They are set only with your consent.

3.3 Analytics

These help us understand how the Service is used — which pages people visit, where they get stuck, how features perform. They are set only with your consent.

Our current analytics stack:

PostHog (EU Cloud — Frankfurt, Germany) — product analytics, session replay, and feature flags. Sets cookies and uses local storage to identify a returning device. Loaded only after you grant analytics consent.
Vercel Analytics (operated by Vercel Inc.) — privacy-preserving traffic measurement. Does not use cookies and does not persist identifiers; the data is aggregated at the edge.
Sentry (Functional Software, Inc.) — error and crash reporting. Sentry's browser SDK does not set cookies but does collect technical context (browser, OS, URL, stack trace) for crash diagnostics. We treat this as a strictly-necessary integration because it is essential to running a reliable service; you can disable it by blocking the Sentry script in your browser or by emailing privacy@letsloop.app.

4. Managing Cookies

You can manage cookies and similar technologies in two places:

In-product cookie banner — when you first visit, we ask which categories you allow. You can change your choices at any time by clicking "Manage cookie preferences" on this page or in our Privacy Policy.
Your browser settings — most browsers let you block or delete cookies. Note that blocking strictly-necessary cookies will prevent the Service from functioning.

If you have previously consented and want to withdraw consent, click "Manage cookie preferences" at the top of this page or email privacy@letsloop.app.

5. Mobile Apps

Our mobile apps do not use browser cookies. They use platform identifiers and local storage in line with the iOS / Android operating system rules. Where mobile analytics or push-notification SDKs are loaded, we describe them in our Privacy Policy.

6. Third-party Cookies

We do not set third-party advertising or social-network cookies (no Meta Pixel, no Google Ads tags, no TikTok pixel, no LinkedIn Insight Tag). The only third-party scripts we load are the ones listed in Section 3.3, and they are loaded only with the relevant consent.

7. Changes to This Policy

If we materially change which cookies we use we will update this Policy and re-prompt you to consent. The "Last updated" date at the top of this page shows the most recent revision.

8. Contact

Questions about cookies or this Policy: privacy@letsloop.app

LetsLoop Ltd 71-75 Shelton Street, London WC2H 9JQ, United Kingdom Company number 17178512 (registered in England and Wales)