• Home
  • /
  • Legal
  • /
  • Privacy Policy
Legal document

Privacy Policy

This page explains what Proxynade stores, why it is stored, and how account, order, payment, support, and security data is handled across the website and dashboard.

Last updated: 2026-04-23 Scope: website, dashboard, tickets, email Contact: postmaster@proxynade.net

Plain-English summary

  • Proxy-only signup asks for email and password, not full legal name.
  • Full legal name can be requested later for dedicated server rentals or ownership reviews.
  • Discord details are optional and only used when Discord support is chosen.
  • Email verification, session records, and security logs help protect accounts and orders.

1. What this policy covers

This policy applies to the public website, account registration, login, dashboard use, proxy orders, pool access, dedicated server rentals, payment processing, support tickets, verification emails, and abuse or security handling tied to the Proxynade service.

It covers information provided directly by users and technical records generated while the service is being operated, secured, billed, and supported.

2. Contact points

  • Legal, privacy, billingpostmaster@proxynade.net
  • Abuse reportsabuse@proxynade.net
  • Service supportDashboard ticket flow first
  • Community supportDiscord support for general help
  • Service nameProxynade
Important: If a request affects account ownership, billing, or deletion, enough information may be required to verify identity before changes are made.

3. Information collected

Accounts, proxy orders, and pool access

  • Email address.
  • Hashed password and authentication state.
  • Session records, login IP history, and user agent data.
  • Proxy orders, pool access balances, usage records, billing period, payment status, and public order IDs.
  • Litecoin payment addresses, transaction references, and order totals.
  • Support tickets, issue type, and user-provided ticket details.
  • Operational and security logs needed to run and defend the service.

Dedicated server rentals and ownership reviews

Full legal name can be requested when a user rents a dedicated server or asks for a sensitive ownership review. That field is not required for basic proxy-only signup.

Optional Discord support data

Discord user ID is stored only when a user chooses Discord-based support or shares Discord details during a support request.

4. How information is used

Account, proxy, and pool operations

  • Create and secure user accounts.
  • Verify email ownership before dashboard use.
  • Process proxy orders, pool access, and maintain service state.
  • Confirm cryptocurrency payments and detect payment issues.
  • Deliver proxy, pool, and server credentials.
  • Provide support, issue tickets, and send service emails.
  • Prevent abuse, investigate incidents, and enforce service rules.
  • Maintain audit trails for sensitive actions.

Dedicated server identity checks

Identity details can be reviewed when needed for dedicated server rentals, ownership disputes, or other sensitive account actions.

5. Cookies and local storage

Proxynade uses essential cookies and browser storage for authentication, CSRF protection, dashboard state, and security. These are required for account access and order handling. If non-essential analytics or marketing tools are added later, this document should be updated before they are enabled.

6. Sharing and disclosure

Proxynade does not sell personal data. Limited information may be shared when needed to operate the service or respond to legal and abuse matters.

  • Infrastructure and hosting providers.
  • Mail delivery and routing systems.
  • Payment and blockchain verification providers.
  • Infrastructure vendors involved in service delivery.
  • Law enforcement or regulators where disclosure is legally required.

7. Retention

Data is retained as long as it is needed for active service delivery, account security, payment reconciliation, support history, abuse handling, legal obligations, or internal audit needs. When data is no longer required, it may be deleted, anonymized, or archived.

8. Security measures

  • Passwords are stored as hashes, not plaintext.
  • Session invalidation and token revocation are enforced.
  • Admin actions are audited.
  • Sensitive endpoints use CSRF protection and cookie-based auth.
  • Email verification is required before login succeeds.

9. Your choices

  • Update your profile fields from the dashboard.
  • Enable or disable two-factor authentication.
  • Revoke active sessions.
  • Ask for account deletion through support.
  • Request access, correction, or deletion review by email.

10. Policy updates

This policy may change as the service changes. Material edits should be reflected on this page with a new update date. Continued use after an update means the revised policy applies from that point forward.