Privacy Policy

Last updated: 27 August 2026

This policy explains what the Finally Some Good.News website (finallysomegood.news) and the Finally Some Good.News Android app do with data about you. The two share a codebase and a news feed, so one policy covers both — passages that apply to only one platform are marked Website or App.

1. Who is responsible

The Finally Some Good.News website and Android app are published by an individual developer based in the Czech Republic. For the purposes of the EU General Data Protection Regulation (GDPR) and the UK GDPR, that person is the "data controller" for the limited processing described here.

You can reach the publisher at [email protected]. There is no separately appointed data protection officer; privacy questions go to that address.

2. What we don't collect

To be clear about the baseline, the website and the app do not: Website + App

• have user accounts, logins, profiles, or a sign-up of any kind;
• ask you for your name, email address, phone number, date of birth, or any other identifying detail;
• collect your GPS location or precise location;
• run a first-party analytics product (there is no Google Analytics tag, no tracking pixel, and no custom event logging that we operate);
• read your contacts, photos, files, camera, microphone, or calendar;
• sell, rent, or trade data about you to anyone;
• build our own advertising or behavioural profile of you across sites or apps.

The website stores nothing on your device other than what Google's advertising code sets (see below). It sets no cookies of its own, uses no localStorage, and has no "remember me" state. Website

3. What is collected, and by whom

Server request logs Website

Like every website, finallysomegood.news is served by a hosting provider whose servers automatically record standard technical information for each request: your IP address, the page or file requested, the time, the referring page, and your browser's user-agent string. These logs exist for security, abuse prevention, and basic traffic troubleshooting. They are held by the hosting/CDN provider, are not combined with anything else, and are not used to identify you as a person.

The app fetches its news data as a plain file (feed.json) from the same host, which produces the same kind of log entry. App

Data collected by Google Play App

When you install and run an app from the Google Play Store, Google automatically collects certain information regardless of what the app's own code does — for example app installs, uninstalls, crashes, and aggregate performance and device data. This collection is governed by Google's Privacy Policy and the Play Store terms, not by us, and we receive only aggregated, non-identifying reports from it in the Play Console.

Advertising identifiers and cookies

Google's advertising services collect data to select and measure ads. On the website that is done with cookies and similar browser storage; in the app it is done using the device's resettable advertising ID. Details, and how to limit or switch this off, are in the next section. Website + App

4. Advertising

Both platforms are supported by advertising. We do not operate an ad server or a data-management platform; we embed Google's, and Google acts as an independent controller for the ad data it collects.

On the website: Google AdSense Website

The feed page shows ads served by Google AdSense. Google and its ad-technology partners may set and read cookies and similar identifiers in your browser to serve ads, cap how often you see the same ad, detect fraud and invalid traffic, and — where permitted — personalise the ads you see and measure their performance. How Google uses this data is described in "How Google uses information from sites or apps that use our services".

In the app: Google AdMob App

The app shows ads served by Google AdMob. AdMob uses your device's advertising ID and related technical data to serve ads, limit repetition, detect invalid activity, and — where permitted — show personalised ads and measure them. In its current configuration the app is set up to allow personalised ads where you have not opted out or declined consent. Google's handling of this data is described in the same document linked above and in AdMob's data-disclosure guidance.

Your choices about ads

• EEA and UK — consent. Before any personalised advertising or non-essential ad storage takes place, you are shown a consent request (Google's certified consent mechanism / a consent banner). You can refuse; if you do, ads are still shown but are non-personalised, and only the storage strictly needed for that and for fraud prevention is used. You can change your choice later — on the website by clearing the site's cookies and reloading, and in the app via the app's privacy/consent option in settings where offered, or by reinstalling. Website + App
• Website ad settings. You can review and turn off ad personalisation for your Google account at myadcenter.google.com, and opt out of personalised advertising from many vendors at optout.aboutads.info and youronlinechoices.eu. Website
• App advertising ID. In Android Settings → Privacy → Ads you can "Delete advertising ID" (after which apps can no longer use it for ads) or reset it and opt out of ad personalisation. App

5. Diagnostics and crash reporting

To find and fix bugs, the app may report crashes and basic technical diagnostics (for example the device model, Android version, and a stack trace) through Google's standard developer tooling — at minimum the crash reporting built into Google Play, and possibly Google/Firebase crash reporting. This data is tied to a random, app-scoped identifier rather than to you, is used only to keep the app working, and is not used for advertising. It is processed under Google's Privacy Policy. App

6. Other third-party services and content

Displaying a global news feed means your device talks to servers other than ours. In each case that third party receives your IP address and user-agent simply because your browser or the app is making the request; we don't send them anything extra.

• Google Fonts. The website loads its typefaces from Google's font CDN (fonts.googleapis.com / fonts.gstatic.com), so Google receives the request for those files. Website
• Article thumbnail images. Story thumbnails are loaded directly ("hotlinked") from each news outlet's own servers — they are never copied onto our host. When a thumbnail loads, that outlet's server sees your IP address and user-agent. We don't control those outlets or their privacy practices. Website + App
• Outbound links to articles. Opening a story sends you to the publisher's own website, which has its own privacy policy. For stories not in English, the "read" link routes through Google Translate (translate.google.com) to provide an English rendering; that request is handled by Google. Website + App
• Hosting and CDN provider. The static files are served by a third-party hosting/CDN provider that processes the request logs described in section 3 on our behalf as a processor. Website
• Google Play. Distribution of the app, and its update mechanism, run through the Google Play Store. App

7. App permissions

The app requests only network access (INTERNET / network state), which it needs to download the news feed, thumbnails, and ads. It does not request location, storage, camera, microphone, contacts, phone, or SMS permissions. App

8. Legal bases for processing (GDPR)

Where the GDPR or UK GDPR applies, the processing above rests on these legal bases:

• Legitimate interests (Art. 6(1)(f)) — keeping the service running and secure: server request logging, abuse and fraud prevention, crash diagnostics, and serving non-personalised ads with basic frequency capping. You may object to processing based on legitimate interests (see "Your rights").
• Consent (Art. 6(1)(a)) — personalised advertising and any storage of, or access to, information on your device that is not strictly necessary. This is collected through the consent request shown in the EEA and UK, and you can withdraw it at any time with future effect.

Google independently determines the legal basis for its own further use of ad and diagnostics data as a separate controller.

9. How long data is kept

We do not maintain our own database of users or events, so there is nothing on our side to retain. Server request logs are kept by the hosting/CDN provider for a short period (typically a few weeks) for security and troubleshooting, then rotated out. Google retains ad, Play, and diagnostics data according to its own retention schedules, described in Google's Privacy Policy and its data retention page.

10. International data transfers

Google is headquartered in the United States and processes data globally. When Google receives data through the advertising, Play, fonts, translation, or diagnostics services described above, it may transfer that data outside the EEA/UK. Google states that it relies on the European Commission's Standard Contractual Clauses and equivalent safeguards for those transfers; see Google's ads services data transfer information. The hosting provider for the website may also process request logs outside your country under comparable safeguards.

11. Your rights

If you are in the EEA, the UK, or another region with comparable law, you have the right to request access to, correction of, deletion of, or restriction of your personal data; to object to processing based on legitimate interests; to data portability; and to withdraw any consent you have given.

An important practical point: because we hold almost no information that identifies you (see section 2), we usually cannot single you out in the little data we do have, and the GDPR does not require us to collect more just to enable a request (Art. 11). For most of the data covered by this policy — advertising data, Play data, diagnostics — Google is the controller, so requests about that data are best made to Google directly through your Google Account and My Ad Center. We will still help where we can — write to [email protected].

You also have the right to lodge a complaint with a data protection authority. The publisher's lead authority is the Czech Úřad pro ochranu osobních údajů (ÚOOÚ); you may also complain to the authority in your own country of residence.

12. Children

Neither the website nor the app is directed to children, and we do not knowingly collect personal data from children under the age of 16 (or the applicable age of digital consent in your country). The app is rated and distributed accordingly on Google Play. If you believe a child has provided personal data, contact us and we will address it.

13. Security

The website and the feed are served only over HTTPS. Because there are no accounts and no user-submitted data, there is no user database to breach on our side. Third-party providers (Google, the hosting provider) maintain their own security programmes for the data they hold.

14. Changes to this policy

This policy may be updated as the site or app changes — for example if the ad configuration changes or a new service is added. The "Last updated" date at the top always reflects the current version. For a significant change affecting how your data is used, we will make the update prominent (for example a notice on the feed page or in the app) before it takes effect where required.

15. How to contact us

For any question about this policy or about your data, email [email protected]. The publisher is an individual developer based in the Czech Republic; a postal address for formal data-protection correspondence is available on request.

This document is provided for transparency and to meet Google Play and Google AdSense/AdMob disclosure requirements. It is not legal advice. — Finally Some Good.News · Feed · Support