Privacy Policy

Effective 13 August 2026

What Solva does not collect

Solva does not collect, store, transmit or sell:

• the addresses of pages you visit, or any part of their content;
• your browsing or search history;
• your name, email address, phone number or postal address;
• your precise location;
• your contacts, photos, files, calendar or health data.

Why the blocking itself cannot see anything

Almost all of Solva's blocking is done by Safari content blocker extensions — the seven entries named Solva — Blocklist 1 to Blocklist 7. A content blocker hands Safari a list of patterns once, and Safari does the rest inside its own process. Those extensions are not told which pages you open, are not run while you browse, and have no network access — there is no channel through which browsing data could leave, and nothing collecting it in the first place.

Solva does not download filter lists while you use it. The rules ship inside the app and change when the app is updated through the App Store.

The eighth entry: Solva Main

The eighth Safari entry, Solva Main, is a different kind of extension and this section describes it separately, because the paragraph above does not apply to it. Some things a blocker has to do cannot be written as a pattern — removing a notice identified by its wording, or undoing a scroll lock left behind by an anti-blocker script. Solva Main exists for those, and to do them it has to run on the page.

Three things bound what that means for you:

• It runs only where you allow it, one site at a time. It does not ask for access to all websites. You grant a single site from the extension's popup in Safari, and it has no access to any site you have not granted.
• What it reads stays on the device. On a site you have allowed, it examines that page's text and elements in order to hide the ones that match its rules. That examination happens in Safari, in memory, and nothing about it is written down, kept after the page closes, or sent anywhere.
• It has no network access. It makes no requests of any kind. Its only channel is a message to the Solva app on the same device, asking two questions: are you switched off, and is this site on your exceptions list.

Its rules ship inside it and change only with an app update, exactly like the blocklists. It downloads and runs no code.

What the app does collect

Three things, all from the app itself and none from Safari.

• Crash reports. If Solva crashes, we receive the stack trace, the app's state at that moment, your device model and your iOS version. This is how a crash that happens on your phone becomes a fix in the next version.
• Which of Solva's own screens you open, and four named events: setup finished, rules rebuilt, the demonstration run, a tip completed. The event we send carries no amount and no product identifier.
• Completed purchases, measured by Google Analytics itself rather than by us: when a tip goes through, the SDK observes StoreKit and records the product, its price and the currency. We did not add this and we cannot see it separately from the rest; it is part of what the SDK does. It is why the App Store privacy label for Solva lists Purchase History.

These go to Firebase Crashlytics and Google Analytics for Firebase, on the app target only. They carry a Firebase installation identifier, which is a random value for this install — not your Apple Account, not your name, and not the advertising identifier: Solva does not link the SDK that reads it, so there is nothing to ask you for under App Tracking Transparency and nothing that can follow you into another company's app.

What is never in it: any address you have visited, any page content, anything typed into Safari, and any domain you have exempted or blocked in Site rules. Those live on your device and are not sent anywhere. The app is structurally incapable of knowing the first three — the extensions that see them are separate processes with no network access, and they do not contain this code.

Turning it off: Settings → Diagnostics & analytics. One switch, both services, effective immediately and on every launch afterwards.

Separately, iOS may offer to send Apple its own diagnostic report. That is Apple's mechanism, it asks your permission, and you can switch it off in Settings → Privacy & Security → Analytics & Improvements.

Purchases

Solva is bought once from the App Store, and it contains an optional tip. All payment is handled by Apple. We never receive your card details, and Apple's reporting to us is aggregate — we cannot tell who bought or tipped.

Who else is involved

• Apple — distribution, purchases, and (if you send one) the diagnostic reports iOS offers to share. Apple's own privacy policy applies.
• Google — Firebase Crashlytics and Analytics receive the crash reports and screen counts described above, under Firebase's privacy terms. Also our support address, which is Gmail, if you choose to write to us. Neither ever receives a page you visited.

There is no advertising network in Solva, no tracking SDK, and no data broker. Nobody can pay to be let through the blocker.

The one page the app loads

Solva has a screen called See it working. It opens a demonstration page on our own site, twice — once with blocking on and once with it off — and counts the requests each time. That page deliberately asks for about three dozen real advertising and tracking URLs, because a demonstration of blocking that used fake ones would prove nothing. With blocking on, none of those requests leave the device. With it off, those companies see a request the same way they would on any other website.

The page carries no advertising account, sells nothing and earns nothing. We receive no report from it: it is a static file, it sets no cookie of ours, and we do not log who opens it. Nothing about you reaches us from that screen, and it only runs when you open it.

If you email us

Solva can open your mail app with a broken-site report already written. Nothing is sent from the app: you see every word, you send it yourself from your own mail account, and you can delete any line first. The draft fills in the site you named, your app version, your iOS version, your device model, how many of Solva's extensions are switched on, how many rules are loaded, whether blocking is on or off, and which of the filter lists you have switched off — the things we would otherwise have to ask for, and the last one is usually the answer.

It does not include any address you have visited, and it does not include which language packs you use. Mail you send reaches us at a Google-hosted address, so Google handles it the way it handles any email; we keep it for as long as it takes to answer and to get the fix into the filter list.

How long anything is kept

Crash reports and screen counts are kept by Firebase under its own retention periods — crash data for 90 days, analytics for 14 months — and an email you chose to send us is kept for as long as it takes to answer. Your settings — the sites you have made exceptions for, the domains you have blocked yourself, which lists you switched on — live on your device and in your own iCloud backup if you use one. Deleting the app deletes them.

Children

Solva is not directed at children, and nothing it collects would identify anyone of any age: no name, no account, no advertising identifier, and no address you have visited.

Your rights

If you are in the EU, the UK, California or another region with data protection law, you have the right to ask what is held about you, to have it corrected, and to have it deleted. Because Solva holds nothing tied to an identity, there is in practice nothing to return — but write to us and we will confirm that in writing. Deleting the app removes everything Solva has ever stored, all of which is on your own device.

Changes

If this policy changes in a way that matters, the version shipped with the update will say so and the date at the top will change. Past versions stay available on request.

Contact

Questions, or a request under the section above: ovemora.support@gmail.com.