Section 01
Introduction
At Pyrbit, we believe your documents are your business — not ours. Pyrbit PDF was built with a single guiding principle: everything that happens to your documents happens on your device, and they never leave it.
This Privacy Policy explains what information the App collects, how it is used, how it is stored, and what choices you have — including the parts of the App (ads and anonymous analytics) that do involve a third party. Please read it carefully. By downloading or using Pyrbit PDF, you agree to the practices described here.
If you do not agree with any part of this policy, please do not use the App.
Section 02
Scope
This Privacy Policy applies to:
This policy covers all 42+ tools in the App including PDF editing, compression, merging, splitting, conversion, OCR, an on-device AI Assistant, digital signing (including verifying signatures on documents like e-Aadhaar), and password protection. It does not govern third-party services you interact with externally (Apple App Store, your email client, iCloud).
Sections 4 to 23 were written for the iPhone, iPad and Mac apps (referred to as “the App”). Where Pyrbit PDF on the web works differently, Section 3 describes what applies to it; the remaining sections — including children's privacy, your rights, policy changes and contact details — apply to the web app as well.
Section 03
Pyrbit PDF on the web (pdf.pyrbit.com)
Pyrbit PDF is also available as a web app at pdf.pyrbit.com. This section explains how the web app handles your information. Where it differs from the iPhone, iPad and Mac apps described elsewhere in this policy, this section applies.
Your documents stay in your browser
When you use a tool on the web, your documents are processed inside your web browser, on your own device. They are never uploaded to Pyrbit or to anyone else. Online, you can work with files of up to 10 MB.
Signing in with Google
To use the online tools, you sign in with a Google account. Sign-in is handled by Firebase Authentication, a service of Google LLC. When you sign in, we receive your Google account's name, email address and profile photo URL, and a Firebase user ID. Anonymous accounts can't use the online tools.
What our server stores
Our server runs on Amazon Web Services (AWS) in the Mumbai region (ap-south-1). For each account, it stores:
- your Firebase user ID;
- your email address;
- the number of documents you have made;
- the time of your current free 24-hour window;
- your Pro status and when it expires; and
- Razorpay order and payment IDs.
Why we keep it: to give each Google account one free document every 24 hours, to provide Pro access, to prevent fraud and abuse, and for rate limiting. Rate limiting uses short-lived per-minute counters that expire automatically within minutes.
How long we keep it: for as long as your account exists. To have it deleted, email [email protected] and we will delete it within 30 days — except payment records that we are required by law to keep.
Payments for Pyrbit Pro
Payments for Pyrbit Pro on the web are processed by Razorpay Software Pvt. Ltd. We never see or store your card, UPI or bank details. Pro on the web is a one-time payment for 1 month or 1 year, with no auto-renewal.
Website delivery and security
Our websites are delivered and protected by Cloudflare, which provides our content delivery network (CDN) and DDoS protection. Like any web server, these services process your IP address and request data to keep the service secure. Our AWS API logs are kept for 14 days.
Ads on the web
If you use the web app for free, you may see ads served by Google (AdSense or Google Ad Manager), which may use cookies or similar identifiers. Pyrbit Pro users see no ads. Where required — in the European Economic Area, the United Kingdom and Switzerland — a consent message is shown first. To learn how Google uses information in advertising, see How Google uses cookies in advertising.
Storage in your browser
The web app stores your settings, drafts of files you have made (in your browser's IndexedDB storage) and your sign-in state in your browser only. You can clear them at any time, for example by clearing this site's data in your browser settings.
Section 04
What We Collect — and What We Don't
In the iPhone, iPad and Mac apps, we DO store locally on your device (never transmitted to us): your optional display name, app settings, recently-opened file metadata, on-device usage statistics, and subscription status sourced from Apple.
We do NOT collect, upload, or transmit: your PDF files or images, your phone number, your precise location, or your contacts — to us or to anyone. If you create an account in the apps, we receive only the basic profile (name and email address) that Google or Apple shares for sign-in. On the web, see Section 3 for what Google sign-in shares with us and what our server stores.
Ads & anonymous analytics are the one place third parties are involved in the iPhone, iPad and Mac apps: Google AdMob (ads, free tier only) and Google Firebase Analytics (anonymous usage counts). Neither ever receives your documents or their contents — see Sections 7 and 20 for exactly what each does and doesn't do. The services the web app uses are listed in Section 3.
Aadhaar Digital Signature verifies documents already digitally signed by an issuing authority (e.g. e-Aadhaar), and lets you sign with a certificate you already have. It does not ask for, collect, or store your Aadhaar number, date of birth, or gender.
Section 05
Information You Provide
a) Display Name
The App allows you to set a personal display name in your profile. It is stored locally on your device using
Apple's UserDefaults and never transmitted anywhere. It is entirely optional — the default is "User"
and you can change it anytime.
b) Digital Signatures — Aadhaar Digital Signature
This tool works two ways, and neither one involves us receiving your identity details:
If the certificate you bring was itself issued to you via an Aadhaar-based identity check (by a licensed Certifying Authority, outside this App), whatever identity fields that certificate contains become part of any PDF you sign with it — the same as with any digital signature. The App doesn't add, read, or transmit anything beyond using the certificate to sign.
c) Support Communications
If you tap Send Feedback, your email client opens a pre-filled email to [email protected]. Any information you include is received solely to respond to your inquiry and is never used for marketing.
Section 06
AI Assistant — Powered by Apple Intelligence, On Your Device
The AI Assistant runs on Apple Intelligence, using Apple's Foundation Models framework — the language model built into your device's operating system. It is a device capability, not a service we operate.
- The model lives on your device. Your device downloads it once from Apple as a system component — we neither ship it nor download it — and it then runs locally on your device's Neural Engine.
- It works with no internet connection. Once the model is on your device you can switch on Airplane Mode and the assistant still answers. If it can't work offline, it simply doesn't work — there's no online fallback.
- Nothing you type or attach is sent anywhere. Your prompts, any documents you attach, and the assistant's replies are processed entirely on your device — not to us, to Apple, to Private Cloud Compute, or to any other AI service. The App makes no network request for AI, and contains no code that could.
- It is off until you turn it on. The assistant is disabled by default, and you can switch it off any time in Settings → AI Assistant.
What It Can See
Only what it needs to answer the message in front of it: your chat messages in the current conversation, and text from any document you explicitly attach with the paperclip (having a file on your device does not expose it). All of this stays in memory for the conversation and is cleared when you start a new chat — none of it is logged, sent anywhere, or used to train any model.
Personalization (Opt-In)
If you turn personalization on, the App may notice a detail you type in chat (name, email, phone, organisation) and ask before saving it, so drafts can use your real details. Saved details stay in the App's private on-device storage only — you can view, edit, or erase them anytime in Settings → AI Assistant → Personalization.
Apple Intelligence requires a supported device and system version, and must be enabled in Settings. If it's unavailable on your device, the AI Assistant is simply unavailable — every other tool in the App works normally.
Section 07
Information Collected Automatically
This table describes the iPhone, iPad and Mac apps. What the web app stores is described in Section 3.
| Data | Purpose | Storage | Transmitted? |
|---|---|---|---|
| App preferences & settings | Appearance, quality defaults, export format | UserDefaults (on-device) | Never |
| Usage statistics | PDFs processed, pages handled, tools used, storage saved — shown in Profile | UserDefaults (on-device) | Never |
| Recent file metadata | File names, page counts, sizes, last-opened dates (not file contents) | UserDefaults (on-device) | Never |
| Subscription status | Pro/Free status, plan type, expiration — to unlock features | UserDefaults (on-device), sourced from Apple StoreKit | Never |
| Onboarding flag | Remembers whether you have seen the onboarding screen | UserDefaults (on-device) | Never |
| Advertising identifier | Show and measure ads for free (non-subscriber) users only | Not stored by us | By Google AdMob |
| Anonymous analytics ID + named events | Understand which tools get used, how often, on which device type | Not stored by us | By Firebase |
Section 08
Information We Do Not Collect
The Pyrbit PDF apps for iPhone, iPad and Mac do not collect any of the following, by us or on our behalf (for Pyrbit PDF on the web, see Section 3):
- Email addresses (unless you voluntarily contact us)
- Phone numbers
- Physical address or precise location data
- Contacts or calendar data
- Biometric data of any kind
- Web browsing history or cookies (the App is not a browser — see Section 20)
- Third-party account passwords (Sign in with Apple/Google use token-based authentication; we never see your password)
- Crash logs or diagnostics sent to any server
The App does use the camera (to scan paper documents into PDFs) and the microphone and speech recognition (to let you dictate a message to the AI Assistant) — see Section 13 for exactly when each is used. What we do not do is transmit anything captured that way: scans and dictated speech are processed entirely on your device.
The App's embedded PrivacyInfo.xcprivacy manifest honestly declares
NSPrivacyTracking = true,
because Google AdMob uses a device identifier for advertising, and lists the ad-network domains that involves
(Google's own). We don't add any tracking beyond what AdMob itself requires, and everything else the App accesses —
UserDefaults and FileTimestamp — is declared for on-device use only.
Section 09
How We Use Information
Because most data never leaves your device, our use of information is limited:
| Purpose | Data Used | Legal Basis |
|---|---|---|
| App features & functionality | Locally stored preferences, file metadata | Contract |
| Subscription entitlements | Subscription status from Apple StoreKit | Contract |
| Profile & usage display | Display name, local usage counters | Legitimate interest |
| Verify / sign PDF documents | The certificate already in the document, or a certificate you bring — no identity data collected | Contract |
| Show & measure ads (free tier) | Device advertising identifier, only if you allow tracking | Consent (ATT) |
| Understand app usage | Anonymous Firebase installation ID + named events | Legitimate interest |
| Support communications | Your email and message content | Legitimate interest |
How the web app uses the data it stores, and why, is described in Section 3.
Section 10
Legal Bases for Processing
Where applicable law (EU/UK GDPR, India DPDPA 2023) requires a legal basis for processing personal data:
- Contractual necessity — Processing subscription status and preferences is required to provide the App as purchased. The same applies to signature verification/signing, which uses only certificates already present or brought by you.
- Consent — Personalized advertising: Google AdMob only uses your device's advertising identifier for personalization if you allow tracking when Apple's App Tracking Transparency prompt asks. Declining doesn't stop ads from showing — it only stops them being personalized.
- Legitimate interests — Storing recent file metadata and usage statistics locally, and collecting anonymous, aggregated analytics about which tools are used, helps us build and fix the right things. No override of your fundamental rights occurs, since none of this identifies you individually or leaves your device tied to your identity.
Section 11
Sharing of Information
We do not sell, rent, or trade your personal information, ever. The sharing below is limited to the specific purposes named.
The data sharing that occurs in the App (for the web app's service providers, see Section 3):
Section 12
Third-Party Services
| Service | Purpose | Data Exposed to Third Party |
|---|---|---|
| Apple StoreKit 2 | In-app subscriptions & one-time purchases | Product ID + purchase date only. Payment card, Apple ID, name: never exposed to us. |
| Apple Foundation Models | Powers the on-device AI Assistant | Nothing — runs entirely on-device, no network request is made. |
| Apple PDFKit / Vision / Security / CommonCrypto | PDF rendering, OCR, signing keys, document hashing | On-device only. No network calls. |
| Apple PHPickerViewController | Privacy-preserving photo selection for Images-to-PDF | Only explicitly selected images, processed locally. |
| Sign in with Apple / Google Sign-In | Optional account sign-in | Name and email address only, from the provider you choose. |
| Google Mobile Ads (AdMob) | Shows ads to free-tier (non-subscriber) users | Device advertising identifier (with your consent), standard ad-request data. |
| Google Firebase Analytics | Anonymous usage analytics | Installation ID, device type/OS, named in-app events. |
Those are the only third-party SDKs in the App, used only for what's named above. Neither AdMob nor Firebase Analytics is used for anything else, and neither ever receives your documents, their contents, or filenames. There is no crash-reporting, A/B testing, or backend-storage SDK of any kind. The services Pyrbit PDF on the web uses are listed in Section 3.
Section 13
App Permissions and Why They Are Needed
| Permission | Required For | Status |
|---|---|---|
| Camera | Scanning paper documents into PDFs (Scan PDF tool) — scans are processed entirely on-device | Only when used |
| Microphone & Speech Recognition | Dictating a message to the AI Assistant instead of typing — transcribed on-device where supported | Only when used |
| Photo Library | Adding a signature image, or the "Images to PDF" tool | Only when used |
| Files / Document Access | Opening PDFs from Files app, iCloud Drive, third-party cloud services | Only when used |
| App Tracking Transparency | Asks whether AdMob may personalize ads using your device's advertising identifier | Once, on request |
| Location, Contacts, Calendar, Health, Bluetooth | Not used | Not requested |
| Push Notifications | Not used | Not requested |
Section 14
Data Retention
| Data | Where Stored | How to Delete |
|---|---|---|
| Display name | Device (UserDefaults) — until you edit it or uninstall | Edit in Profile, or delete the App |
| App settings | Device (UserDefaults) | Settings → Reset, or delete the App |
| Recent file metadata | Device — rolling list | Settings → Storage → Clear Recent Files |
| Usage statistics | Device (UserDefaults) | Delete the App |
| Subscription status | Device (UserDefaults), sourced from Apple | Delete the App (subscription itself is managed via the App Store) |
| Processed / output PDFs | Device temp folder (cleared automatically) or Files app if saved | Settings → Storage → Clean Temp Files; delete saved files manually |
| Signing certificates | Device's local trust store only — never uploaded | Remove from the trust list in the App, or delete the App |
| AI Assistant personalization details | Device (App's private storage) — only if you turned personalization on | Settings → AI Assistant → Personalization → remove individually or erase all |
| Support emails | Developer's email inbox | Email [email protected] to request deletion |
| Web app account record | Our server (AWS, Mumbai) — while your account exists | Email [email protected]; deleted within 30 days, except payment records we must keep by law |
| Web app browser storage | Your browser only (settings, drafts, sign-in state) | Clear this site's data in your browser |
The App does not retain PDF files or document contents on any server. If you create an account, account-related personal data may be associated with that account until you delete it. Uninstalling the App removes all locally stored data from your device, but does not by itself delete an account.
Section 15
Data Security
We take reasonable technical precautions to protect the data stored by the App:
- All data is stored using Apple's established system APIs (
UserDefaults,FileManager,Security), benefiting from the full iOS/macOS security architecture — App Sandboxing, hardware Data Protection, and Secure Enclave. - Passwords for password-protected PDFs you open, and passwords/PINs for certificates you sign with, are held in memory only for that one action and are never written to disk, Keychain, or settings.
- Cryptographic keys generated on-device use RSA-2048 via Apple's Security framework and, where ephemeral, are never persisted.
- SHA-256 hashing (via CommonCrypto) is used for document integrity verification.
- The App transmits no document content or personal file data over any network connection. Ad requests and anonymous analytics events (Section 20) are the only network traffic the App makes, and neither ever includes anything from your documents.
No method of data storage is 100% secure. While we protect your device-resident data, we cannot guarantee absolute security against physical device theft. Use your device's Face ID, Touch ID, or passcode to protect your device.
Section 16
International Data Transfers
Because the Pyrbit PDF apps for iPhone, iPad and Mac store all document and personal data locally on your device and we do not operate a backend server for them, we do not transfer personal data internationally in the ordinary course of business when you use them.
The instances in which data may cross borders — none of them run by us — are:
- Apple StoreKit transactions — Apple routes App Store purchases through its global infrastructure, governed by Apple's privacy practices.
- Google AdMob & Firebase Analytics — Google's global infrastructure processes ad requests and anonymous analytics events, governed by Google's own Privacy Policy and its standard contractual safeguards.
- Support email — Emails to [email protected] travel through Google's (Gmail) email infrastructure, which may span multiple countries, under Google's Standard Contractual Clauses.
Pyrbit PDF on the web does use a server of ours: the account record described in Section 3 is stored with Amazon Web Services in Mumbai, India (ap-south-1), so if you use the web app from outside India, that record is transferred to and stored in India. Sign-in (Google Firebase Authentication), website delivery (Cloudflare), web payments (Razorpay) and web ads (Google) are handled by those providers, whose infrastructure may process data in other countries under their own privacy policies.
Section 17
Children's Privacy
Pyrbit PDF is intended for general audiences and is not directed at children under the age of 13 (or under 16 where applicable, such as in the EU under GDPR). We do not knowingly collect personal information from children under 13 — and, as described throughout this policy, we collect very little personal information from anyone.
If you are a parent or guardian and believe your child has provided personal information through this App (for example, via the support email), please contact us at [email protected] and we will promptly delete it.
Section 18
Your Rights and Choices
For All Users
| Right | How to Exercise |
|---|---|
| Access your data | Your data lives on your device. Profile shows your name and usage stats. Settings shows all preferences. |
| Correct your data | Edit your display name in the Profile screen anytime. |
| Delete your data | Delete the App to remove all locally stored data. Use Settings → Storage to clear recent files or temp files individually. |
| Delete your web account data | Email [email protected]. We delete the account record kept for Pyrbit PDF on the web within 30 days, except payment records we must keep by law (Section 3). |
| Decline ad personalization | Choose "Ask App Not to Track" in the App Tracking Transparency prompt when asked. Ads still show; they simply aren't personalized. |
For EU/EEA, UK & Switzerland Residents (GDPR)
You have additional rights including data portability, restriction of processing, right to object, and the right to lodge a complaint with your national data protection authority (DPA). Contact us at [email protected]. All requests are fulfilled within 30 days.
For California Residents (CCPA/CPRA)
You have the right to know, delete, and opt out of the sale of personal information. We do not sell personal information, and we do not share it for cross-context behavioural advertising. Contact us to make a CCPA request.
For India Residents (DPDPA 2023)
Under the Digital Personal Data Protection Act 2023, you have rights including access, correction, erasure, and grievance redressal. The Aadhaar Digital Signature feature does not collect your Aadhaar number, so there is no such identity data of yours held by us to request.
Section 19
Account Deletion / Data Deletion Request
Account deletion: If you signed in with Apple or Google, go to Settings → Account → Delete Account in the App. This revokes the sign-in with that provider and erases your locally stored profile immediately — no request to us is needed.
If you're unable to delete your account through the App for any reason, contact us at [email protected].
Pyrbit PDF on the web: to delete the account record our server keeps (Section 3), email [email protected]. We delete it within 30 days, except payment records we must keep by law. You can clear the web app's browser storage yourself at any time.
To remove other data associated with your use of Pyrbit PDF:
Delete the App from your device — Settings → General → iPhone Storage → Pyrbit PDF → Delete App. This removes all UserDefaults entries, cached files, and locally stored preferences.
Delete output PDF files you have saved to your Files app or iCloud Drive manually.
For support emails: email [email protected] with a deletion request. We will delete your email records within 30 days.
Section 20
Advertising, Analytics & Tracking
Advertising
In the iPhone, iPad and Mac apps, Pyrbit PDF shows ads from Google AdMob only to free (non-subscriber) users, and only after they've already used a Pro tool's one free daily use — watching a short ad unlocks one more use of that tool that day. Subscribers never see an ad anywhere in the App, and tools that aren't Pro-only never show ads.
To show and measure ads, AdMob collects a device advertising identifier. On iOS you're asked whether Pyrbit PDF can use this identifier for personalized advertising (Apple's App Tracking Transparency prompt) — you can decline, and the App and its ads work exactly the same either way. We do not receive or store this identifier ourselves; it's collected and used by Google under Google's own Privacy Policy.
Ads in Pyrbit PDF on the web are described in Section 3.
Analytics
We use Google Firebase Analytics to understand overall app usage — which tools get used, how often, and on which device type (iPhone, iPad, or Mac) — so we know what to build next and what to fix.
Firebase Analytics collects a randomly-generated installation identifier (not your name, Apple ID, or email), your device platform and OS version, and the names of a small set of in-app events (e.g. "a document was opened," "a document was exported") — never the contents of your documents, their filenames, or anything you type. This data is processed under Google's own Privacy Policy and is not linked by us to your Apple ID or sign-in name.
Cookies & Browser-Based Tracking
The iPhone, iPad and Mac versions of Pyrbit PDF are native iOS/iPadOS/macOS applications. They do not use a web browser engine, do not load web pages, and do not deploy cookies, web beacons, pixel tags, fingerprinting scripts, or any other browser-based tracking technology. The advertising identifier described above is the only cross-app signal involved, and it exists solely for the ad SDK named above.
Pyrbit PDF on the web runs in your browser: it keeps your settings, drafts and sign-in state in your browser's storage, and the Google ads shown to free users may use cookies or similar identifiers — see Section 3.
Everything else the App does — document processing, OCR, editing, signing, redaction, and everything the on-device AI Assistant does — never involves any ad network, analytics SDK, or third-party service, and none of it leaves your device.
Section 21
Do Not Track
"Do Not Track" is a browser-level signal, and the Pyrbit PDF apps for iPhone, iPad and Mac are native applications rather than websites, so there's no browser DNT signal for them to respond to. The equivalent, meaningful control on iOS is Apple's App Tracking Transparency prompt (Section 13), which the App fully honors: declining it stops AdMob from personalizing ads to you, immediately and permanently, without affecting anything else in the App.
Pyrbit PDF on the web does not currently respond to browser Do Not Track signals. Where required, a consent message is shown before ads, as described in Section 3.
Section 22
Changes to This Privacy Policy
We may update this Privacy Policy from time to time to reflect changes in the App, applicable law, or our practices. When we make material changes, we will:
- Update the Version and Last updated date at the top of this policy
- Notify users through an in-app notice on the next App launch (for significant changes)
- Post the revised policy at this same URL
Your continued use of Pyrbit PDF after the effective date of any revised policy constitutes your acceptance of the changes. If you do not agree, please stop using the App.
Section 23
Contact Information
If you have questions, concerns, or requests regarding this Privacy Policy or your personal data, please contact us:
We will respond to all legitimate privacy inquiries within 30 calendar days.
Pyrbit PDF — Privacy Policy · Version 1.8 · Last updated 10 November 2026