Skip to content

SwiphtBrowser - Privacy Policy

Last updated: 23 June 2026 · Effective: 23 June 2026

In a sentence

SwiphtBrowser is designed for text-only browsing without app telemetry, advertising, account sync, AI summarization, or remote classification in the current app scaffold.

Who publishes SwiphtBrowser

SwiphtBrowser is published by Pengfan Chang as an independent developer. Contact: support@swiphtgroup.com.

What the app processes

When you enter a URL, SwiphtBrowser sends a request to the website you chose to open. That website and the network providers involved in reaching it may receive normal request information such as your IP address, requested URL, user agent, request headers, cookies, and site state associated with the app-owned reader profile.

The app may store local reader history, session state, cookies, site data, subscription entitlement state, restore-key status, a generated install identifier, and settings on your device.

Direct GNU/Linux and Windows builds contact swiphtgroup.com with the generated install identifier to verify whether the one-month trial or subscription is active before browsing. The app does not send the page contents you read to swiphtgroup.com for this entitlement check.

What the current app does not do

  • No app telemetry or analytics are part of the current app scaffold.
  • No advertising SDK, account system, cloud sync service, AI summarization, or remote classification service is part of the current app scaffold.
  • Reader history, session state, cookies, site data, settings, device identifier, restore key status, and subscription entitlement state may be stored locally on the device.
  • Direct GNU/Linux and Windows builds contact swiphtgroup.com to verify SwiphtBrowser Access before browsing.
  • Websites you choose to open still receive normal network request information needed to load those pages.

Subscriptions and app stores

SwiphtBrowser Access subscriptions for direct GNU/Linux and Windows builds are handled through swiphtgroup.com checkout and the payment provider. The direct build may send an install identifier, selected plan, checkout request ID, restore key claim, and entitlement status request to swiphtgroup.com. Store builds may also check store-provided entitlement status to unlock access, restore purchases, or keep access active during supported billing grace periods.

Support requests

If you contact support, the information you send in that message, such as your email address, device details, screenshots, logs, page URLs, or description of the issue, will be used to respond to your request and troubleshoot the problem. Avoid sending passwords, payment card numbers, private documents, or sensitive page contents in support messages.

Changes to this policy

We may revise this policy as SwiphtBrowser or applicable law changes. The Last updated date at the top reflects the most recent change.