Privacy Policy
Effective date: October 26, 2026 · PointLens Chrome extension v0.2PointLens processes flight-page content on your device to calculate points equivalents. It does not send flight searches or saved comparisons to its licensing server. Optional Pro licensing uses a licence key, a random browser identifier and an activation token.
1. Who is responsible
This policy describes data handled by the developer of PointLens and its associated support and Pro licensing services. For questions or privacy requests, contact trifocal.store@gmail.com.
2. What the extension reads
When you explicitly activate PointLens on a supported flight-search tab, it reads the page address to check whether the site is supported and examines visible page text to identify fare amounts. It adds points-equivalent badges and a comparison panel. Detection is heuristic and can also encounter text or amounts unrelated to fares. Page content is processed locally; the extension does not transmit that content to the licensing server.
PointLens does not collect a browsing-history log, record keystrokes or mouse activity, read personal messages, or request your airline password, card number, bank details or reward-account balance.
3. Data stored on your device
- Your selected currency, personal point valuation, assumed award fees and display setting.
- If you use Pro: the licence-server address, a randomly generated browser activation ID, and an activation token.
- If you save a Pro comparison: its user-entered name, currency, cash fare, award points, taxes, calculated value and save time.
These items are stored in Chrome's local extension storage, not Chrome sync storage. You choose whether to export saved comparisons to a CSV file. An exported file is under your control and may be synced or shared by other software you use. Do not put sensitive personal information in comparison names.
4. Optional Pro activation and verification
Pro requires a configured licensing service. Activation sends the licence key and random browser activation ID to the server address shown in the extension. The service returns a token that the extension uses to verify entitlement when you save or export Pro comparisons. Removing an activation sends the token to that service to release the browser slot.
The PointLens licensing backend stores a licence record, payment-session identifier, purchase email when provided by checkout, active status, creation time, and browser activation records. Licence lookup keys and activation tokens are hashed in the database; the licence key itself is also retained to deliver it after purchase and support recovery. Access to Pro requires online verification. Do not enter your key into an untrusted server address.
Network services necessarily receive technical connection information such as IP addresses. Hosting or payment providers may keep security and operational logs according to their own policies. PointLens does not derive your location from those connections or use them for advertising.
5. Payments and availability
The v0.2 package includes an optional Pro licensing flow. Live purchases must remain disabled until the developer has configured and tested checkout, licence delivery, seller information and applicable purchase terms. If purchases are enabled, payment is handled by the external payment provider identified at checkout, rather than by the extension. The supplied checkout integration uses Stripe. Card-entry details are not passed to the extension; the licensing backend receives the payment-session and purchase-email information described above. Review the provider's privacy policy and purchase terms before paying.
6. How data is used and shared
Data is used to provide fare comparisons, save and export your shortlist, activate and verify Pro, prevent excess browser activations, handle payment confirmation and refunds, and respond to support requests. Support emails contain whatever information you choose to send; avoid sending passwords, full card numbers or unnecessary travel documents.
PointLens does not sell user data, use it for targeted advertising, use it for creditworthiness or lending decisions, or use it for purposes unrelated to these functions. Service providers may process data as needed for hosting, payment processing and email support. Data may also be disclosed when legally required.
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
7. Retention and deletion
Local settings and saved comparisons remain until removed through Chrome's extension/site-data controls or by uninstalling the extension. Exported files are not deleted when you uninstall. Removing a Pro activation deletes that activation record from the licensing service; it does not automatically delete the purchase record or saved local comparisons.
Purchase and licence records are retained to provide ongoing entitlement, support and payment-related obligations. To request access, correction or deletion, email the contact above. The developer will explain what can be deleted and any records that must be retained for applicable legal or accounting obligations. Deleting a licence record may prevent further Pro access. This policy does not promise automatic deletion on a fixed schedule.
8. Security
Production licensing and checkout connections must use HTTPS. Do not use an HTTP development server for live purchases. Local extension storage is not a password vault or encrypted backup. No storage or transmission method is completely secure. No remotely hosted executable JavaScript is used by the packaged extension; licence responses are data, not executable code.
9. Your choices and other websites
You may use basic comparison features without activating Pro, decline optional licensing-server access, uninstall the extension, or contact support about personal data. Flight-search websites, browser services, the static-site host, payment providers and your email provider operate under their own policies. Privacy rights vary by jurisdiction; contact us to exercise applicable rights.
10. Changes
This page will be updated when PointLens data practices change. The effective date will identify the latest update. Material changes may also require an updated extension disclosure or consent.