Privacy Policy
Halveo is committed to safeguarding your privacy and network security. We strictly adhere to data minimisation principles: our control platform and ledger systems never record your browsing history or traffic payloads, never sell user data, and bundle zero third-party analytics SDKs by default.
Data Controller
Core Principles & Commitments
Platform-Level Activity Minimisation
Our control platform and databases never collect, store, or analyse your destination websites, IP addresses, DNS queries, payload contents, or mappings between your source IP and accessed destinations.
Zero Third-Party Analytics SDKs
Our website and client applications do not integrate any third-party analytics, behavioral tracking, or advertising attribution SDKs (such as Google Analytics, Firebase, Facebook Pixel, etc.).
Never Sell or Share User Data
We never sell, rent, monetize, or disclose your personal information or VPN usage data to any third-party advertisers, data brokers, or commercial organizations.
1. Information We Collect & System Basis
We adhere to the data minimisation principle, collecting only data strictly required to maintain account authentication, device authorisation, and subscription billing. Every data item directly corresponds to our underlying data models:
A. Account & Identity Information
Collected fields: registered email address, display name, optional phone number, scrypt password hash, email verification timestamp, last login timestamp, account status.
System basis: packages/domain/commerce.py (Customer model, table customers).
Purpose: Used for user authentication, password recovery, and essential service notifications. We never store plaintext passwords, only irreversible salted scrypt cryptographic password hashes (apps/api/security.py).
B. Login Sessions & Security Tokens
Collected fields: session token hash, issuance and expiration timestamps, revocation timestamp, client environment hash, login IP address.
System basis: packages/domain/commerce.py (CustomerSession in table customer_sessions and CustomerOneTimeToken in table customer_one_time_tokens).
Purpose: Used to maintain multi-device login sessions, prevent token replay attacks, and perform security risk control. Sessions become invalid immediately upon expiration or logout.
C. Connected Devices & Connection Credentials
Collected fields: device display name (chosen by the user), randomly generated internal device identifier (not a real email), device lifecycle status, encrypted secret reference.
System basis: packages/domain/commerce.py (VpnClient model, table vpn_clients).
Purpose: Used to enforce the maximum concurrent device allowance of the subscription plan, provision server node authorization, and manage per-device credential revocation. Real credentials are encrypted in an isolated Secret Store (Vault).
D. Orders & Payment Transaction Records
Collected fields: order number, amount in cents, currency, payment status, completion timestamp, third-party payment event identifiers.
System basis: packages/domain/commerce.py (Order in table orders and PaymentEvent in table payment_events).
Purpose: Used for order fulfillment, accounting reconciliation, and statutory financial compliance auditing.
E. Traffic Accounting & Immutable Incremental Ledger
Collected fields: accounting period start/end timestamps, incremental byte counter (delta_bytes), traffic direction (INBOUND / OUTBOUND), traffic source type.
System basis: packages/domain/observability.py (TrafficLedger model, table traffic_ledger).
Purpose: Used for subscription quota deduction and usage reconciliation. Ledger entries are immutable once written. ★ The ledger strictly records total incremental bytes transferred and contains zero domain names, destinations, URLs, or packet contents.
F. Operational & Security Audit
Collected fields: HTTP request method, API path template, action name, execution outcome, request IP address, user-agent hash, request trace ID.
System basis: packages/domain/audit.py (AuditLog model, table audit_logs).
Purpose: Used to defend against malicious attacks, investigate system errors, and ensure platform availability. ★ The audit system strictly prohibits logging private keys, passwords, tokens, or full VLESS links (the config retrieval endpoint only audits that a config was read, never what it said).
2. Platform Data Boundaries & Excluded Data
In our platform architecture and data storage systems, Halveo strictly enforces data minimisation and explicitly excludes the following from our control plane and databases:
- The control platform does not record any destination website domains, web URLs, remote IP addresses, or service port numbers.
- The control platform does not record any network payload contents, transferred files, unencrypted message text, or application data.
- The control platform does not record DNS query resolution histories or user browsing activity.
- The control platform does not create or maintain any mapping between a user's original connecting IP and accessed destinations.
- Audit and logging systems strictly filter out plaintext credentials, UUIDs, or full VLESS share links.
3. Third-Party Services & Data Protection
We strictly limit third-party involvement and require all partners to provide equivalent privacy and security safeguards:
Licensed Payment Processors
Online payments are processed by regulated, licensed payment providers (e.g. Stripe). Payment providers handle payment credentials directly under the highest industry security standard (PCI-DSS); we never receive or store your full credit card number or CVV.
Any data transmission to third parties is governed by strict confidentiality and data processing agreements requiring third parties to maintain data protection standards equivalent to this policy.
4. Data Retention & Account Deletion Policy
We retain data only for the duration necessary to fulfill the purposes described in this policy and satisfy statutory obligations:
User Rights & Self-Service Controls
You have the right to inspect your account data, export available configurations, and revoke individual device credentials at any time in the customer center. To request complete account deletion, please contact our support email (hello@halveoapp.com), and we will execute personal data erasure and account dissociation upon identity verification.
Account Deletion Processing Workflow
Upon receiving and confirming your account deletion request via customer support, the system executes the following process:
- Complete erasure of personal identity: your registered email, display name, phone number, password hash, active sessions, and one-time tokens are permanently deleted or irreversibly anonymized.
- Immediate credential invalidation: all registered VPN device credentials associated with your account are instantly revoked, terminating all active connections.
- Statutory compliance retention: in accordance with legal tax, accounting, anti-money laundering, and anti-fraud regulations, historical payment transaction records and aggregate incremental traffic ledgers are retained for mandatory statutory periods. All retained records are completely unlinked from your deleted identity and cannot be reverse-attributed to any individual.
5. Data Security Safeguards
We employ end-to-end modern encryption protocols (TLS 1.3 / REALITY), an isolated Secret Store (Vault) for sensitive credentials, row-level database authorization, and strict least-privilege access controls to prevent unauthorized access, tampering, or disclosure.
6. Contact Information & Policy Updates
If you have any questions, suggestions, or wish to request account and data deletion regarding this Privacy Policy, please contact our support team: hello@halveoapp.com
If material changes are made to this policy, we will provide prominent notice on our website and update the effective date. We encourage you to review this page periodically to stay informed about our privacy practices.