Legal · Privacy

Privacy notice

How ReverseIPData handles information needed to operate accounts, payments, support, security, and the service.

Last updated
9 August 2026
Applies to
Website and service
Contact
Official support
Language
English

Scope

This notice covers reverseipdata.com, its account and checkout areas, the public preview, licensed access, support communication, and operational security records controlled by the ReverseIPData operator.

Information we process

  • Account identifiers such as username, email, profile selection, and account timestamps.
  • Order and payment records such as selected plan, network, order reference, payment wallet, amount, provider status, and public blockchain transaction details.
  • Service activity needed to fulfill access, operate scans, enforce allowances, diagnose errors, and protect availability.
  • Technical and security information such as IP-derived security data, user-agent-derived security data, session records, rate-limit events, and audit events.
  • Support messages and the information you choose to provide.
  • Lookup input required to answer and protect a public or licensed request.

Information you should not send

Do not provide wallet seed phrases, private keys, account passwords, API secrets, client keys, certificates, private order URL tokens, unrelated customer records, or sensitive personal information that is not necessary for support.

Why information is processed

Information is used to create and secure accounts, authenticate sessions, create and verify orders, activate access, deliver service, enforce plan limits, prevent abuse, investigate errors, provide support, maintain records, comply with applicable obligations, and improve reliability and usability.

Payment processing

Crypto checkout requires order details and transaction state to create a unique invoice and confirm whether the matching blockchain payment was received. Public blockchain transactions are inherently visible on their networks. Payment verification may involve the configured invoice provider and related infrastructure.

Sessions and local storage

Strictly necessary session cookies support sign-in, request verification, checkout, private order status, rate controls, and security. The current website does not need advertising cookies to provide its core workflow. Browser storage may be used only where required for interface state or security.

Service providers and disclosure

Information may be processed by hosting, payment, email, security, and support providers where necessary to operate the service. It may also be disclosed when reasonably necessary to comply with law, protect users or the service, investigate abuse, or establish and defend legal claims. ReverseIPData does not sell account passwords or wallet secrets.

Retention and security

Records are retained only as reasonably necessary for active access, account security, payment and accounting records, support, abuse prevention, disputes, backups, and applicable legal requirements. Retention periods vary by record type. Access is limited by operational need, and technical safeguards are used to reduce unauthorized access. No online system can promise absolute security.

Choices and requests

Depending on applicable law, you may request access, correction, deletion, or other handling of account information. Some records may need to be retained for security, payment, accounting, dispute, or legal reasons. Contact official support with enough information to identify the account and request; do not send authentication secrets.

Children

The service is not directed to children and is intended for users who can lawfully agree to the applicable terms. Do not create an account if you cannot legally use the service in your jurisdiction.

Changes to this notice

This notice may be updated as the service, providers, or legal requirements change. The updated date will be shown on this page. Material changes will be communicated where reasonably appropriate.

Contact

Use the official ReverseIPData support account listed on the contact page for privacy questions. Include the account username or email and the nature of the request. Do not send a password, seed phrase, private key, or private session link.