Privacy Policy

This policy covers two things: the SettleScout mobile app for iOS and Android, and this website at settlescout.app. Where the two differ, we say which one we mean.

The data controller is NICE DIJITAL TEKNOLOJILER YAZILIMLARI, a company registered in Türkiye, contactable at support@settlescout.app.

It does not cover the settlement administrators, courts, or law firms we link to. Once you follow a link to an official claim form you are on someone else's site, under their privacy policy.

In the mobile app

• Claim details you type — full name, email address, phone number, mailing address, and any proof-of-purchase description, together with which settlements you filed for and their status.
• A random device identifier generated on first launch. It is not derived from your hardware and is never shown to you. Every claim and notification registration is keyed to it.
• Push notification token, if you opt in, along with your selected country, your brand selections and your subscription flag.
• Subscription status and purchase history, through RevenueCat. Alongside it, RevenueCat stores the vendor identifier your device reports (Apple's IDFV or Android's ID) and the IP address the request came from, so a purchase can be matched back to the right customer.
• Product analytics — screens opened, settlements viewed, and subscription events, tied to the random device identifier.
• App version and platform (iOS or Android).

Your onboarding answers — country, age range, gender and brand selections — are stored only on your phone. They are not sent to our servers, and deleting the app removes them. The single exception is the country and brand list attached to a push registration, which we need in order to send you the right alerts.

On this website

• Analytics about pages viewed — the page URL, the section of the site, the referring page, and how long the page was open. This is anonymous by default: we do not build a profile for ordinary visitors. In the EU, the UK and the EEA none of it runs until you accept the cookie banner.
• App-store redirects. Every store button on the site passes through /download so we can count how many visitors tried to get the app and which page sent them. This is recorded on our server rather than in your browser, so an ad blocker does not distort the count.
• Partner applications. If you apply to the partner programme, we receive the name, email address, platform, audience size and message you type into that form.
• One first-party analytics cookie, plus one that records your answer to the cookie banner. See the Cookie Policy, which lists both and carries a switch that turns analytics on or off wherever you are.

You do not need an account to use the app or the website. There is nothing to log into.

What we never collect

• Your location, contacts, photos, calendar, or microphone.
• The advertising identifier. SettleScout does not show an App Tracking Transparency prompt because it has nothing to ask for: none of your data is joined to data from other companies' apps or websites.
• Passwords — there are no accounts.
• Your browsing history outside settlescout.app.

The consequence matters, so it is worth being blunt about it. The name, email, phone number and address you enter in the SettleScout app are stored on our servers only, so that the app can show you your claim history and alert you when a settlement you filed for starts paying out. We do not transmit them to a settlement administrator, and we could not withdraw or correct a claim on your behalf even if you asked us to — that has to go to the administrator directly.

It also means uninstalling the app does not erase those details. Only a deletion request does that.

• To match you with settlements based on your country and the brands you selected.
• To show you the claims you have filed and their status.
• To send push notifications about new settlements and approaching deadlines — opt-in only, and capped so that a busy week does not turn into a stream of alerts.
• To run and bill subscriptions.
• To understand which parts of the app and site are used and which are ignored, so we know what to build and what to fix.
• To answer your support emails.
• To detect and prevent fraud and abuse, and to comply with the law.

We do not use your data to make automated decisions that produce legal effects for you, and we do not profile you for advertising.

Legal bases (UK and EU visitors)

• Performance of a contract — storing your claims, running your subscription, giving you the service you asked for.
• Consent — push notifications, and analytics cookies on the website. You can withdraw either at any time, without affecting anything done before.
• Legitimate interests — product analytics, security, fraud prevention, and keeping the service working. We have weighed these against your rights and use anonymous or pseudonymous data wherever the answer does not require more.
• Legal obligation — billing and tax records.

We do not sell your personal information, and we never have. We do not share it for cross-context behavioural advertising. We use the following service providers, each bound to process data only on our instructions:

We may also disclose information where the law requires it, or where it is necessary to establish, exercise or defend legal claims — and to a buyer, along with the rest of the business, if SettleScout is ever sold. You would be told before that happened.

• Onboarding preferences — on your device only, until you uninstall.
• Claim details — up to three years after the claim period for that settlement closes, because payouts routinely arrive a year or more after filing and you may need to show what you submitted.
• Push tokens — while active. When a token is rejected as invalid, we remove it.
• Analytics — retained by PostHog under their retention policy.
• Subscription and billing records — as long as tax and accounting law requires, which is longer than the rest and outside our discretion.
• Support email — two years from the last message in the thread.

Data is encrypted in transit with TLS and at rest by our hosting providers. Access to the production database is limited to the people who need it to operate the service.

Our servers and our providers are located primarily in the United States, and we operate from Türkiye. If you use SettleScout from the UK, the EEA, or anywhere else, your information will be transferred to and processed in those countries. Where the law requires a transfer mechanism, we rely on the European Commission's Standard Contractual Clauses (and the UK Addendum) with our providers.

No system is perfectly secure. If a breach affects your personal data and presents a real risk to you, we will tell you and the relevant regulator within the deadlines the law sets.

Wherever you are, you can ask us to:

• tell you what we hold about you, and give you a copy;
• correct anything that is wrong;
• delete it — see Delete My Data, which explains exactly what goes and what cannot;
• restrict or object to how we use it, including analytics;
• port it to another service, where that right applies;
• withdraw consent for notifications or cookies at any time.

Email support@settlescout.app. We acknowledge every request within 7 days and complete it within 30. There is no charge, and you never have to explain why.

If you are in the UK or the EEA

You may lodge a complaint with your local supervisory authority. We would rather you came to us first, but that right is yours regardless.

If you are in California

You have the rights to know, delete, correct, and to opt out of sale or sharing. There is nothing to opt out of: we do not sell or share personal information as the CCPA defines those terms, and we do not process it for cross-context behavioural advertising. We will never discriminate against you for exercising a right.

SettleScout is for adults. You must be 18 or older, or the age of majority where you live, to use it. We do not knowingly collect information from children, and if we learn that we have, we delete it promptly. If you believe a child has given us data, write to support@settlescout.app.

We update this policy when what we do changes. The effective date at the top always reflects the current version. For a material change — a new category of data, a new purpose, a new recipient — we will give notice in the app before it takes effect, rather than relying on you to re-read the page.