Privacy Policy

Last updated: May 2026
Application: PDF Presenter (iPhone, iPad, Mac)

1. Overview

PDF Presenter uses Google Firebase for:

1. Google Analytics for Firebase — usage events (anonymous or pseudonymous) when the user enables optional analytics in onboarding. It can be turned off there; while off, the Analytics SDK does not send those events.
2. Firebase Crashlytics — crash and non-fatal error reporting for stability (stack traces, technical context, app build). Stays enabled for diagnostics; payloads are sanitized in code (no sensitive file paths, no file:// URLs, no PDF content in context keys).
3. Firebase Cloud Messaging (FCM) — remote notifications on iOS after system permission. The FCM/APNs token identifies the installation for message delivery.

2. What Analytics may record (with consent)

When statistics consent is on, the app may send, including:

• Screen views with internal names: home, paywall, presenter.
• Events such as onboarding steps (onboarding_step with numeric index), paywall product list load (product count only), presentation session duration in milliseconds (presenter_session_ended), without identifying the PDF document.

Not sent to Analytics: PDF content, file names, paths, document IDs, or unnecessary data — the code applies sanitization and blocked parameter keys.

3. What Crashlytics may record (when applicable)

• App crashes with device and build metadata.
• Manually recorded errors and technical logs after sanitization (no PII or file content).
• User ID in Analytics/Crashlytics only when the analytics flow allows; when analytics is disabled, the identifier is cleared.

4. Push (FCM on iOS)

With notifications allowed, the registration token and delivery metadata may be processed per Firebase and any backend using FCM.

5. Subscriptions and App Store purchases

Who processes payment: PDF Presenter Pro subscriptions are sold and billed by Apple. Payment data (card, billing, transaction history) is handled by Apple per Apple’s Privacy Policy.

What the publisher receives: the app uses StoreKit on device to check whether an active Pro subscription exists (entitlement state). The publisher does not receive your PDF content, file names, or document identifiers because of the subscription.

Related telemetry (only with analytics consent): internal screen view paywall and aggregate events (e.g., count of subscription products loaded) may be recorded. Not sent to Analytics: receipts, amounts paid, Apple ID, transaction identifiers, or billing data.

Restore purchases: this contacts Apple’s servers to revalidate a subscription on the same Apple ID; it does not upload PDFs to the publisher.

For subscription terms (renewal, cancellation, free vs. Pro plans), see the Terms of Use. Feature limits by plan (for example, slide count, recent history, and external display) are described in those Terms.

6. Legal basis, consent, and rights

Depending on LGPD, GDPR, or applicable law, bases may include contract performance, legitimate interest (technical stability), and consent for non-essential analytics.

You may request information, access, or rectification by contacting the app publisher (see below).

7. International transfers and subprocessors

Google processes data under its policies (Firebase / Analytics). Processing may occur outside your country.

• Firebase Terms
• Data Processing Terms
• Google Privacy Policy

8. Retention

Retention follows Google’s policies for each product.

9. Contact

Privacy inquiries: support@micheltlutz.me, pdf-presenter.micheltlutz.me, or App Store publisher details.