Privacy Policy
Effective and last updated: September 21, 2026.
1. Scope and controller
This policy explains how SweetMobile, the operator of PDF Eye, handles personal data when you use pdfeye.net, create an account, purchase Premium, contact support, or interact with our public pages. SweetMobile is the controller for the processing described here. Questions and privacy requests can be sent to help@pdfeye.net.
2. Your documents stay on your device
PDF Eye processes document bytes, filenames, extracted text, visual signatures, annotations, and generated output inside your browser. PDF Eye does not upload that document content to its servers, Firebase, RevenueCat, Google Analytics, or advertising services, and does not use it for AI training. Closing or refreshing the working tab clears the active document session. Your browser or operating system may separately retain files you opened or downloaded, browser history, thumbnails, or temporary data under its own settings.
3. Data we process and why
- Account, authentication, and access-grant data: Firebase Authentication processes your Firebase user ID, authentication provider, authentication timestamps, security information such as IP address and user agent, and—when you identify yourself—your email address and any display name or profile image supplied by your sign-in provider. PDF Eye may also retain a verified email address, enabled status, and an internal administrative note when complimentary Premium access is granted. Starting a guest purchase may create a temporary anonymous Firebase identity for security and checkout attribution; it is not a registered PDF Eye account. We use this data to sign you in, secure the service, link purchases when you ask us to, provide authorized access, and administer your account.
- Billing and entitlement data: RevenueCat processes an anonymous or identified customer ID, billing email, product and offering identifiers, price and currency, subscription status, transaction and renewal information, and customer-portal details. Its payment gateway, Stripe, processes payment credentials and payment-risk information. PDF Eye does not receive your full card number or security code.
- Service and measurement data: We may process page and workflow names, coarse file-count, page-count, and file-size ranges, browser and device information, referrer or campaign category, approximate location derived by service providers, consent state, error codes, checkout and transaction references, account type, and timestamps. Analytics never includes document names, document text, signatures, or document bytes.
- Support data: If you contact us, we process your email address, message, billing reference, and any other information you choose to provide. Do not send confidential documents, passwords, complete payment-card details, or one-time codes.
4. Legal bases
Where the GDPR or similar law applies, we rely on: performance of a contract to provide tools, authentication, purchases, Premium access, and support; compliance with legal duties for tax, accounting, consumer, and lawful-request records; legitimate interests in securing the service, preventing abuse and duplicate purchases, diagnosing faults, and measuring content-free service performance; and consent for non-essential analytics, advertising, or storage where consent is required. You may withdraw consent at any time without affecting earlier lawful processing.
5. Guest purchases and account recovery
A guest checkout uses a randomly generated RevenueCat anonymous customer ID stored in your browser. RevenueCat may return the billing email collected during checkout so PDF Eye can offer account recovery after payment. If you choose Google or email-link recovery, the anonymous RevenueCat identity may be associated with your Firebase UID. Until recovery is verified, PDF Eye stores a limited recovery record containing the transaction reference, originating anonymous ID, target UID, status, timestamps, and a safe error code. Guest access can be lost if browser data is cleared, you use private browsing, change devices, or sign out.
6. Local storage, cookies, analytics, and advertising
Strictly necessary browser storage is used for authentication state, fraud and security controls, your theme, the anonymous billing identity, purchase recovery, email-link completion, and short-lived checkout or navigation state. These functions may not work if necessary storage is blocked. We do not store your documents in local storage.
Google Analytics and Google advertising may operate on public pages when configured. In the EEA, United Kingdom, Switzerland, and locations that cannot be determined safely, Google Tag Manager and optional Google tags are blocked until you consent. In other locations, measurement may operate by default where permitted, subject to browser privacy signals such as Global Privacy Control. You can accept, reject, choose by purpose, or change your choice at any time using Privacy and cookie settings in the footer. If you allow advertising, Google Ads may measure whether a completed purchase followed an ad. That measurement receives the purchase amount, currency, and a transaction ID, and never document content. Rejecting optional purposes does not block the PDF tools or checkout.
7. Who receives data
We disclose only the data needed to operate the service to:
- Google Firebase, for Hosting, Authentication, Cloud Functions, Firestore, security, and consent-based analytics;
- RevenueCat, for checkout, customer identity, entitlements, subscription lifecycle, billing emails, receipts, and the customer portal;
- Stripe, as RevenueCat Billing's payment gateway, for payment processing and fraud prevention;
- Google advertising services, on public pages and subject to the consent controls described above; and
- professional advisers, authorities, or a successor operator when reasonably necessary to comply with law, protect users and the service, establish legal claims, or complete a business transfer subject to appropriate safeguards.
These providers may also act as independent controllers for data they collect directly under their own notices, particularly payment, sign-in, and advertising data.
8. International transfers
Firebase, RevenueCat, Stripe, and Google may process data outside your country, including in the United States. Where required, transfers are protected through adequacy decisions, approved contractual safeguards such as Standard Contractual Clauses, or another lawful transfer mechanism. Provider privacy notices explain their current locations and safeguards.
9. Retention
- Firebase account information is kept while the account exists and then removed under Firebase's deletion and backup cycles.
- Complimentary Premium grant records are retained until PDF Eye disables or removes the grant. Because a grant is assigned to an email address rather than a Firebase UID, deleting a Firebase account does not itself remove that separate administrative grant record; you may request its deletion through support.
- Checkout-correlation records expire after 30 days. Content-free, aggregated measurement may be kept longer.
- A pending browser recovery record expires automatically after its limited recovery window and is cleared sooner after verified recovery, explicit abandonment, sign-out, or sandbox reset.
- RevenueCat, Stripe, and Google retain their records under their notices and legal obligations. Billing, fraud, tax, accounting, dispute, and transaction records may be kept after account deletion for the legally required or defensible period.
- Support correspondence is kept only as long as reasonably needed to resolve the request, maintain security and support history, or meet legal obligations.
10. Account deletion
Signed-in users can request deletion from the Account page. After recent reauthentication, this removes the Firebase identity, requests deletion of the RevenueCat customer associated with that UID, and deletes directly linked PDF Eye attribution records. A separately administered complimentary email grant is not automatically deleted with the Firebase UID; contact support if you also want that grant record removed. Backup, transaction, tax, fraud, dispute, and legally required records may remain for their applicable retention periods.
Deleting an account does not cancel a subscription or stop renewal. Manage or cancel the subscription separately before deletion if you do not want it to renew. Deletion also cannot erase a separate anonymous RevenueCat purchase that was never successfully linked to the deleted Firebase account.
11. Your privacy rights
Depending on your location, you may request access, correction, deletion, restriction, objection, or portability of your personal data, and may withdraw consent. You may also have the right to appeal a denied request or complain to a supervisory authority. We do not sell document content. To exercise a right, email help@pdfeye.net. We may verify your identity and retain information necessary to document the request.
If you are in Spain, you may complain to the Agencia Española de Protección de Datos (AEPD). EEA and UK residents may instead contact the authority where they live or work. PDF Eye does not itself make solely automated decisions that produce legal or similarly significant effects; payment and fraud providers may make their own automated assessments under their notices.
12. Security and children
We use HTTPS, provider access controls, data minimization, and browser-local document processing. No online service can guarantee absolute security, so keep original files, protect your email account and device, and report suspected misuse promptly. Read more on our Security page.
PDF Eye is not directed to children under 16, and they must not create an account or purchase Premium. If you believe a child supplied personal data, contact us so we can review and delete it where appropriate.
13. Changes and contact
We may update this policy when the service, providers, or law changes. We will change the date above and provide additional notice when a material change requires it. For questions or requests, visit PDF Eye Support or email help@pdfeye.net.