Privacy Policy

PureFlow Network operates the PureFlow service. This Policy explains data handling for our website, Telegram Mini App, accounts, payments, and network transport. Website activity and service transport telemetry are different data categories and are described separately.

PureFlow provides encrypted transport tunnels. We do not inspect, record, or store the contents of application payloads or personal communications carried inside user packets. This commitment concerns communications content; protocol and header information used for destination identification and routing is processed through the sniffing described below.

Data Plane nodes maintain local transport access logs (access.log). Connection events can contain timestamps, client credential UUIDs, source IP addresses, and destination network endpoints or hostnames. The node telemetry daemon reads source IP addresses and credential identifiers from these logs to track active IPs and enforce concurrent-device limits. Separate traffic counters and the backend telemetry collector aggregate bandwidth usage for quotas and service operation. Operational telemetry supports connection counting, limit enforcement, and node health monitoring.

A credential UUID identifies network access credentials and can be associated with an account or subscription. Transport access logs can contain destination information even though the live daemon tracker extracts source IPs and credential identifiers rather than building a destination history.

VLESS inbounds enable HTTP, TLS, and QUIC protocol sniffing for destination identification and routing. This processing reads relevant protocol information; it is not restricted to emergency fallback routes. Destination hostnames may therefore appear in local access logs. We do not claim that transport metadata is never recorded.

When concurrent connection limits are exceeded, security incident records retain source IP addresses, timestamps, and credential identifiers. These records support device-limit enforcement and protection against credential abuse and unauthorized distribution. They are distinct from the live active-IP tracking window.

• Telegram account identifiers, including user_id and username, are used to recognize accounts and provide access.
• If you use email access or account recovery, account records include your email address and verification information. Registration records may also include the source IP address and country.
• Billing records include transaction ID, payment-provider references, amount, currency, and status, together with the subscription associated with the purchase.
• When you contact support, we process the information you provide to investigate the request, including an order reference and relevant device or connection details.

These records support account administration, access delivery, payment reconciliation, fraud prevention, and support. Do not send private connection credentials or unrelated communications content in a support request.

The website loads Umami, Microsoft Clarity, and Meta Pixel. These tools process website usage and browser interaction information. Meta Pixel receives PageView events and events for selected actions, including Lead and InitiateCheckout when relevant landing-page buttons are used.

Analytics providers receive browser requests, which can include network and device information. Their tools may use cookies or similar browser storage under their own policies. These website events are separate from traffic passing through your encrypted tunnel. Loading this website is not an assurance that analytics scripts are absent.

PureFlow also uses a locale preference cookie and authentication/session cookies for language selection and account access. Browser settings can restrict cookies and tracking requests, although restricting essential cookies may affect sign-in or saved preferences.

We do not compile or retain personal browsing profiles or dossiers from operational telemetry or account data. We do not sell operational or account data to third parties or use it for commercial behavioral advertising. Website analytics are separately described below; this commitment is not a claim that the website has no analytics or tracking.

Operational processing serves delivery of the service, bandwidth accounting, concurrent-device enforcement, security, and node health. Account and billing processing supports your subscription, payments, support requests, and applicable recordkeeping obligations.

Service delivery involves infrastructure providers, Telegram where you use Telegram features, payment providers, and the website analytics providers identified above. Whop Inc. and Paddle.com Market Ltd. act as Merchants of Record for transactions made through their platforms and process purchase and tax information under their respective policies.

Data relevant to a service or transaction may be handled by the provider delivering it. Information may also need to be disclosed where required by applicable law or to address abuse and protect the service and users. Such processing is distinct from selling operational or account data for advertising.

Local access logs, stored security incidents, account records, payment records, and aggregate usage counters have different operational purposes. The daemon's live tracking window is not a deletion deadline for access logs or database records. This Policy does not promise that all operational data exists only in memory or is immediately erased after a connection.

Records are handled for service operation, security, support, dispute handling, and applicable recordkeeping needs. We use access controls and safeguards appropriate to those purposes, but no storage or transmission system can be guaranteed entirely risk-free. Contact us for information about retention or a deletion request concerning your account.

PureFlow operates a distributed network and works with service providers. Information may be processed in countries different from your own as needed to deliver the service or process a transaction. Applicable protections and obligations depend on the processing and jurisdiction; contact us with questions about a particular account or transaction.

You may request information about your personal data, correction of inaccurate records, or deletion. Where applicable law provides additional rights, including access, portability, restriction, objection, or complaints to a competent authority, those rights remain available. We may need to verify account ownership, and some records may need to be retained for applicable obligations or unresolved disputes.

For privacy requests contact legal@pureflow.net. For account assistance contact support@pureflow.net or @PureFlowVPN_SupportBot. Explain the request without sending passwords or private connection credentials.

We publish changes to this Policy with an updated revision date. Read the current Policy when using the service and contact us if a description requires clarification. This Policy is read alongside the Terms of Service and Refund Policy.