Effective date: 25 August 2026
Last updated: 25 August 2026
Privacy summary. PDF Resizer changes PDF page dimensions and saves a new copy. PDF files are processed locally on your device. We do not upload PDF content, document text, filenames, file paths or document URIs to Anderkontrol, Google Analytics for Firebase or Firebase Crashlytics.
The app uses Google AdMob for optional rewarded ads, Google User Messaging Platform (UMP) for privacy choices, Google Analytics for Firebase for usage analytics, and Firebase Crashlytics for crash and stability diagnostics.
This Privacy Policy applies specifically to PDF Resizer for Android (the “App”), distributed through Google Play by Anderkontrol – Michał Anderko (“Anderkontrol”, “we”, “us”, “our”). It explains what information is processed when you use the App, why it is processed, and the choices available to you.
Data controller:
Anderkontrol – Michał Anderko
Burstwiesenstrasse 22
8606 Greifensee
Switzerland
Support and privacy contact:
anderkobrothers@gmail.com
If you contact us, we process the information you provide only as reasonably necessary to answer your request, investigate a reported problem, maintain appropriate business records, or comply with legal obligations.
PDF Resizer lets you select a PDF through the Android system document picker, choose a target page size such as A4, Letter or custom dimensions, and save a resized copy to a location selected by you.
PDF metadata needed to perform the requested operation, such as page count and page dimensions, may be held temporarily in memory or local application state. This operational information is not used to build a user profile.
The App uses export credits. In the current version, a completed rewarded advertisement can grant one credit, and one successful PDF export uses one credit.
Export credits:
The App excludes its credit wallet from cloud backup and device-to-device transfer. A temporary active-export operation may also be stored locally so that an interrupted credit transaction can be recovered safely after process termination.
The App may store settings, selected units, consent-related state provided by Google UMP, and temporary state needed to resume a system document-picker or export flow. These values are used to operate the App and are not account-synchronized by Anderkontrol.
The App integrates only the services listed below in the current version.
| Service | Purpose | Information that may be processed |
|---|---|---|
| Google AdMob / Google Mobile Ads | Optional rewarded advertisements, ad delivery, measurement, frequency management, fraud prevention and compliance | Advertising identifiers where available and permitted, IP address, approximate location inferred from IP, device/app information, consent status, and ad interactions. Google determines the exact processing under its policies and your privacy choices. |
| Google User Messaging Platform (UMP) | Privacy messages, consent management and the in-app Privacy choices entry point | Consent choices, region-related information, device/app information and technical information needed to present and store privacy choices |
| Google Analytics for Firebase | Understanding app usage, activation, retention, sessions, engagement and product funnels | Automatically measured usage/session data; screen transitions; app interactions; app version; locale; device/app metadata; installation or measurement identifiers used by Firebase; coarse location information such as region inferred from network information where processed by Google; and coarse event parameters such as page-count ranges, selected page-size mode, orientation, fitting mode and controlled failure categories |
| Firebase Crashlytics and Firebase Sessions | Crash, ANR, stability and unexpected technical-failure diagnostics | Stack traces, relevant app state, app/device metadata, Firebase installation/session identifiers, app version, operating-system information, and a limited set of privacy-safe diagnostic keys and breadcrumbs |
Google Analytics for Firebase automatically measures certain events such as first use, sessions and user engagement. The App also records a limited set of product events, for example successful PDF selection, export attempts and results, logical screen transitions, and the rewarded-credit flow.
Custom Analytics events use controlled categories and ranges instead of document-identifying values. The App does not set a Firebase Analytics user ID and does not include PDF filenames, URIs, file paths, document content, raw exception messages, exact credit balances, credit operation identifiers, advertising-unit identifiers or consent strings in its custom Analytics events.
Firebase Crashlytics may automatically collect crash reports, ANR reports, stack traces, relevant app state and device/app metadata. The App may attach a small, fixed set of technical context such as the logical screen, app locale, export stage, coarse page-count range, page-size mode, orientation, fitting mode, wallet-health category and network-state category.
The App does not set a Crashlytics user ID. We do not intentionally attach PDF filenames, URIs, file paths, PDF content, user email addresses, raw credit balances, transaction identifiers, consent strings, AdMob identifiers or full third-party SDK error messages to Crashlytics reports.
Expected product conditions—such as being offline, having zero credits, cancelling a picker or export, an unavailable advertisement, an encrypted/password-protected PDF, an unsupported/corrupt PDF, invalid custom dimensions, or the absence of a PDF viewer—are not intentionally reported as non-fatal crashes merely because they occurred.
Information described in this Policy is used to:
Where a consent-required privacy flow applies, the App uses Google UMP to present Google-managed privacy messages. In consent-required flows, Analytics collection starts disabled and is enabled only when the resolved consent policy permits collection. Ad requests are not made until UMP reports that ads may be requested.
Where required by the active UMP message, you can revisit your choices through Settings → Privacy choices. Changing or withdrawing a choice causes the App to re-evaluate whether Analytics collection and advertising requests are permitted.
Depending on your region and choices, Google may serve personalized or non-personalized ads. You can also manage advertising identifiers and related settings through Android and Google controls.
Ad availability is not guaranteed. If a rewarded advertisement is unavailable, no reward is granted merely for clicking the offer.
We share or make information available only as needed to operate the active services described in this Policy, comply with legal obligations, protect rights and security, or respond to lawful requests.
We do not sell your personal information for money. Certain advertising or analytics activities may be defined as a “sale” or “sharing” under some privacy laws. Where required, Google UMP, provider controls or platform/device settings are used to present consent or opt-out choices.
The active providers process information under their own terms and privacy policies:
Where applicable law requires a legal basis, processing may rely on:
Anderkontrol is located in Switzerland. Google and Firebase may process information in countries other than your country of residence. Where required, transfers are handled using safeguards made available by the relevant provider, such as contractual transfer mechanisms.
Depending on your location, you may have rights to access, correct, delete, restrict or object to processing, to withdraw consent, or to lodge a complaint with a competent supervisory authority.
You may:
Clearing app data or uninstalling the App also removes locally stored export credits and settings.
PDF Resizer is a general-purpose utility and is not directed to children under 13. We do not knowingly ask children to create an account or submit personal information through the App. If you believe a child has provided personal information to us through a support request, please contact us.
We use reasonable technical and organizational measures appropriate to this App, including local document processing, limited event schemas, controlled diagnostic keys, release signing and the separation of debug-only diagnostics from release builds. No method of electronic processing or transmission is completely secure.
This published Privacy Policy is currently provided in English. The App may display translated interface labels, but the linked legal page may remain in English. Any translation of this Policy is provided for convenience; the English version controls to the extent permitted by applicable law.
We may update this Policy when the App, active SDKs, data practices or legal requirements change. We will update the “Last updated” date and provide additional notice where required.
Questions about this Policy or the App’s data practices can be sent to: