Kaizen Official Group

Data and privacy

This describes how the site is built, technically. It is not a legal document and not a statement of compliance with any jurisdiction — those should come from a lawyer, not an engineer. What follows are facts you can verify.

What the site does not have

No way to collect anything about you

Forms

None. Submitting data through this site is technically impossible.

Cookies

The site sets none and reads none. There is no consent banner because there is nothing to consent to.

Third-party analytics

No Google Analytics, no Yandex Metrica, no pixels, no third-party counters, of any origin. How many times a page was opened is counted by the server itself, from its own log.

Fingerprinting

The pages carry no scripts at all, so there is nothing that could collect device characteristics.

External resources

Fonts are the ones already on your system; styles and images are served from here. Your browser contacts this site only.

Country detection

You pick the language yourself with a link. The site does not look at where you are coming from and serves no region-specific content.

None of this requires taking my word for it: open your developer tools, the Network tab, and look at the list of requests.

What the server writes down

A server with no records at all cannot be operated

Request log
Date and time, request method, the page address without the query string, protocol version, response code, response size and processing time. It contains no IP address, no User-Agent, no referrer and no cookies. The format was changed specifically for that, and an automated test proves on every change that those parameters never reach the log.
Error log
Kept, deliberately: a server without one can neither be fixed nor defended. Its format is fixed by the web server and cannot be changed, so error records may contain the address of the requester. The file is rotated every hour, addresses and query parameters are stripped at rotation, and anything older than seven hours is deleted entirely.
Operational counters
Aggregate figures are derived from the request log: how many requests, how many responses per class, how many bytes served, how long they took. These are numbers, not records about people. Only those numbers leave the server; the log lines themselves do not.
Page and click counters
On top of those there are counters per section: how many times the home page, the services, the case studies and the contact page were opened, how many times the Telegram or email button was used, and how many visitors arrived through the link in a classified ad. The same log is read the same way: a number tied to a section is incremented. Who opened it, from what address, with which browser, and whether it was one person or ten is not in those numbers, because it is not in the log either.

The rest

Hosting, outbound clicks and correspondence

Where the site is hosted
The server is in Europe, outside Russia, and the site is reachable internationally. Requests therefore travel through infrastructure in that country. No data you enter is involved — there is nothing on the site to enter.
Opening Telegram or email
Some of the contact buttons go through an internal address of this site that redirects outward immediately. That is the counting: the server adds one to a number and sends you on. No intermediate page, no tag in the address and no identifier appears on the way. Next to every such button the contact page also carries the direct form — the handle as plain text and the email address — and that one does not go through the server at all. Once you click, you are in a third-party service where their rules apply.
Correspondence
I use whatever you write to me only to reply and to discuss the task. I do not pass it to third parties and do not add it to mailing lists — there are none. The correspondence stays where you started it.

Why the site is built this way: I offer infrastructure and security work. A site that pulls in third-party scripts and sets advertising cookies would contradict the offer. Collecting nothing was simpler than explaining later why I collected it.

If anything here looks incomplete, ask and I will make the text more precise. This document describes how the site actually works at the time of publication.