Privacy Policy

Last updated: June 12, 2026

This policy covers the Livingstone iOS app, the Livingstone browser extension, this website (the Livingstone Pro checkout), and the license system behind them. Each product may have slightly different data practices; see the relevant section below.

1. What we collect

• Purchase records: when you subscribe, we store your license key, subscription status, the email address from your order, and Paddle's customer, subscription, and transaction identifiers. We need these to issue your key, validate it, and provide support.
• License checks: when the extension or the Activate page verifies a key, our server processes the key itself. We do not collect your search queries or browsing history through this website.
• Device seats (sharing prevention): so a key works on only one device at a time, the extension sends a random device identifier it generates on install (not tied to your identity) with each license check. We store that identifier, a coarse device label (e.g. "Chrome on Windows"), and the time of the last check, alongside a salted, one-way hash of the connecting IP address used only as an abuse signal. We never store your raw IP address. Activating on a new device replaces the previous device's seat.

2. What we don't collect

• Payment details: card numbers and payment methods are handled entirely by Paddle, our merchant of record. They never reach our servers. See Paddle's Privacy Policy.
• Tracking: this site sets no advertising or analytics cookies. The Paddle checkout overlay may set cookies strictly necessary to process your payment and prevent fraud.

3. How your data is used

• To generate, deliver, and validate your license key.
• To keep your subscription status in sync with Paddle (renewals, failed payments, cancellations) via signed webhooks.
• To respond to support, refund, and transfer requests.

We do not sell your personal data or share it with third parties for marketing.

4. Where it's stored

License records are stored in a managed Postgres database (Neon) and processed by serverless functions hosted on Vercel, both over encrypted connections (HTTPS/TLS). Access is restricted to the operator of Livingstone.

5. Retention

We keep purchase and license records for as long as your subscription exists and afterwards only as long as needed for support, fraud prevention, and legal/accounting obligations.

6. Your rights

Depending on your location (e.g., GDPR in the EU/UK, CCPA in California), you may have rights to access, correct, export, or delete your personal data. Email questions.livingstone@outlook.com and we will respond within 30 days. Note that deleting purchase records may deactivate your license.

7. iOS App Specifics

Search History (Local Only)

The Livingstone iOS app stores your recent search queries locally on your device, in the app's private database. This is never sent to our servers and is deleted only when you clear the app's cache or uninstall the app. Your searches remain entirely on your device.

License Validation (Pro Tier)

If you subscribe to Livingstone Pro via Apple In-App Purchase, the app validates your subscription status with Apple's servers (not with Livingstone's). Your subscription status is checked locally on your device and communicated directly to Apple. We do not receive or store your Apple ID, payment information, or subscription details.

Search Display (Google Results)

When you search, the app displays Google results in an embedded web view. This communication between your device and Google is the same as if you visited Google in Safari—Google receives your query and device information per their own privacy policy. Livingstone acts as a view layer only and does not log or inspect these queries after they leave your device.

Apple Frameworks

The app uses Apple's on-device translation framework to translate search results. Apple handles the translation processing and does not share translation requests with Livingstone. If you opt into crash reporting during TestFlight or after App Store release, Apple collects anonymized crash logs per their privacy policy. Livingstone does not receive or store these logs.

No Analytics or Tracking

The iOS app does not use analytics, advertising cookies, or any third-party tracking. We do not know how you use the app or what you search for.

8. Changes

We will post any changes to this policy on this page with an updated date above.

9. Contact

Jaime Vergara · questions.livingstone@outlook.com