Privacy policy

Updated 2026-11-19

This page describes what data this website collects, why, where it goes and how to have it removed. No “improving your experience” phrasing: every point matches what the site actually does.

Company details
THE BOTIROFF LLC
EIN
38-4415856
Address
One World Trade Center, 42nd Floor, Suite 4205, New York, NY
All company details →

Who processes the data

The controller is the dbit.one company you deal with: THE BOTIROFF LLC (USA) for clients outside Uzbekistan, and «THE BOTIROFF» MChJ (Tashkent) for clients in Uzbekistan. Details for both are on the Company details page. For any question about this policy, or to request a copy of your data or its deletion, write to hello@dbit.one.

The site runs on our own server in Finland (Hetzner). Form submissions are not stored in a site database — how they are transmitted is described below.

What the contact form collects

When you submit the contact form we receive exactly what you typed into it, and nothing beyond that.

Name, email, phone
required — this is how we reply
Company, budget
optional; left blank, they are not transmitted
Your message
what you wrote
Interface language and page address
so we reply in your language and understand the context

Where the enquiry goes

The enquiry is delivered as a message to our team’s working chat in Telegram and is stored in that chat. It is not saved to a site database. This means Telegram’s own terms apply to the transmission as well.

The form contains a hidden trap field for spam bots. People never see or fill it; if it is filled, the submission is discarded and never sent.

Technical specification builder

The specification builder runs at dbit.one/ru/brief and dbit.one/ru/brief/gost. You describe your project there in more detail than in the enquiry form, so we treat it differently.

While you fill it in, your answers stay in your browser only, in local storage under the key dbit-tz-v1. They reach our server only when you press the send button. After sending, the draft stays in the browser so you can return to the document. To erase it, use the reset button («Начать заново») or clear the site data in your browser.

A submitted specification is stored as a file on our server in Finland, in a Hetzner data centre. A copy of the text goes to our internal panel and is linked to the client record by phone number.

Our team chat in Telegram receives a short notice: name, phone, company, project name, product type, preliminary estimate, budget if you gave one, and a link. The full text is not posted to the chat.

A submitted specification opens via a link carrying an eighteen-character random token. Only you and we know the link, and search engines do not index it.

The file on the server is kept for twelve months from submission and then deleted automatically. In the internal panel the specification stays in the client record while we work with you. Write to hello@dbit.one and we delete it earlier, from the server and the panel.

The IP address is used only for rate limiting on submission: it is held in memory for ten minutes and is not stored with the specification.

Name and phone
required; the phone links the specification to your record
Company, project name
optional
Answers and specification text
what you selected and typed
Consent to this policy
recorded with the date of its version
Retention
12 months on the server, then deletion

Technical data

The sender’s IP address is used only for rate limiting: no more than five submissions from one address per ten minutes. It is held in the server’s memory for that window, never written to disk and never shared.

Your interface language is stored in the NEXT_LOCALE cookie and in browser local storage so the site opens in the same language next time. That is a technical necessity, not tracking.

Your answer to the consent banner is stored in browser local storage under the key dbit-consent — otherwise we would have to ask on every page.

Analytics and cookies

We use Yandex Metrica, a visit-statistics counter. It includes Session Replay: it records cursor movement, scrolling and input into form fields so we can see where people get stuck.

The counter script is not loaded until you press “Allow” in the banner. If you declined or have not chosen yet, the site carries no third-party scripts and no analytics cookies at all. Declining breaks nothing: the site and the form work identically.

Once consent is given, Yandex Metrica sets its own cookies and may synchronise advertising identifiers with its partners. We do not control that part and receive no data from it; the terms are described in Yandex’s own policy.

The Meta Pixel is enabled together with Metrica. It is the counter of the Facebook and Instagram advertising system and tells Meta about page views and the fact that a request was submitted: this is how we see which ads bring clients and can show ads to people who have already visited the site. We do not send the contents of the form — name, phone, message — to Meta. The pixel sets its own cookies, and Meta processes the data under its own policy.

_fbp
browser identifier for the Meta Pixel
_fbc
Meta ad click marker
_ym_uid
anonymised visitor identifier
_ym_d
date of first visit
_ym_isad
ad-blocker indicator
_ym_visorc
Session Replay service cookie

Error tracking

When something breaks on a page — say a script fails to load — the error report goes to Sentry. That is how we learn about a failure right away: a visit counter sees the visit, not what the person got instead of the page.

What is sent: the error message and stack, the page address, the browser and operating system version. This service receives no cookies, no visitor identifier, no IP address, no session recording and no content of form fields from us.

Error tracking runs regardless of your answer in the banner: it is not behavioural observation but availability — whether you see the page at all depends on it. It collects nothing that identifies you and sets no cookies.

How long we keep it

  • Enquiry correspondence — while the project is being discussed and for as long as performing the contract requires.
  • Metrica data — on Yandex’s side, under its retention terms.
  • Meta Pixel data — on Meta’s side, under its retention terms.
  • IP for rate limiting — ten minutes in server memory.
  • Your banner choice — until you clear browser storage or this policy changes.

Your rights

You may request a copy of the data we hold, ask for it to be corrected or deleted, and withdraw consent to analytics. Withdrawal does not affect the lawfulness of processing before it.

You can withdraw analytics consent with the button at the bottom of this page — the counter stops loading and its cookies are deleted. For anything else write to hello@dbit.one; we answer within a working week.

Changes

If this policy changes in substance, the date at the top changes with it. Cosmetic edits do not change the date.

Consent is separate: the banner asks you again when what you agreed to changes — that is, the analytics. A new section that requires no consent does not cancel your earlier answer.