Image to PDF – PDF Maker
Image to PDF – PDF Maker
This Privacy Policy explains what information the Image to PDF – PDF Maker app (“the app”, “we”, “us”), published by Swiftpaycard Limited, does and does not collect, how it is used, and the choices you have. By using the app you agree to this policy.
Short version
- Your documents stay on your device. Every PDF and image you open, edit, convert or save is processed entirely on your device. We never upload, transmit, store or have access to your files.
- The app is free and supported by ads. It uses Google AdMob to show ads and Google Analytics for Firebase to measure ad performance. These require internet access and the device advertising identifier, and collect some data as described below.
- You are in control. Where the law requires it, you are asked for consent before personalised ads are shown, and you can reset or limit the advertising identifier in your device settings at any time.
1. Information we do NOT collect
- Your files and their contents. PDFs, images, scans, page contents, file names and folder locations are accessed only through Android’s Storage Access Framework, only for the files you explicitly pick, and only on your device. They are never uploaded to us or to any third party.
- Passwords for encrypted PDFs. If you open a password-protected PDF, the password is held in memory only for the duration of that task and is never written to storage, never included in any output, and never transmitted.
- Accounts. The app has no sign-in or user account, so we do not collect names, email addresses or profiles.
2. Information collected through advertising and analytics
The app uses the following Google services, which may collect data on their own terms:
- Google AdMob — serves the ads shown in the app.
- Google User Messaging Platform (UMP) — gathers your consent for ads where required.
- Google Analytics for Firebase — receives an event each time an ad is shown, used to measure ad revenue and to optimise our advertising campaigns.
Through these services, the following categories of data may be collected and processed:
- Advertising identifier (Advertising ID /
AD_ID) — used to serve and measure ads, cap how often an ad is shown, and (with your consent) personalise ads. - Device and app information — such as device model, operating system version, language, app version and similar technical identifiers.
- Ad interaction and performance data — such as ad impressions, the ad format and
placement, the ad network that filled the ad, and the estimated revenue value of an
impression (the
ad_impressionevent the app sends to Firebase Analytics). These contain information about the ad only — never anything about your documents. - Approximate location — advertising services may infer coarse location from your IP address. The app itself does not request or use precise (GPS) location.
- Diagnostics — standard crash and performance data that the advertising and analytics SDKs may collect.
We do not sell your personal information. Data handled by Google under these services is subject to Google’s own privacy terms (see Section 8).
3. How this information is used
- To display ads that keep the app free.
- To measure how ads perform and the revenue they generate.
- To optimise our advertising campaigns (including return-on-ad-spend campaigns in Google Ads).
- To limit how often the same ad is shown.
- With your consent where required, to show more relevant (personalised) ads.
4. Permissions the app requests, and why
| Permission | Why it is used |
|---|---|
INTERNET | To load ads and the consent form. |
AD_ID (advertising ID) | So the ads SDK can serve, cap and (with consent) personalise ads. |
ACCESS_NETWORK_STATE | So the ads SDK can check connectivity before requesting an ad. |
POST_NOTIFICATIONS | To show progress and completion notifications for long file operations. Optional — the app works if you deny it. |
FOREGROUND_SERVICE / FOREGROUND_SERVICE_DATA_SYNC | To let a long file operation keep running when you leave the app. |
The app deliberately does not request broad storage permissions
(READ/WRITE_EXTERNAL_STORAGE, MANAGE_EXTERNAL_STORAGE) or media
permissions. It only ever sees the files you choose through the system file picker.
5. Your choices and controls
- Consent (EEA, UK and other applicable regions). On first launch, and whenever required, you are shown a consent form managed by Google’s User Messaging Platform. You can change your choice later from the app’s Settings (“Privacy options”).
- Advertising ID. You can reset your advertising ID, or opt out of ad personalisation, in your device settings: Settings → Google → Ads (or Settings → Privacy → Ads on some devices).
- Notifications. You can turn app notifications off in your device settings at any time.
6. Data retention
We do not store your files or personal data on our own servers — the app has none. Data collected by Google AdMob and Firebase Analytics is retained according to Google’s policies and your account and consent settings.
7. Children’s privacy
The app is intended for a general audience and is not directed to children under the age of 13 (or the minimum age required in your country). We do not knowingly collect personal information from children. If you believe a child has provided personal information, please contact us and we will take appropriate steps.
8. Third-party services
The advertising and analytics services used by the app are operated by Google. Their handling of data is governed by:
- Google Privacy Policy: https://policies.google.com/privacy
- How Google uses data from partners’ apps: https://policies.google.com/technologies/partner-sites
- Google AdMob: https://support.google.com/admob/answer/6128543
9. Security
Because your documents never leave your device, they are protected by your device’s own security. Data transmitted by the advertising and analytics SDKs is sent over encrypted connections managed by Google.
10. Changes to this policy
We may update this Privacy Policy from time to time. Changes will be posted at this page with an updated effective date. Continued use of the app after a change means you accept the updated policy.
11. Contact
If you have any questions about this Privacy Policy or your data, contact us:
Swiftpaycard Limited
Email: doc.swiftpaycard@gmail.com
Comments
Post a Comment