Privacy

Cookie Policy

Effective 6 September 2026

Short version: one analytics cookie, no advertising, and a switch on this page that turns it off. The rest of this document is the detail behind that sentence.

Contents

1.What we use, in one paragraph
2.The full list
3.What we do with it
4.Turning analytics off
5.Third parties that see a request
6.Changes and contact

1What we use, in one paragraph

This site sets one first-party analytics cookie, from PostHog, and stores a few related values in your browser's local storage. That is the entire list. There are no advertising cookies, no social media pixels, no cross-site trackers, and nothing that follows you to other websites.

In the EU, the UK and the EEA, we ask first.

If you are visiting from a country whose law requires consent, the analytics cookie is not set until you accept it in the banner. Nothing loads while that banner is waiting — the analytics code is not on the page at all, rather than loaded and told to stay quiet. Everywhere else analytics run by default, and section 4 turns them off in one click.

Cookies are small files a site stores in your browser so it can recognise the same browser on a later page or a later visit. Local storage does the same job with no expiry date. We treat both the same way in this policy, because from your point of view they are the same thing.

2The full list

Name	Set by	Purpose	Expires
`ph_<project key>_posthog`	PostHog (first-party)	Holds a random visitor ID and the current session ID, so a visit reads as one journey rather than a pile of unconnected page views.	12 months
`ss_consent`	SettleScout	Remembers whether you accepted or declined analytics, so we neither ask again on every page nor load anything you refused. Strictly necessary: without it your answer would not survive the next click.	12 months
PostHog local storage keys	PostHog (first-party)	The same visitor and session values, kept in local storage so they survive a browser that restricts cookies.	Until cleared

The random visitor ID is not your name, your email address, or anything you have told us. For ordinary visitors we do not build a profile at all — we count page views and journeys, not people.

3What we do with it

Three questions, and nothing beyond them:

Which settlement pages people actually read, so we know what to write more of.
Which pages lead someone to download the app. Every store button on the site passes through a redirect on our server that records the click, which is why that number holds up even when a browser blocks the cookie.
Where the site is broken or confusing enough that people leave.

We do not sell this data, we do not share it for advertising, and we do not join it to data about you from anywhere else.

If you decline, we still count the second one — but as an anonymous tally with a throwaway identifier, not as something joined to you or to the pages you read. We learn that a download happened; we learn nothing about who.

4Turning analytics off

This is the same choice the banner offers, and it overrides whatever you answered there. It takes effect immediately and needs no reload: turning analytics off stops the current session and deletes the identifiers already stored, and on your next visit the analytics code is not loaded at all.

You can also block cookies in your browser's settings, or use private browsing, or an ad blocker — all of them work here, and none of them break the site. Nothing on settlescout.app requires a cookie to function: there is no login, no basket, and no preference we need to remember.

Turning analytics off does not affect the app.

The SettleScout mobile app does not use cookies. It has its own analytics, described in the Privacy Policy, and its own controls in your device settings.

5Third parties that see a request

Two other companies see that your browser asked for something, without receiving a cookie from us:

Google Fonts serves the typeface this site is set in. Loading it means Google receives your IP address and browser details. It sets no cookies.
Vercel hosts the site and keeps standard server request logs, as any web host does.

Links out to settlement administrators, courts and the app stores lead to sites we do not run. Once you are there, their cookie policies apply, not ours.

6Changes and contact

If we ever add a cookie, this table is where it will appear, and the effective date at the top will change with it. Questions go to support@settlescout.app. Related reading: the Privacy Policy for everything outside your browser, and Delete My Data to have your records erased.

Questions about this document?

Write to support@settlescout.app. SettleScout is operated by NICE DIJITAL TEKNOLOJILER YAZILIMLARI, a company registered in Türkiye.