Yappa

Cookie Policy

The cookies we use and how consent controls analytics.

Last updated: 18 June 2026

This Cookie Policy explains how Precise Impact Ltd, trading as Yappa ("we", "our", "us"), uses cookies and similar technologies when you visit our website and use the Yappa application (the "Service"). We keep our use of cookies deliberately minimal: a small number of essential cookies that keep you signed in and remember your choices, and optional analytics cookies that are loaded only if you accept them.

1. What are cookies?

Cookies are small text files that a website stores on your device (computer, tablet, or mobile phone) when you visit it. They are widely used to make websites work, to keep you signed in, to remember your preferences, and to give site owners aggregate information about how the site is used.

We also use a few similar technologies, such as your browser's local storage and tags loaded through a tag manager. Where these behave like cookies, we describe them in this policy too. Throughout this document, "cookies" is used as shorthand for cookies and these similar technologies unless we say otherwise.

2. Your cookie choices

When you first visit the Service you will see a cookie banner. Essential cookies are always on because the Service cannot function without them, so the banner is about the optional categories. It gives you a clear choice:

  • Accept analytics: essential cookies plus the optional analytics (and any marketing) cookies are enabled.
  • Reject: only the essential cookies are used. No analytics or marketing tags are loaded, and none of their cookies are ever created.

Analytics is strictly opt-in. Nothing analytics-related runs, and no analytics cookies are set, until you actively accept analytics in the banner. Your choice is remembered in a first-party consent cookie so we do not have to ask you again on every visit. You can change or withdraw your consent at any time, see Section 6.

3. Cookies we use

3.1 Essential cookies (strictly necessary)

These cookies are required for the Service to work and do not need your consent. They keep you signed in, secure your session, and remember the consent choices you have already made. Without them, you could not log in or stay logged in, and the consent banner would reappear on every page.

Name Purpose Type Duration
yappa_consent Stores your cookie-consent choices so the banner is not shown on every visit and so analytics is only loaded if you opted in. First-party 12 months
Session / authentication cookie Keeps you securely signed in to your Yappa account between page loads and protects your session. Cleared when you sign out. First-party Session / on sign-out
__cf_bm Set by Cloudflare, our network and security provider, to tell legitimate visitors apart from automated traffic and protect the Service. This is a functional security cookie. Third-party (Cloudflare) 30 minutes

3.2 Analytics cookies (optional, opt-in)

These cookies help us understand how visitors use the Service in aggregate so we can improve it. They are set only if you accept analytics in the consent banner. If you reject, they are never created.

We route all client-side analytics through a single Google Tag Manager (GTM) container. That container is consent-gated: its script is injected into the page only after you have accepted analytics. Before consent, GTM does not load, and neither do the tags it manages. Through that one container we load Google Analytics 4 (traffic and journey measurement) and Microsoft Clarity (anonymised usage and interaction insights). The cookies these set are listed below.

Name Purpose Type Duration
_ga Distinguishes individual users for Google Analytics 4. Third-party (Google Analytics 4) 2 years
_ga_<container-id> Maintains session state for Google Analytics 4. Third-party (Google Analytics 4) 2 years
_clck Set by Microsoft Clarity to persist a user identifier so usage metrics can be attributed across pages. Third-party (Microsoft Clarity) 1 year
_clsk Set by Microsoft Clarity to connect multiple page views into a single session. Third-party (Microsoft Clarity) 1 day

The Google Tag Manager container itself does not set its own tracking cookies; it is the delivery mechanism for the analytics tags above, and it loads only after consent.

3.3 Marketing cookies (optional, opt-in)

The Service does not currently set advertising or marketing cookies. If we add any in future, they will be treated as an optional, consent-gated category in the same way as analytics: loaded only through the consent-gated tag manager after you have agreed, never before, and always refusable from the banner. We will update this policy and the banner before introducing them.

4. How consent gating works

We do not rely on you closing the banner or on a default "accept". The technical default is the opposite of tracking:

  • On a fresh visit, only essential cookies exist. The analytics tag manager is not present on the page.
  • When you accept analytics, your choice is saved to the consent cookie and the Google Tag Manager container is injected, which then loads Google Analytics 4 and Microsoft Clarity.
  • If you reject, or have not yet chosen, no analytics or marketing script is added to the page and none of their cookies are written.

Because the tags are injected only on consent, withdrawing consent stops new analytics data being collected from your next page load.

5. Similar technologies (local storage)

In addition to cookies, the Service uses your browser's local storage. Local storage is not a cookie: it is not sent to our servers with every request and stays on your device unless the application reads it. We use it for essential, functional purposes such as keeping you signed in between page loads and remembering interface preferences (for example, layout or display settings) so the Service looks the way you left it.

You can remove this data at any time by clearing your browser's site data for the Service, usually found alongside the cookie controls in your browser settings. Doing so will sign you out and reset your interface preferences.

6. Managing your cookie preferences

6.1 Through our cookie banner

Your choice is recorded in the consent cookie. To change it later, re-open the cookie banner from the link in the site footer, or clear the Service's cookies in your browser so the banner appears again on your next visit. Withdrawing consent removes analytics from future page loads.

6.2 Through your browser

Most web browsers let you view, delete, and block cookies through their settings. Here are instructions for popular browsers:

6.3 Impact of disabling cookies

If you block all cookies and site data in your browser, the consent banner will reappear on each visit because your choice cannot be remembered, and signing in may not work because the Service cannot keep your session. Rejecting or blocking analytics and marketing cookies has no effect on the core functionality of the Service.

7. Third-party services

A small number of third parties may set cookies through the Service. We only allow analytics and marketing providers to do so after you have given consent. The third parties involved are:

  • Google (Google Tag Manager and Google Analytics 4) delivers and runs our consent-gated analytics. Google processes IP addresses to derive approximate location and does not store them with analytics data. See the Google Privacy Policy. You can also opt out of Google Analytics on any site with the Google Analytics Opt-out Browser Add-on.
  • Microsoft (Microsoft Clarity) provides anonymised usage and interaction insights, loaded only after consent. See the Microsoft Privacy Statement.
  • Stripe is our payment processor. When you go through checkout or manage billing, Stripe may set cookies for fraud prevention and to secure the payment flow. These are functional to completing a payment. See the Stripe Privacy Policy.
  • Cloudflare is our network, performance and security provider. Cloudflare may set functional cookies (for example __cf_bm) to protect the Service from malicious or automated traffic. See the Cloudflare Privacy Policy.

8. Data retention

  • Consent cookie: your consent choice is kept for up to 12 months, after which the banner will ask again.
  • Google Analytics 4: analytics identifiers and event data are retained in Google Analytics for up to 14 months, then automatically deleted.
  • Microsoft Clarity: usage data is retained in line with Microsoft's Clarity retention defaults, after which it is deleted.

9. Updates to this policy

We may update this Cookie Policy from time to time, for example if we add new features or change the analytics or other services we use. When we make changes, we will update the "Last updated" date at the top of this page. For significant changes, we will notify you through the Service or by email.

10. Contact us

If you have questions about our use of cookies, please contact us:

Precise Impact Ltd
Trading as Yappa
128 City Road, London, EC1V 2NX
United Kingdom

Email: privacy@getyappa.com

For more information about how we handle your personal data, please see our Privacy Policy.

Related policies