← Back to news

Privacy policy

This notice covers the PressRadar website at pressradar.net.

Account and sign-in

For registration we process an email address, display name and, for password accounts, a one-way password hash. We record the registration method and date, email verification, account status and role, and the last sign-in time. You can read public news without an account.

Google sign-in provides a provider account identifier, name and email address where available. We do not receive your Google password or request access to your mail, contacts or posting permissions. Google access tokens are not kept permanently in our account database.

Sign in with Apple provides an Apple account identifier and, when supplied, your name and email address. If you choose Hide My Email, we receive Apple's relay address instead of your personal address. We store the provider identity and an encrypted Apple refresh token to manage authorization and revoke it when deleting the account. We do not receive your Apple password. Apple or Google sign-in takes place in the provider's browser authentication flow, with a short-lived, single-use return code to the app.

Your selected countries, categories, sources, custom source URLs, keyword groups, saved articles, reactions, recent searches and appearance/language choices support your personal news feed. Recent account search history is limited to 20 entries and can be cleared from the search interface. Language and country suggestions and source requests may also be saved. These private choices are not published to other readers.

We use these data to provide the requested account and personalized service (GDPR Article 6(1)(b)). Necessary account data are required to register; account features are optional.

Security, usage and support

Sign-in security records include attempt time, success or failure, an email hash and IP address. Sessions include a browser/app user-agent and expiry. Rate limits use time-limited hashed identifiers. The application also records search text, filters and whether there were results, and counts original-article openings; those operational search and click records have no account identifier. Separate personal search history is linked to your account. Server logs can contain IP addresses and technical request information. Administrative changes have audit records.

These operations help prevent misuse, diagnose errors and maintain the service, based on legitimate interests (Article 6(1)(f)). You may object. We do not use an independent third-party analytics SDK in the iOS app.

Contact forms collect the name, email, topic and message you submit. Messages are sent to the operator's designated mailbox through the configured mail service; the application does not maintain a separate message-body database. Support uses legitimate interests; handling data-rights requests also fulfils legal obligations (Article 6(1)(c)). Do not send passwords or unrelated sensitive data.

Weather and location

The five-day forecast uses Open-Meteo. We request foreground device location only after your browser or operating system grants permission. No background location tracking takes place. You can refuse or withdraw permission in your browser or device settings and continue reading news.

Before transmission, coordinates are rounded to two decimal places. Our server sends this approximate location to Open-Meteo, which sees our server's IP address, not your device IP. We cache a forecast for one hour and share that cache across readers without account IDs or personal location history. Its technical cache key is derived from the rounded location; raw coordinate fields and reader IPs are not stored in the forecast cache. We retain a bounded cache and reuse the forecast in your current browser/app session for up to an hour.

Your device sends the rounded coordinates directly to BigDataCloud to resolve the place name and country, so that provider also receives your network IP. BigDataCloud may associate location and IP signals to improve its geolocation service. The country selects an initial Celsius/Fahrenheit unit; you can change it. We do not send account details to either weather provider. Location processing for this optional feature uses your consent (Article 6(1)(a)). See Open-Meteo terms and privacy information and BigDataCloud privacy information.

Cookies and device storage

  • Offline reading: the device caches interface files, previously downloaded news and images (news expires after five days), and the signed-in profile. Profile changes made offline stay on this device and are sent only to the same account after reconnection and, when necessary, renewed sign-in. Passwords, payment actions and account deletion are not queued. Signing out clears the local account cache and pending changes; changing accounts isolates their data. The operating system may remove cached files when storage is low.
  • hr_session, hr_native_session: Used for sign-in and form protection. In the mobile app, sign-in does not expire because of time or inactivity, including for administrators. Logout and security revocation still end it. hr_native_session marks the mobile session retention mode; it does not grant access by itself. In a browser, reader sessions renew for 30 days during active use, at most once every five minutes, and expire after 14 days of inactivity. Browser administrator sessions expire after 12 hours or two hours of inactivity.
  • hr_visitor: a random guest identifier, lasting up to one year, used to distinguish reactions. Guest reactions may be linked to your account on sign-in.
  • hr_lang: interface language, up to one year. Local storage also remembers theme, onboarding, temperature units and guest search history.
  • Reading position: this browser remembers selected feed filters and positions for up to 64 lists. Forecast data and place name are held for at most one hour in session storage; coordinates are not stored there.
  • hr_delete_receipt: a private deletion-status receipt, valid for up to 30 days and limited to the deletion page.

You can clear site/app data in your device or browser settings. This may remove remembered choices and sign you out. Completing account deletion clears the application's local reading and preference storage in the browser/app where you open its completion page; you can clear data separately on other devices. Guest data on the device can also be removed this way.

Subscriptions, advertisements and other providers

The website and email infrastructure runs on a Contabo VPS in Europe. Contabo provides the infrastructure and processes the data needed to operate it.

Web subscriptions use Stripe; Android subscriptions use Google Play. Their services receive the information needed to identify and verify the purchase. Our server stores provider customer, checkout or purchase identifiers, subscription state and paid period, and, for Google Play, protected purchase tokens and a pseudonymous account reference. We do not store payment-card numbers. Test purchases are distinguished from real purchases. Closed financial records may remain detached from the deleted account for payment reconciliation and misuse prevention.

The current iPhone/iPad version does not offer Apple in-app purchases and does not load advertisements or an advertising SDK. Existing server-confirmed account entitlements can be displayed. This version does not use data for cross-app advertising tracking or request Apple's advertising identifier.

The website and Android app may show Google AdSense advertisements to eligible readers; Android also integrates the Google Mobile Ads WebView connection. These Google services may process IP and approximate location, device or advertising identifiers, interactions and diagnostics for advertising, measurement and fraud prevention. This is separate from the ad-free iOS version. See Google privacy information and Google Mobile Ads data disclosures. Stripe information is available in its privacy policy.

Hosting and email providers process data necessary to deliver the service. Gmail may process messages received in the operator's mailbox. Google Fonts receives network request information when fonts load. Google and Apple apply their own policies during sign-in; see Apple privacy information. Providers may process data outside the EEA; their notices describe locations and transfer safeguards. Opening an original article loads the publisher's website under its own privacy practices. Sharing opens your device's share options; we do not choose recipients or send on your behalf.

Retention

Account data and preferences remain until deletion. Saved items and reactions may also disappear when the related article expires. Registration links last 24 hours; used requests are removed, and expired requests are cleaned up during later authentication activity. Sign-in attempt logs have a seven-day deletion threshold; operational search and click logs have a 32-day threshold. Actual cleanup runs in bounded batches. A completed deletion receipt contains status and dates without the account link and expires after 30 days. Pending requests remain until handled.

Support correspondence and legally necessary payment/security records are retained for the relevant purpose or obligation. Expiry of a session is not necessarily immediate physical erasure. Residual backups and infrastructure logs follow the operator's retention arrangements rather than the live account-deletion transaction; contact us for details about retained data and applicable periods. We do not claim that deleting a live account erases a provider's independent records.

Delete your account and personal data

Open Profile → Account → Delete account in PressRadar or use the direct deletion page. Sign in, review the consequences and confirm. Password accounts also require the current password. No support message or reason is required. This deletes the shared web, Android and iOS account, not just the copy on one device.

Most accounts are deleted immediately. If a payment, Apple authorization or administrator role needs attention, the request is recorded for manual completion within 30 days, without a separate support request. The deletion page displays status and we attempt to send email confirmation. Administrators see the pending queue. The request is not postponed automatically until a subscription expires.

Deletion removes account sign-ins, provider identities, encrypted Apple grants, preferences, personal feed requests/subscriptions, saved articles, reactions and personal searches. Apple authorization is revoked before the Apple-linked account is deleted. Shared publisher articles are preserved. Your Google or Apple account itself is not deleted. Revoking the provider's authorization alone does not delete the PressRadar account.

Account deletion or uninstalling the app does not cancel provider subscriptions. Manage Google Play subscriptions in the Play Store and web subscriptions in Ad-free. You can submit the deletion request even while a payment needs attention. For partial data deletion, lost access or another privacy request, use Contact.

Data controller

Géza Fodor
Andrássy út 83-85. I/15A.
1062 Budapest
Hungary

For privacy enquiries, email hello@pressradar.net or use Contact.

Your rights

Under the applicable GDPR conditions, you can request access, correction, erasure, restriction and portability, object to processing based on legitimate interests, and withdraw consent without affecting earlier lawful processing. We do not make solely automated decisions with legal or similarly significant effects about you. Contact us through Contact. We normally respond within one month. You can complain to the Hungarian National Authority for Data Protection and Freedom of Information or your competent supervisory authority, and seek a judicial remedy.