Data

How I handle personal data

Updated: July 2026

I run this site myself, and I handle the data myself too. I collect exactly what is needed to reply to you and to give you access to the research — and nothing beyond that.

Below is an honest list: what is collected, where it is stored, why, and how to delete it. No legal boilerplate.

What data I collect

Only what you leave yourself, plus anonymous visit statistics:

  • The /contact form: your name, a contact channel (email or Telegram), and optionally your company and a few words about your question.
  • The research gate: your name and email — to send you a sign-in link and unlock the gated chapters.
  • Analytics: an anonymous page-view counter with the category of the visit source (Telegram, LinkedIn, search, or an AI assistant — no URLs, no identifiers) plus anonymous in-tool events. All of it with no personal data, no IP addresses, and no cookies. I honor Do Not Track and Global Privacy Control — when they are on, nothing is recorded.

Where the data is stored

On my own servers in the European Union and in Russia. I do not hand data to third-party CRMs, ad networks, or email services — there simply aren't any here.

Why I use it

Contact details are used only to reply to you personally. The name and email from the gate are used to send your sign-in link and to unlock the gated chapters. Anonymous analytics helps me understand what on the site is useful and what isn't.

I don't build profiles, run funnels, or use your data for advertising.

AI tools: what goes to the model

Three tools on this site call a language model: “Ask Vyacheslav” (the AI twin), the “Board of Directors”, and the concierge navigator. The content of your question goes to my LLM gateway and on to an external language-model provider that composes the answer; the processing may happen outside Russia. Without that transfer the tools physically do not work. I say it plainly here, because the “I never share your data with third parties” line below would be inaccurate without this carve-out.

I do not name the provider on this page: I change the line-up of external models by quality and availability, and a name written into the text would go stale before you read it. Who processes the requests today — I will name on request: write to the address at the bottom of the page.

The deterministic tools — the intake gate, F/ONE Verdict, the scanner, and the glossary — never call a model at all: they compute in your browser, and the text of your document never leaves the tab.

  • What goes to the model: the text of your question plus the tool's own context. No name, no email, and no IP address is attached to it.
  • What I keep: the question and the answer as they were, so that I can see how the tools actually perform and fill the gaps where the model fell short. I am the only reader, and every time a text is opened it is recorded in the admin activity log.
  • How long: 90 days, after which the record is deleted in full, automatically.
  • Do Not Track and Global Privacy Control: with either signal on, no question or answer text is stored at all — only anonymous metadata remains (which tool, how long the answer took, whether it failed).
  • Your right not to have text stored works today: turn on Do Not Track or Global Privacy Control in your browser and storing switches off. That is the toggle — the browser signal is honored on the server, not ignored.
  • Deletion: email me at the address below with the approximate date and the wording of your question — I will find the record and delete it. For anonymous use that is the only way to link you to a record, and it does work.

Functional cookies and local storage

There are no advertising or tracking cookies here. There are 12 functional markers, and I name every one of them; below they are grouped by purpose.

  • Reading settings — things you switched yourself; they appear the moment you switch them, not before: fone-theme (cookie, 1 year) — your chosen theme, light or dark; shared between fedoseev.one and en.fedoseev.one so switching language does not reset it; theme (local storage, until you clear site data) — the same theme as the theme library stores it: the twin of the cookie above, without which the wrong theme would flash on load; fone-jargon-level (local storage, until you clear site data) — the explanation level in glossary tooltips: plain, business, or technical.
  • Reading progress — builds up while you read; without signing in it never leaves your browser: fone-reader-progress (local storage, until you clear site data) — how far through each chapter you have read, so the progress bar and the table of contents remember where you stopped; fone-reader-progress-v (local storage, until you clear site data) — a marker that the progress above has already been migrated to the current format; its only job is to keep the migration from running twice; fone-nudge-state (local storage, until you clear site data) — when you dismissed the offer to follow the next chapters, so it stays away for 30 days.
  • Tools — they appear when you run a tool, not when you read the site: scanner-app (local storage, until you finish the run or clear site data) — your draft run of the Scanner: answers and current step, so an accidental page reload does not wipe the work; fone-search-recent (local storage, until you clear site data) — a handful of your most recent search queries, offered back on the empty search page; they never leave your browser; fone-one-prompt-mode (tab storage, until you close the tab) — which mode you left the site's command bar in: navigate or ask; fone-one-prompt-handoff (tab storage, until the question reaches the tool page — seconds) — the text of your question while the command bar hands it over to the tool page; the record is deleted the moment it is picked up; fone-quota (cookie, 90 days) — a random number used to count tool runs per day, tied to nothing about you.
  • Sign-in — appears after you follow the link from your email: better-auth.session_token (cookie, 1 year, or until you sign out) — your sign-in session; without it the gated chapters cannot open.
  • Left over from the past — the site no longer sets this one, but long-time readers may still have it in their browser: fone-hint-dismissed (cookie, 1 year from the last visit before July 2026) — a dismissed coach-mark about the theme switch; it was removed in July 2026 and the site no longer writes this marker, so it expires on its own.
  • More on fone-quota: the number reveals no name, no email, and nothing about you, and it has nothing to do with visit analytics. It appears not when you read the site but when you first use an AI tool. I do not collect a browser fingerprint in any form.
  • More on the session cookie: over https your browser shows it with a __Secure- prefix, page scripts cannot read it, and in production it is shared between fedoseev.one and en.fedoseev.one so signing in once covers both languages. Signing out deletes it on the server and in the browser alike.
  • Visit analytics still runs with no cookies and no identifiers — these markers are not part of it and never reach the counters.
  • I do not type this list by hand: it is assembled from an internal registry, and a marker added in code without a registry entry fails a mandatory check before release. So the list above is as complete as that check keeps it — not as complete as my memory.

The private admin area's activity log

Actions taken in this site's private admin area are recorded in an internal log together with the administrator's IP address and browser. That is the site owner's own data about himself: I am the only person with admin access, and the log exists so I can tell my own sign-in from someone else's. Entries keep the IP and browser for no longer than 180 days, after which those two fields are cleared.

None of this applies to site visitors: visit analytics still carries no personal data, no IP addresses, and no cookies.

How long I keep it

Contact details: for as long as it is relevant to our conversation, or until you ask me to delete them. Everything else has a concrete term:

  • AI tool questions and answers — 90 days, then the record is deleted automatically.
  • The admin activity log — IP and browser are cleared after 180 days; the history of actions itself remains.
  • Anonymous visit and event counters — up to 400 days, so that year-on-year comparison stays possible.
  • AI tool run counters — up to 35 days; this is an aggregate of the form “N runs”, not a history of what you did.

How to delete your data

Email me one line — "delete my data" — and I will remove it from every source and confirm. No account or dashboard required.

If you used an AI tool anonymously and want that particular question gone, give me the approximate date and the wording of the question — that is enough for me to find the record. No account needed.

What I never do

I never sell your data and never share it with third parties — with the single carve-out named above: the content of a question to an AI tool goes to my LLM gateway and on to an external language-model provider, otherwise there would be no answer. No CRMs, no ad networks, no email marketing services are involved.

I don't set advertising or tracking cookies. I don't collect a browser fingerprint. I don't add you to mailing lists without your explicit consent.

Questions and deletion

For any question about data processing, or to delete your data, write to me directly:

[email protected]