Last updated 10 September 2026
This Privacy Policy explains how we handle information when you use the iOS application Compress PDF (the "App").
The App is published by Sudha Krishnasamy. In this policy, "we", "us", and "our" mean that publisher, who is the data controller for the limited information described below.
If you have questions, or want to exercise any of the rights described under Your Privacy Rights, contact us at supportnewagedev@gmail.com.
The App works without an account. We never ask for your name, email address, or payment details, and there is nothing to sign in to.
Document processing happens on your device. Every operation — compressing, merging, splitting, signing, redacting, OCR, and the rest — runs locally using Apple's own frameworks. We do not upload your documents to our servers, and no part of a document is included in any report the App sends.
The App contains no advertising, no ad SDK, and no in-app purchases.
The App does not use App Tracking Transparency and does not access the Advertising Identifier (IDFA). Nothing you do here is used for cross-app or cross-site tracking.
The App asks for camera access if you use document scanning. To build a PDF from photos it uses Apple's photo picker, which hands over only the images you select and needs no access to your photo library. The App asks for nothing else — no microphone, contacts, or location.
Optional usage statistics and crash reports are off until you turn them on. The App asks once, on first launch, and you can change your answer at any time in Settings.
The App's own code contains no networking of any kind. Usage statistics and crash reports are the only things the App itself sends anywhere. Apple's system services still reach the network on your behalf when you ask them to — opening a file from iCloud Drive, loading a photo stored in iCloud, following a link to the App Store — under Apple's terms rather than ours.
This is the part most people are asking about, so it comes first.
Documents you open, create, or edit are processed on your device, using Apple's own frameworks. We do not upload them to our servers. We do not receive their contents, their file names, their page text, their sizes, or their page counts, and no part of a document is included in usage statistics or crash reports.
Two things sit outside that, because they are your choices rather than ours:
Where you save or open files. The iOS Files app can show locations backed by iCloud Drive or another cloud provider. If you open a document from such a location, or save a result to one, that provider handles the file under its own terms.
Where you share results. When you use the share sheet, you pick the destination — Mail, Messages, another app, a cloud service — and that destination handles the file under its own privacy policy.
Device and iCloud backups may also include App data, depending on your backup settings. Those are handled by Apple under Apple's terms.
The App requests one permission: camera access, and only at the moment you first scan a document. Scanning uses Apple's document scanner; the camera feed and the resulting pages are processed on your device and are not sent to us. You can refuse, and the rest of the App still works.
Photos are handled differently and do not involve a permission at all. When you build a PDF from photos, the App presents Apple's photo picker, which runs outside the App. Only the images you explicitly select are handed to the App, and it has no access to the rest of your photo library. Those images are converted on your device.
The App does not request microphone, contacts, location, health, or calendar access, and contains no code that would use them.
The App does not require an account or any personal details.
If you email us for support, we receive whatever you choose to put in that message — typically your email address, a description of the problem, and sometimes screenshots or device details.
The App saves the following locally so it works between launches. None of it is transmitted to us.
your list of recent documents;
saved workflows;
saved signatures and initials;
favourite tools and per-tool defaults, such as compression level or page ranges;
interface preferences and one-time hints you have already seen;
a count of successful jobs, used only to decide when to offer the rating prompt;
your two privacy choices described below.
Nothing in this section happens until you tap Allow on the first-launch question or switch something on in Settings. Before that, the App does not contact Google at all: the analytics and crash-reporting services are not started, and no installation identifier is created.
Usage statistics (Google Analytics for Firebase). Two different things are collected here, and it is worth separating them.
Events we define. The App's own code records a fixed, closed list of six custom events:
Event
What it says
feature_opened
which tool you opened
job_started
a job began, and in which tool
job_finished
a job ended, in which tool, and whether it succeeded
result_shared
a result was shared, and from which tool
job_chained
one tool's result was passed to another, and which two
workflow_finished
a saved workflow ran, and whether it succeeded
The only details attached to any of these are the name of the tool (for example compress, merge, redact) and whether the job succeeded, failed, or was cancelled. That list is fixed in the App's source code, so no file name, path, or document content can be added to it by accident.
Events and parameters the Firebase SDK collects on its own. Separately from our six, Google Analytics for Firebase collects a set of standard events and parameters automatically, without the App asking it to. These include first open, session start, session engagement time, app and operating system updates, and screen views. Google documents the full set in Automatically collected events and Automatically collected user properties. We do not control this list, and it can change when the SDK is updated.
Identifiers and technical information. Alongside both kinds of event, Google collects:
a Google Analytics app instance ID, which distinguishes this installation of the App from another. It is not your name and is not tied to any account, but it is not anonymous either: it is a per-installation identifier, which is what allows sessions to be counted rather than just raw events. It is reset if you delete and reinstall the App, or clear its data;
a Firebase installation ID, used by Firebase services to identify this installation, and a separate installation identifier used by Crashlytics. These are distinct from the Analytics app instance ID. Google describes them in Manage Firebase installations;
device and app information, such as device model, operating system version, language, time zone, and App version;
an approximate region — country and state or region — that Google derives from the IP address of the connection. The App itself never asks for location permission and contains no location code; this is inferred at Google's end from the network connection, as it is for any internet request.
Crash reports (Firebase Crashlytics). When enabled, and only when the App actually crashes or hits a non-fatal error, the App sends a report containing the stack trace showing where the code stopped, the device model, the operating system version, the App version, a Crashlytics installation identifier, and a crash identifier. Crash reports do not contain your documents or anything you typed.
Ratings. The rating prompt is Apple's own, shown by iOS. Apple does not tell us whether you were shown it, whether you rated the App, or what you said. The "Rate" and "Share" options in Settings simply open the App Store.
Apple developer reports. Apple may give us aggregated App Store, performance, and crash information through its developer tools, under Apple's own terms. This arrives in aggregate or diagnostic form and does not identify you.
During ordinary use of the App, we do not collect your name, email address, phone number, postal address, payment details, contacts, precise location, health data, biometric data, or browsing history. We do not collect the contents, names, or metadata of your documents.
The exception is information you choose to send us. If you email us for support, we receive your email address and whatever else you put in that message, as described under Information you provide.
Photos and camera images are a separate case worth stating plainly: the App can read them, with your permission, in order to build a PDF for you. That work happens on your device, and neither the images nor anything derived from them is sent to us or included in any report.
Usage statistics and crash reports are controlled separately, and both are off by default.
On the first launch, the App shows a single question asking whether you want to help improve it. Choosing Allow turns both on. Choosing Not now, or dismissing the question, leaves both off.
You can change either one at any time in Settings, using Share usage statistics and Send crash reports.
The two switches behave slightly differently when you turn them off, and we would rather say so than round it up:
Usage statistics stop immediately. No further events are recorded or sent.
Crash reports: turning off automatic crash reporting takes effect the next time the App launches. This does not delete reports already sent to Google.
Turning a switch off does not delete information already sent to Google, and deleting the App does not delete it either. To request deletion, email us at supportnewagedev@gmail.com.
On devices that support Apple Intelligence, the App offers an assistant that can suggest and run PDF operations for you. It uses Apple's on-device Foundation Models framework. The App sends nothing to us or to Google for this feature, and it contains no code that transmits your document or your request to any server of ours. Apple's handling of on-device intelligence is described in Apple's own privacy documentation.
If your device does not support Apple Intelligence, the assistant is simply unavailable; nothing is sent anywhere instead.
The App includes a share extension, so you can send a PDF to it from another app, and App Shortcuts, so you can run operations from Siri and the Shortcuts app.
The share extension copies the file you shared into the App's shared container and reads its size so it can show you what you are about to open. It links no analytics or advertising code and sends nothing anywhere.
Shortcuts you build run on your device. If you share a shortcut with someone else, what travels is whatever that shortcut contains: normally just the steps, but a shortcut can also hold text or a file you put into it. Check a shortcut before sharing it.
to run the App's features and remember your preferences between launches;
to respond if you contact us for support;
if you have enabled them, to understand which tools people use, how often jobs succeed, and where the App breaks, so we can fix problems and decide what to build next;
to comply with legal obligations and enforce our rights where necessary.
We do not use any of this information for advertising, profiling, or automated decisions about you.
Apple, for App Store distribution, system frameworks including PDFKit, Vision, and Foundation Models, the ratings prompt, and any App Store developer reports.
Google (Firebase), for optional usage statistics and crash reports, and only when you have turned them on. Google processes this information as our service provider under the Firebase Data Processing and Security Terms, and its general practices are described in the Google Privacy Policy.
We use no other third-party services, and we do not sell or rent information to anyone.
If you contact us for support, or if you have enabled usage statistics or crash reports, information may be processed in countries other than your own, including the United States. Google applies its own transfer safeguards to the data it processes on our behalf.
Data stored on your device stays there until you delete it in the App, overwrite it through normal use, or delete the App. Apple system backups may retain App data depending on your iCloud and device backup settings.
Deleting the App does not delete files you have already exported or shared elsewhere, and it does not delete usage statistics or crash reports already sent to Google.
Crash reports are retained by Firebase Crashlytics for 90 days, after which removal begins.
Usage statistics: we configure Google Analytics to retain user-level and event-level data for two months, without resetting user-data retention on new activity. Expired data is deleted through Google's monthly deletion process. Aggregated reporting may remain available beyond this period.
Google's own description of these periods is at Privacy and Security in Firebase.
Support emails are kept only as long as reasonably necessary to answer you, resolve disputes, and meet legal obligations.
The App is a general-audience document utility. It is not directed to children under 13, or the equivalent minimum age in your region, and it is not published in the App Store Kids Category. We do not knowingly collect personal information from children. If you believe a child has provided personal information to us, contact us at supportnewagedev@gmail.com and we will take appropriate steps.
Depending on where you live, you may have the right to request access, correction, deletion, portability, or restriction of personal information we process, to object to processing, and to withdraw consent.
To make a request, email supportnewagedev@gmail.com. We may need to verify your request before responding.
Two practical notes. First, you can withdraw consent yourself at any time using the two switches in Settings. Second, most of what the App holds never reaches us: data stored only on your device is not something we can access, correct, or delete on your behalf — deleting the App removes it, subject to your backup settings.
If UK or EU data protection law applies to you, we rely on the following legal bases:
Consent (UK/EU GDPR Article 6(1)(a)) for usage statistics and crash reports. This is why both are off until you say yes, why the question is asked before anything is collected, and why nothing is pre-ticked. You may withdraw consent at any time using the switches in Settings; withdrawal does not affect processing carried out before you withdrew.
Legitimate interests (Article 6(1)(f)) for answering support emails and for protecting our rights, where our interest in responding to you and in running the App safely is not overridden by your interests or rights.
You have the right to lodge a complaint with a data protection supervisory authority. In the UK this is the Information Commissioner's Office (ico.org.uk); in the EEA it is the authority in the country where you live or work.
We do not sell personal information, and we do not share personal information for cross-context behavioural advertising or targeted advertising. The App contains no advertising and no advertising identifiers.
The App does not collect precise geolocation, biometric information, protected classifications, or sensitive personal information.
If you have enabled usage statistics or crash reports, we may process identifiers — the Google Analytics app instance ID, the Firebase installation ID, and the Crashlytics installation identifier — along with internet or other electronic network activity information and the approximate region Google derives from your IP address, in the limited diagnostic form described above. If you contact us for support, we process the identifiers and content you include in your message, in order to answer you.
The App is a native iOS application and does not browse the web, so browser Do Not Track and Global Privacy Control signals do not apply to it. Regardless of any signal, the App performs no tracking: it contains no advertising code and never accesses the Advertising Identifier.
We may update this Privacy Policy from time to time. The updated version will be identified by the "Last updated" date above. If we materially change what the App collects, we will update this policy and the App Store privacy disclosures before the change ships.
Email: supportnewagedev@gmail.com