No-logs policy
This is DemonProxy’s signature commitment, stated plainly: we do not log your proxy traffic. No destination addresses, no connection timestamps, no payload contents, no browsing history. There is no traffic log to subpoena, sell, or leak — because we never build one. This page sets out exactly what that means, what we do and do not store, and how the policy is enforced. Last updated: June 2026.
No traffic, no destinations, no inspection
Most providers that advertise privacy still quietly retain connection metadata “for abuse prevention.” That metadata is the leak. We draw the line at traffic content and connection records — we do not keep them at all.
Your proxy traffic is never recorded
We do not log the contents of the traffic that passes through our proxies. We do not record the websites, hosts, or IP addresses you connect to. We do not store request or response bodies, URLs, query strings, cookies, or HTTP headers. There is no archive of what moved through your session, because we never write one.
No connection timestamps or destination logs
We do not keep per-connection logs that pair your account with a destination at a moment in time. We do not retain the granular connection timestamps, destination hostnames, or per-request records that would let anyone reconstruct your activity. The link between “who” and “where and when” simply does not exist on our side.
No deep packet inspection
We do not perform deep packet inspection (DPI). We do not crack open, parse, or analyze the payloads moving across the proxy. Our role is transport: we move bytes between you and your destination and stay out of the contents entirely.
No bandwidth content capture
We meter bandwidth as an aggregate byte count for billing and capacity, but we never capture what those bytes contain. The number of bytes you used is not a record of what you did with them.
The minimum it takes to run an account
A no-logs proxy is not a no-data company. To operate accounts, bill fairly, and stop abuse, we keep a thin slice of operational data — and nothing that describes your traffic.
Account data
We store the email address you register with and a salted, hashed password — never the password itself. This is the identity needed to give you access and let you sign in.
Billing records
We retain the billing records required to run a paid service and meet tax and accounting obligations: plan, invoices, and aggregate usage totals. Card and payment details are handled by third-party payment processors; we do not store full payment instruments ourselves.
Minimal anti-abuse signals
To keep the network healthy we retain a small set of aggregate, short-lived anti-abuse signals — such as total bytes per account, connection counts, and coarse rate metrics. These describe load and abuse patterns, not the content or destinations of your traffic, and they are pruned on a short retention window.
No-logs policy at a glance
How the no-logs policy is enforced
A promise is only as good as the way it is built. The policy holds because the systems are designed not to collect the data in the first place.
No-collect by design
The strongest enforcement is architectural: our proxy layer is configured not to write traffic or connection logs to disk at all. You cannot hand over, sell, or lose a record that was never created. We cannot be compelled to produce traffic logs we do not hold.
No sale of data, ever
We do not sell, rent, or trade user data to advertisers, brokers, or any third party. Operating revenue comes from subscriptions, not from your information.
Lawful requests
If we receive a lawful request, we can only ever provide the limited account and billing data described above — never traffic or destination logs, because none exist. Read how this fits the wider picture in our Privacy Policy.
Run one proxy off the record, free
Take a real Polish mobile IP for an hour — no card, no logs of what you do with it. Confirm it stays clean under your workload, then pick a plan.