Data and privacy policy
Revision of 2026-09-14 (version 2026-09-14)
The operator and the contact address are not configured yet. While that is so, this document describes how the program works and is not a legal commitment.
Webmarket is a search engine over classified ads: we collect offers from open sources and send the buyer to the seller. We have no warehouse, no cart and no payments, so we have no purchase data either.
This document describes what the program actually does with a visitor's data. It is written from the code rather than from a template: every line below corresponds to a table in the database or a query against it.
Who processes the data
Operator: [not configured: PRIVACY_OPERATOR / PRIVACY_CONTACT].
Data questions: [not configured: PRIVACY_OPERATOR / PRIVACY_CONTACT].
While these two places are empty, treat this document as a technical description rather than a legal commitment: only the service owner can name the legal entity and the contact address.
What we keep
A visitor row is created before any sign-in: age confirmation and favourites are needed by people who never intend to sign in. The identifier is random, issued by the server, and on its own it does not name a person.
| What we keep | Why | How long |
|---|---|---|
| Random browser identifier | telling visitors apart without a sign-in: favourites, history, age confirmation | while the browser is in use; the row is deleted after 400 days without a visit |
| Browser string (User-Agent) and a "looks like a bot" flag | not counting robots as people in our own reports | together with the visitor row |
| Date of age confirmation | showing age-restricted categories | together with the visitor row |
| Telegram: account number, username, display name | one set of favourites and one history across a person's devices | until Telegram is unlinked or the data is deleted |
| One-time sign-in codes | passwordless sign-in through the bot | the code is valid for 10 minutes; the row is removed after the retention period |
| Search history: query, section, category, number of results | showing "you searched for" and learning what the catalogue lacks | 180 days |
| Product card views | seeing what is viewed more often | 180 days |
| Result clicks and hand-offs to sellers (without any phone number) | the main measure of the site: did the buyer reach the seller | 180 days |
| Favourites and saved searches | things the person saved deliberately | until the person removes them or deletes their data |
| Consent records: policy version, purpose, date, surface | answering the question "on what basis is this data here" | as long as the visitor row exists |
| A request to a seller, if you left one: contact and text | delivering to the seller what you wrote to them | deleting your data removes the request from our service; anything already received by the seller stays with the seller |
| Web server log: connection address, browser string, page address | troubleshooting and protection against enumeration | the retention is set by server configuration; the owner has not confirmed it yet |
What we do not keep
Not your Telegram conversations, not the phone number of the person who signed in, not passwords, not payment details: none of this is passed to us and we do not ask for it.
The consent ledger holds neither an IP address nor signed Telegram data: the visitor identifier is enough to answer who consented to what.
We do not buy data about you from anyone and we do not link your identifier to advertising profiles.
Telegram sign-in and consent
Signing in serves exactly one purpose: so that favourites, saved searches and history are the same on all your devices. The catalogue works in full without signing in.
Before signing in we explain that pressing the Telegram sign-in button means consent, show the current policy link, and record the consent immediately before the sign-in request: the version of this text, the purpose "telegram_login", the date and the surface (site or Telegram app). Without a recorded consent the server refuses to link the browser to Telegram.
Consent can be withdrawn: "Unlink Telegram" removes the link and marks the consent as withdrawn. The catalogue, favourites and this browser's history stay where they are.
Age
Age confirmation is your statement about yourself, not a consent to data processing, and we do not pass one off as the other. We cannot truly verify age and do not pretend to; the date of the statement is recorded.
Age confirmation does not unlock goods that may not be advertised: nobody sees those.
What you can do
Download your data — we return visitor-database records held under your identifier as JSON. Server logs, Yandex Metrica and Google Tag Manager data are not included.
Delete your data — in one action with an explicit confirmation: history, views, clicks, favourites, saved searches, sign-in codes, consent records, the Telegram link and the visitor row itself all go. The catalogue and sellers' listings are untouched.
Unlink Telegram — the link is removed, the browser's data stays.
These actions are available from the "My data" section; the technical endpoints require the current identifier of this browser, which must not be shared with anyone else.
Traffic counters
Yandex Metrica and Google Tag Manager run on the pages. They may write cookies and storage data, send network events to providers and use visitor identifiers. We do not treat this data as automatically anonymous; the exact cookies, storage, parameters and retention periods will be described on the Cookies and analytics page after the GTM container and requests are technically reconciled.
What this document does not say yet
We claim here neither compliance with any particular law, nor the physical location of the database, nor its state registration: only the service owner is entitled to make such statements, and until then they will not appear here.
The list of open items is kept in the open, in docs/PRIVACY_DATA_MAP.md in the source code.
Changes
The document has a version. When the text changes, the version changes and consent is asked again: consent to a previous revision is not consent to the new one.