RAM-only VPN routing
VPN traffic is routed through RAM-only servers. PhantomPath does not retain browsing activity, DNS queries, VPN traffic content or message content in its customer database.
Technical privacy architecture
“Zero logs” should describe what is not recorded, not pretend that payments, provisioning and security happen without any operational events. This page separates VPN activity, communications content, transaction data and system operations clearly.
VPN traffic is routed through RAM-only servers. PhantomPath does not retain browsing activity, DNS queries, VPN traffic content or message content in its customer database.
VPN passes do not require a traditional customer account, password or email address. Access codes are time-limited and exist for the duration of the purchased session.
Message payloads processed by PhantomPath-controlled systems are automatically deleted server-side within 30 seconds of delivery. Standard messaging uses TLS and voice transport uses SRTP.
Payment providers retain their own transaction records. PhantomPath receives only the limited order information needed for provisioning, refunds, fraud prevention, accounting, support and legal obligations. It is not linked to VPN traffic or communications content.
Limited payment, provisioning, error, security, system and administrative events may be logged. These operational records are rotated, size-capped and cleaned up, and do not contain browsing activity, traffic content or message content.
Supported USA numbers may require mobile-number verification for telecom compliance, fraud prevention and activation. The submitted number is used for that purpose and is not intentionally associated with VPN traffic, session keys or message content.
It means PhantomPath does not log or retain browsing activity, DNS queries, VPN traffic content or communications content. It does not mean that a functioning service can hold no operational record whatsoever. Limited payment, provisioning, error, security, system and administrative events may exist for defined operational or legal purposes.
PhantomPath routes VPN traffic through RAM-only servers and does not retain browsing activity or VPN traffic logs in its customer database. RAM-only infrastructure reduces persistent storage at the VPN-routing layer.
Yes. PhantomPath VPN passes do not require a traditional customer account, password or email address. A time-limited access code is generated for the purchased duration.
No. Payment and limited order records remain operationally separate from VPN traffic, browsing activity, session content and communications. Payment providers retain their own transaction records under their policies and legal obligations.
Message payloads processed by PhantomPath-controlled systems are automatically deleted server-side within 30 seconds of delivery. No message history is retained in the PhantomPath customer database. Telecom providers may have their own legally required processing and retention practices.
Operational logs record events needed to provision and protect the platform, such as payment confirmation, errors, security events and administrative actions. They are distinct from user-activity logs because they do not contain browsing activity, VPN traffic content or message content.
PhantomPath processes the submitted number for telecom verification and service-protection purposes and does not intentionally associate it with VPN traffic, browsing activity, session keys or message content. Relevant verification providers may process it under their own terms.
No system should promise absolute anonymity without qualification. PhantomPath makes specific, testable claims about data minimisation, no mandatory traditional VPN account, RAM-only routing, activity-log exclusions, communications-content deletion and payment-data isolation.