Last updated: 30.04.2026
Applies to: Nitro Pdf Editor (“the App”), provided by (“we”, “us”, “our”).
Contact: [support email]
1. Summary
This App is built to view and manipulate PDF—and related—files largely on your device. We aim to minimise data processing and explain what occurs when you use the App.
2. Information we do not routinely collect
The App does not require you to create an account to use core features described in product documentation.
We do not ask for your name, email, postal address, or phone number solely to use offline-style tools that process files on your device.
3. Information processed on your device
When you use features such as opening, exporting, merging, splitting, cropping, removing pages, or converting images to PDF, documents and previews are ordinarily processed on your device using operating system APIs (for example Storage Access Framework and rendering libraries).
Processed outputs are written to locations you choose through your device’s file picker or save flows.
Because processing can occur entirely on-device, we may not receive a copy of your files.
4. Permissions and access
Depending on OS version and the feature you use, Android may prompt for access to photos, documents, storage, or other capabilities. [Option A: Describe only what you currently request.] [Option B: If you ship updates that add cloud/network features, revise this section.**]
You control whether to grant permission and can revoke it in system settings subject to OEM/Android behaviour.
5. Data we may automatically receive (technical diagnostics)
[Choose one:
If you truly collect none: ] We do not collect analytics identifiers, diagnostic logs in the backend, crash reports to our servers, or advertising IDs through the App ourselves.
Replace with truthful text if different, for example Crashlytics, Play vitals forwarded to Firebase, telemetry SDKs—list vendor, categories of data (device model, logs, timestamps), lawful basis/purpose where required.
6. Third parties
[Adapt.]
Examples you might truthfully declare:
Google Play, which processes certain information independent of us when you obtain the App from Google Play (Google Policies).
[If applicable] Third-party SDKs listed by name.
If you monetise:
[If ads present] Identify ad networks, “personalisation” versus “non-personalised” ads, identifiers used, choices.
[If analytics/crash tooling present] Name tools and link to vendor privacy notices.
[If payments present] Mention payment processor behaviour.
[If AI/cloud processing present] State what is uploaded, retained, geographic transfer, safeguards.
Currently, if core tools run offline on-device, state that plainly and remove unused categories.
7. Cookies and websites
[If no website] N/A unless you operate a companion site—in which case add a Cookies/website section.
8. Legal bases & regional rights (EU/UK example)
[If targets EU/EEA or UK] State lawful bases for each processing category (typically contract/legitimate interest for diagnostics with balanced test, consent for optional analytics/ads).
Describe rights: access, deletion, portability, objection, withdrawal of consent [and EU representative if required].
[If CPRA/other US states apply] Explain “sell/share” disclosures and opt-out mechanics if relevant.
[If HIPAA/health data]** Do not** imply compliance unless formally assessed—the App is unlikely suitable for HIPAA data.
9. Children
The App [is/is not] directed at children under 13 (or relevant age threshold). [If directed at general audience] We do not knowingly collect personal information from children. Parents may contact [email] regarding concerns.
[If knowingly children’s app]** Comply with COPPA/other rules and revise thoroughly.
10. Security
We use reasonable safeguards common to consumer Android apps (“defence in depth” at device level plus secure engineering practices [only if truthful]). No method is 100% secure. Reduce risk by keeping OS updated, securing device lock screens, limiting sensitive documents on shared phones.
11. Retention
On-device artefacts remain until you delete them. [If analytics on servers] Explain retention timetable (e.g. crash logs retained [X days]).
12. Changes
We may revise this Privacy Policy periodically. [If app shows version] Updating the posted date and notifying within the App or store listing may suffice. Continued use after changes may constitute acceptance only where permissible under applicable law (legal review recommended).