Privacy Policy

1. Scope and contact

PVPium is the developer brand used by Efekan Kılıç, the individual developer and data controller operating PVPium IV Scanner. PVPium is not described here as an incorporated company.

This policy explains how PVPium IV Scanner processes information while you use its Android scanning, History, rewarded-ad and optional subscription features. For privacy questions or requests, contact contact@pvpium.com.

PVPium IV Scanner is an independent companion tool and is not presented as an official Pokemon GO application. This policy does not cover Pokemon GO, your game account or external websites and services.

2. Screen capture and on-device recognition

Scanning starts only after you start the scanner and approve Android's screen-capture request. While that session is active, the app receives screen frames to identify Pokemon, forms, CP, HP and appraisal IV bars and calculate league and evolution results. Capture can continue while Pokemon GO or another app is in front of PVPium.

Depending on Android's sharing mode, captured frames can include other visible screen content, including notifications or another app if you switch away from the game. Stop scanning before viewing sensitive content. The floating result panel being absent, closed or obscured does not itself stop the capture session.

The app processes screen images and recognition locally. Its scanner does not upload frames or recognized text to a PVPium server or pass them to the advertising SDK. It does not save screenshots or screen videos as History. Temporary recognition buffers are replaced or released during processing; local diagnostics may retain a short OCR excerpt in application memory until it is replaced or the process ends.

You can stop scanning using the app's stop control or the scanner notification. Android may also end a session. Declining capture permission prevents scanning but does not require you to provide game credentials.

3. Information stored on your device

• History: recognized Pokemon species and form, CP, attack/defence/HP IVs, scan time, calculated league and evolution results, favourites and the calculation data version.
• Preferences: scanner and result-panel settings and acknowledgement of the scanning explanation.
• Rewarded access: reward timing, device boot count and a randomly generated local reward receipt used to avoid duplicate grants. This is not an IMEI or a permanent hardware identifier.
• Server-verified access, where enabled: a temporary reward session identifier and claim secret, and a Google Play purchase token and verified subscription expiry. Cached subscription access is limited to 24 hours or its expiry, whichever is earlier; fresh verification is required after a device restart or detected clock rollback.
• Local diagnostics: recognition status, timings, errors and a short recognized-text excerpt. Debug builds may write diagnostic information to Android's local logs. The app does not automatically send those scanner logs to PVPium.

History and preferences are held in the app's private storage. The app does not sync History to an account or a PVPium cloud service. It does not require a PVPium account or ask for your Pokemon GO password. Its own manifest does not request contacts, SMS, microphone, camera or GPS location access.

4. Google ML Kit

The app uses Google's ML Kit text-recognition SDK. Recognition runs on the device, but ML Kit can send device and application information, recognition API usage and performance/error diagnostics to Google for diagnostics and usage analytics. Local recognition therefore does not mean that the entire app has no network data processing.

See ML Kit's data disclosure and Google's Privacy Policy for the provider's practices.

5. Rewarded ads and privacy choices

Internal test builds use Google AdMob demo rewarded ads. Builds with live advertising enabled use the developer's AdMob rewarded unit. A rewarded ad is shown only when you choose the watch-ad option in PVPium. The scanner must be stopped before an ad is shown; ads are not inserted into the floating result panel or displayed over Pokemon GO by the app. The current app provides 5 free scanning minutes per day, not per app launch. Each completed and verified rewarded ad adds 6 scanning minutes. Time decreases only while the scanner is running. Older app versions may retain their previous access rules. Demo builds use local reward timing; server-verified builds require a valid signed Google callback before access is granted.

For server-verified rewards, the app requests a random session identifier and claim secret from PVPium's hosting service and sends the identifier to Google as reward custom data. Google sends the signed reward transaction identifier, timestamp, ad unit and reward details to that service. The service stores the session, a hash of its secret, reward transaction and expiry to verify access and prevent duplicate grants. The claim secret is not sent as ad custom data.

The service receives the request IP address and uses a short-lived hash for rate limiting. Its application database does not store raw IP addresses, screenshots, OCR text or game credentials. Hosting access logs are separate and may contain IP addresses and request metadata.

The Google Mobile Ads SDK can collect and share IP addresses, app/ad interactions, diagnostic information and device or account identifiers, including advertising and app-set identifiers where available. IP addresses can be used to estimate general location without a GPS permission. These data support advertising, analytics and fraud prevention. Test ads are not represented as a guarantee that no SDK data is processed.

The app uses Google's User Messaging Platform to check applicable privacy requirements before requesting an ad. Where required, a privacy form is presented and an "Ad privacy choices" option allows you to revisit those choices. Consent requirements, your choices and SDK configuration affect the ads and identifiers used. Refusing personalised advertising consent is not the same as stopping all network communication.

See Google Mobile Ads data disclosure and Google's Privacy Policy. Provider data may be processed outside your country under the provider's published privacy and transfer arrangements.

6. Purposes and legal grounds

Local scan processing supplies the scanning function you request. Android capture permission and the in-app explanation precede access to screen content. Local settings and reward timing operate your selected features; provider diagnostics support reliability, and ad data supports rewarded ads and abuse prevention. Purchase and reward verification establish your selected access entitlement and prevent duplicate or invalid grants.

Where applicable data protection law requires a legal basis, requested service processing may be necessary to provide that service, relevant advertising processing relies on consent where required, and support/security processing may rely on legitimate interests or legal obligations. A device permission does not replace any separately required advertising consent.

7. Retention and deletion

History remains on your device until you delete it or remove the app's data. The "7 days" History option is a display filter, not an automatic deletion schedule. You can delete individual History entries or stop the scanner and use "Delete all History" in Settings. Clearing the app's storage or uninstalling normally removes its local History, settings and reward state.

Deleting History alone does not erase all preferences or SDK data. An expired local reward no longer gives access, but its stored timing and receipt can remain until replaced or app data is removed. Diagnostic memory lasts until replaced or the process ends; Android manages its own local log buffers.

Reward database records older than 48 hours are deleted when a new reward session is created. Without new sessions, those records can remain until cleanup runs. Rate-limit hashes older than roughly three minutes are deleted on subsequent rate-limit requests. These cleanup rules do not cover hosting access logs or backups; contact us about their retention and deletion.

Because the app has no PVPium account or History cloud copy, the developer cannot retrieve your local History remotely. Data already handled by Google is subject to Google's retention and deletion practices; removing local app data does not automatically delete that provider data.

8. Support communications

If you email contact@pvpium.com, we receive your email address, message and any attachments you choose to send. These are used to answer your request and investigate issues. Do not send passwords, payment-card details, or screenshots containing unrelated personal information. Support attachments you send voluntarily are separate from the scanner, which does not upload screenshots automatically.

Support information is processed through our email service to handle your request. We do not currently apply a fixed automatic deletion period to support correspondence, so messages and attachments may remain indefinitely unless deleted. Contact contact@pvpium.com to ask about the provider or request deletion of your correspondence. Any legally required retention and limitations will be explained when applicable.

9. Your choices and rights

You can stop capture, withdraw Android permissions through system settings, delete local History, clear app storage and use ad privacy choices where available. Depending on your jurisdiction, you may also have rights of access, correction, erasure, restriction, objection, portability and withdrawal of consent, and a right to complain to a data protection authority. Contact contact@pvpium.com for requests concerning data handled by the operator. We may need proportionate information to verify a request.

Withdrawal does not invalidate processing that was lawful before withdrawal. For data Google handles independently, its privacy tools and policy explain available choices. We cannot promise access to or deletion of data outside the operator's control.

10. Intended audience

PVPium IV Scanner is intended for users aged 13 and over and is not marketed to children under 13. This statement describes the intended audience; the app does not implement an age-verification system. If you believe a child under 13 has sent personal information to our support address, contact us so that we can review and address it.

11. Security

The app uses Android's private app storage and does not enable its own cloud History backup. Google documents encrypted transport for its ML Kit and Mobile Ads SDK data. Device access, malware or voluntary sharing of logs and screenshots can still expose information. No storage or transmission method can be guaranteed completely secure.

12. Optional subscriptions and changes

Where purchases are enabled, Google Play handles subscription checkout, payment details and recurring billing through your Google account. PVPium does not receive your payment-card details or Google password. The app sends its Google Play purchase token to PVPium's verification service over HTTPS. The service sends it to Google's Android Publisher API to check the fixed app, product, plan, purchase state and expiry and acknowledge eligible purchases.

The verification application does not persist purchase tokens, Google account identity or payment details in its database. The app retains purchase and access state locally for verification and restoration. Google processes purchases under its own policies. Hosting logs and backups are separate from the verification database.

Use Restore purchases with the Google Play account used for the purchase. Subscriptions renew according to the terms shown by Google Play unless cancelled. Manage or cancel them in Google Play subscriptions. Uninstalling PVPium does not cancel a subscription. See Google's cancellation instructions. Server verification is refreshed when the app resumes, when you restore purchases and periodically while the app is running. Verification failures do not extend access beyond the last verified access window. Cached access can delay recognition of a refund or revocation by up to 24 hours.

Firebase Analytics and Crashlytics are not enabled in the current scanner build. This policy must be reviewed before adding those services or changing data practices. Feature availability does not replace required consent.

Policy updates will identify the revision date. Material changes will be communicated appropriately, with renewed consent where required. Continued use alone will not be treated as consent to new processing that requires it.