Privacy Policy

The no-logs statement

We do not record the destinations you request, the contents of your traffic, or any response body passing through the gateway. Our routing layer holds the connection tuple only for as long as the connection is open, in memory, and discards it on close. There is no destination log to hand over, subpoena or leak.

What we do meter is volume: bytes in and out per account, per pool, per calendar day. Metering is how prepaid balance is enforced, and it is deliberately built to answer "how much" without ever answering "where to".

Account data

Accounts are created through Telegram, so we hold your Telegram user ID and the timestamps of account creation and last login. If you add an email address in Settings to enable web login, we also hold that address and a hashed password (Argon2id, never reversible). A display name is optional.

We do not ask for your legal name, address, phone number or any identity document. There is no KYC on this service.

Payment data

Payments are crypto only. We store the transaction hash, the asset, the amount credited and the confirmation timestamp — the minimum needed to reconcile a top-up and resolve a dispute. We never see card numbers or bank details because we never accept them.

On-chain data is public by nature and outside our control. If chain-level privacy matters to you, choose your asset and funding path accordingly before sending.

Retention periods

Aggregate daily usage totals are retained for 90 days for billing dispute resolution, then permanently deleted. Per-request records do not exist, so there is nothing to delete.

Gateway error diagnostics are retained for 7 days and contain a truncated account identifier and an error class — never a destination hostname or URL.

Account records and payment reconciliation data are retained while your account is open, and for 12 months after closure to satisfy accounting obligations. Then they are erased.

How residential IPs are sourced

Residential exit capacity comes from partner networks whose participants opted in explicitly, in exchange for a service or payment, with a plain-language disclosure that their connection will be shared. Participants can withdraw at any time and capacity is removed within minutes.

We do not accept capacity from malware, hidden bundling, or SDKs that fail to disclose traffic sharing. Partners are audited on onboarding and re-audited annually; failing an audit removes their capacity from the pool immediately.

Exit nodes never see your account identity. Traffic is decoupled at the gateway so a residential participant cannot associate a request with a Ludax customer.

Website and cookies

This marketing site sets no advertising or tracking cookies and runs no third-party analytics that profile you across sites. The dashboard sets a single first-party session cookie, strictly necessary for authentication, which expires when you log out.

Fonts are served from Google Fonts, which means Google receives your IP address when the stylesheet loads. If that matters to you, block it — the site is fully readable with system fonts.

Legal requests and disclosure

We respond to valid, properly served legal process from a jurisdiction with authority over us — and no further. In practice we can only produce account registration data, payment reconciliation records and aggregate byte counts, because destination logs do not exist.

We reject informal requests that are not backed by valid process. Where we are legally permitted to notify you of a request, we will.

Your rights

You can request a copy of everything tied to your account, correct inaccurate details, or ask for full deletion. Contact us on Telegram from the linked account, or from your registered email address.

Deletion removes account records, credentials and linked identifiers. Aggregate anonymised volume statistics with no link to you may be retained for capacity planning.