Privacy Policy – SnipeRadar

Effective date: 22 August 2026

1. Scope

This Privacy Policy explains how the controller processes personal data when you visit sniperadar.com (the “Website”), contact us, use a SnipeRadar mobile application (the “App”), or use the related API, subscription and notification services (together, the “Services”). It does not govern third-party websites, cryptocurrency exchanges or app stores that you choose to open through external links.

2. Data we process

2.1. Website data and server logs

When you visit the Website, the hosting infrastructure may automatically record technical request data. This may include your public IP address, the date and time of the request, the requested URL and HTTP method, the HTTP status, browser and operating-system information contained in the user-agent string, the referrer when supplied by your browser, and technical error or security events.

We use this information only to deliver the Website, diagnose errors, maintain availability and security, and detect abuse. We do not use server logs to build advertising profiles.

2.2. Messages you send us

If you contact us by email, we process your email address, name or signature if provided, the content of your message, attachments and the technical metadata needed to send and receive the message. A support message generated by the App may include the Support ID displayed in the App. Please do not include information that is not necessary for us to handle your request.

2.3. App installation, authentication and security data

The App uses a pseudonymous installation or device identifier to provide access, apply the correct service tier, manage a device-specific trial, secure the API and prevent abuse. These identifiers do not directly contain your name or email address, but may constitute personal data when linked with other information.

On Android, the App reads the Android system identifier commonly known as ANDROID_ID and transmits it to our API over an encrypted connection. Our backend converts it into a keyed cryptographic hash and stores the hash rather than the original Android identifier. Related records may include the platform, first- and last-seen timestamps, trial end time, access tier, app version, authentication state and security-verification status.

The Android App uses the Standard Play Integrity API to verify that protected requests come from the recognised, untampered App installed through Google Play on a genuine device. Google Play processes request data, App metadata, licence status and device-attestation information to return an integrity verdict. The App sends the encrypted integrity token to our backend, which asks Google Play to decode it. We retain the resulting status, relevant timestamps and limited anti-replay job metadata needed for security and auditability; our database is not designed to retain the raw integrity token or Google’s full response.

On Apple platforms, the App may process service-authentication tokens and Apple App Attest material needed to verify that requests originate from a genuine App installation. We use these data for the same access-control, security and anti-abuse purposes.

2.4. Subscriptions and purchases

Purchases and subscriptions are processed through the relevant app store’s in-app purchase system. Purchase history is processed only if you choose to obtain or restore a paid subscription.

For Google Play purchases, the Android App receives the subscription product identifier, purchase token and entitlement state through Google Play Billing. It stores the purchase token in protected local App storage so that access can be restored and sends the token, App version and pseudonymous device identifier to our API. Our backend validates the subscription with Google Play, may acknowledge a new purchase, and uses the returned payment, acknowledgement, expiry, cancellation or revocation status to determine whether Premium access is active. The backend is not designed to retain the raw Google Play purchase token as a permanent subscription database record.

For Apple purchases, we receive and process the product and entitlement status, transaction identifier and information needed to determine whether Premium access is active, expired or revoked. The App sends the transaction identifier and pseudonymous installation identifier to our API to validate and provide Premium access. When a purchase is initiated, the App may also supply Apple with a pseudonymous app-account token so that the purchase can be associated with that installation.

We do not receive or process your payment-card number or bank-account details. Google Play or Apple processes account, payment and purchase data under its own privacy terms.

2.5. Push notifications

If you allow notifications, the App uses Firebase Cloud Messaging (“FCM”) on Android and may use FCM together with Apple Push Notification service (“APNs”) on Apple platforms to deliver listing alerts. This processing may include an FCM registration token or APNs device token, Firebase installation data, App identifier and version, device and operating-system information, language, time zone and notification-delivery metadata.

For Android, our backend stores the FCM registration token against the pseudonymous device hash. The App may subscribe the installation to a BASIC or Premium topic so that an alert with the appropriate level of detail can be routed. FCM may also deliver a short-lived, device-specific security request that asks the App to repeat Play Integrity verification. Such a request contains technical job and anti-replay data, not the user’s payment details or message content.

Notification permission is optional and can be changed in your device settings. Turning off notification display does not by itself necessarily delete identifiers already held by the notification provider. You may request deletion of data controlled by us by contacting data@sniperadar.com.

2.6. App interactions and service requests

When you use calendar, listing, statistics, pre-generated AI Radar insight, refresh, authentication or subscription functions, the App sends the request needed to provide that function. Our API and security logs may process the requested endpoint, request time, pseudonymous device reference, access tier, App version, response status, public IP address and technical error or security information. We use these interactions only to provide requested App functionality, troubleshoot failures, protect the Service and prevent fraud or abuse. We do not use them to create an advertising profile.

The current Android version does not transmit free-form AI Radar questions because that feature is not enabled. Acceptance of the current EULA and Radar Score disclosure is stored locally on the device by document version. The App contacts our API to obtain and verify the current document versions so that a newly required version must be accepted.

2.7. Advertising status of the Google Play version

As of the effective date of this Policy, advertising is disabled in the Android version distributed through Google Play. That build does not request the Android advertising ID or Ad Services permissions, does not initialise the Google Mobile Ads SDK and does not load or display advertisements. If advertising is enabled in a future Android release, we will first update the App, this Policy and the applicable Google Play disclosures and consent mechanism.

2.8. User-initiated YouTube video playback

Some Website pages include a locally hosted video preview. The embedded YouTube player is not loaded and no connection to YouTube is made until you choose the play button. After that action, the player is loaded from YouTube’s privacy-enhanced domain, youtube-nocookie.com. Google and YouTube may then receive technical request data such as your IP address, browser and device information, referrer, and playback or interaction data, and may use browser storage under their own terms and privacy policy. We do not receive the player’s individual identifiers or your YouTube account information from YouTube.

4. Cookies, browser storage and analytics

On initial page load, the Website does not set optional cookies, use localStorage or sessionStorage, or run analytics, advertising pixels or cross-site tracking. Server access logs are not cookies and do not store information on your device. Fonts, stylesheets, icons and video preview images used by the Website are served from SnipeRadar-controlled origins. The YouTube player and its third-party requests are activated only after you expressly choose to play the video. If we introduce optional analytics, advertising or similar storage in the future, we will update this Policy and request prior consent where required before activating it.

External links are opened only when you choose to follow them; the destination then processes data under its own privacy policy. This includes links to app stores, exchanges and official listing announcements.

5. Purposes and legal bases

• Providing the App, API, subscription access and user-requested notification functionality: performance of a contract or steps requested before entering into a contract (GDPR Art. 6(1)(b)).
• Responding to support, privacy and service enquiries: performance of a contract where the enquiry concerns the Service (GDPR Art. 6(1)(b)); otherwise our legitimate interest in responding and maintaining business correspondence (GDPR Art. 6(1)(f)).
• Operating and securing the Website and API, verifying App and device integrity, diagnosing errors, preventing abuse and protecting legal claims: our legitimate interests in providing a secure and reliable Service (GDPR Art. 6(1)(f)).
• Complying with tax, accounting and other legal duties: legal obligation (GDPR Art. 6(1)(c)).
• Any future advertising-related processing for which consent is legally required: consent (GDPR Art. 6(1)(a)). This Policy does not itself constitute consent.

6. Recipients and international transfers

Personal data may be processed, only as needed for the purposes above, by:

• our website hosting provider (currently OVHcloud);
• providers that host or secure the App API and related infrastructure;
• our email provider when you contact us;
• Google/Firebase for Android push notifications and related delivery infrastructure;
• Google Play for Play Billing, subscription verification and acknowledgement, Play Integrity and App licensing;
• Google/YouTube for video playback that you initiate;
• Apple for App Store purchases, StoreKit, App Attest and APNs delivery; and
• professional advisers or public authorities where disclosure is required by law or necessary to establish, exercise or defend legal claims.

Firebase, Google and Apple services operate on global infrastructure and may process data outside the European Economic Area. Where a transfer for which we are responsible is made to a country without an adequacy decision, an applicable transfer mechanism, such as the European Commission’s Standard Contractual Clauses, or another safeguard permitted by law is used. Provider-specific processing is also governed by each provider’s own privacy terms.

Further information is available from OVHcloud, Firebase, Google and Apple.

7. Retention

We retain each category of personal data only for as long as needed for the stated purpose and then delete or anonymise it, unless a longer period is required by law or necessary for the establishment, exercise or defence of legal claims.

• Website and API access, error and security logs are kept for the standard operational period configured for the relevant service and are not archived to create advertising or audience profiles.
• Support and privacy correspondence is kept until the request is resolved and thereafter only for the period needed for accountability or legal claims.
• Pseudonymous device hashes, App access, trial, security, FCM and subscription-status records are kept while needed to provide the relevant Service, validate entitlement, deliver requested notifications and prevent abuse, and thereafter only where required for legal obligations or claims.
• Short-lived Integrity jobs and anti-replay records are retained only for the period needed to complete and audit the security check and prevent replay.
• Data processed independently by Google, Apple or another destination you choose is retained under that provider’s policy.

8. Your choices and rights

Depending on the circumstances, you have the right to request access to, rectification or erasure of your personal data; restriction of processing; data portability where processing is based on contract or consent and carried out by automated means; and to object, on grounds relating to your particular situation, to processing based on legitimate interests. Where processing is based on consent, you may withdraw that consent at any time without affecting processing carried out before withdrawal.

You may request deletion of data controlled by us by writing to data@sniperadar.com. Because the App does not require a named user account, we may ask for the Support ID shown in the App and other limited information needed to identify the relevant pseudonymous installation and verify the request.

You may also lodge a complaint with the President of the Personal Data Protection Office (UODO) in Poland or another competent supervisory authority.

9. Whether data is required

Website technical request data is generated automatically when your browser communicates with the hosting server; without this communication the Website cannot be delivered. The App’s pseudonymous device reference, service-authentication data, essential App interactions and integrity checks are necessary to provide and secure App access. Purchase data is required only if you choose a paid subscription. Notification permission is optional; without it, you can still use the parts of the App available to you but will not receive push alerts.

10. Children

The Services are intended for adults and are not directed to anyone under 18. We do not knowingly seek to collect personal data from children. If you believe that a child has provided personal data to us, please contact data@sniperadar.com.

11. Automated decision-making

We do not use personal data to make solely automated decisions that produce legal effects or similarly significant effects concerning you. Radar Score is an informational assessment of listing events, not a decision about an individual.

12. Security

We use technical and organisational measures appropriate to the nature of the Services and the risks of processing, including encrypted transmission, pseudonymisation of the Android device identifier at the backend, access controls, anti-replay controls, protected local App storage and App/device integrity checks. No method of transmission or storage is completely secure.

13. Changes to this Policy

We may update this Privacy Policy when the Services, providers or legal requirements change. The latest version and its effective date are published on this page. Material changes may also be communicated through the App or another appropriate channel.

If you have questions about privacy, contact: data@sniperadar.com.