DeepScan
FeaturesHow it worksPricingDocumentationAbout
Legal

Privacy policy

This page explains what data DeepScan collects, why it is needed, how long it is kept and what you can do about it.

Version of 23 August 2026

Who processes the data

The data controller is the owner of the DeepScan service at deepscan.pro. You can reach the controller through Telegram support — the address is on the Contact page.

What we collect

We collect only what the service cannot work without. To be explicit: we do not ask for identity documents, we do not collect data about your health, religion or political views, and we do not buy information about you from third parties.

  • At sign-up: email address, password (stored only as a hash), name and a confirmed phone number
  • At sign-in: the time and address of the sign-in and details of your device and browser — this is how we spot someone else logging in
  • When two-factor sign-in is enabled: your Telegram account identifier
  • While you use the service: the domain lists you check, your selection settings and the results
  • When topping up: the amount, currency, payment method and the payment identifier from the payment provider
  • In the affiliate programme: the payout details you entered yourself
  • Technical records of errors and requests to the service

What we use it for

  • To give you access to your account and protect it from someone else signing in
  • To run the checks you start and show you the results
  • To keep your balance: credit top-ups and charge for checks
  • To answer support requests
  • To find and fix errors and to understand which sections are used
  • To meet legal requirements — for example, keeping records of payments

Cookies and analytics

The service sets only the cookies it cannot work without: a pair of session cookies that keep you signed in, and a cookie holding your chosen language. There are no advertising or tracking cookies.

There are no third-party analytics counters on the site. We count visits ourselves, on our own server, and that data does not leave it. Interface errors are sent to a monitoring system — it receives a technical description of the failure, not the contents of your tasks.

Who we share data with

We do not sell data and we do not share it for advertising. Sharing happens only to the extent the service requires:

  • Payment providers — when you top up. Card details are entered on their side and never reach us
  • Telegram — when sending confirmation codes and notifications, if you connected that channel
  • Infrastructure providers whose servers run the service
  • Government authorities — where the law requires it

How long we keep data

Account data is kept while the account exists. Check results are kept until you delete them. Payment records are kept for as long as accounting law requires. Technical logs are kept for a limited period and then deleted automatically.

How we protect data

The connection to the service is encrypted. Passwords are stored as an irreversible hash — not even we can recover the original. Database access is restricted and administrator actions are logged. Two-factor sign-in is available, and signing in from an unfamiliar address requires confirmation.

No system is completely secure. If a breach does happen, we will tell the users affected.

Your rights

To exercise any of these rights, write to support. We will respond within a reasonable time and confirm what we did.

  • View and change your data in the Profile section
  • Request a copy of the data we hold about you
  • Ask us to delete your account and the data linked to it
  • Withdraw your consent to processing — after which the service cannot be used
  • Turn off notifications, keeping only those about account security

Changes to this policy

We may change this policy — for example, when a new payment method is added. The date of the latest version is shown at the top of this page. We will announce material changes in the interface or by email.

DeepScan

Domain checks before you buy: metrics, year-by-year site history and a verdict with the reasoning behind it.

Product

  • Features
  • How it works
  • Pricing
  • Documentation

Account

  • Sign up
  • Sign in
  • Dashboard

Support

  • FAQ
  • Contact us

© 2026 DeepScan. All rights reserved.

PrivacyTerms of use