VARVAR Privacy Notice
Public version · Updated: 2026-11-09This document describes VARVAR Site as it is currently configured. It does not state that every legal question has been resolved, and it does not publish the operator's personal details.
This notice covers the public site at varvar.tech and information you send directly to VARVAR. The VARVAR Terminal at app.varvar.tech is a separate product and is not covered by this notice. No public site account, payment details or wallet connection is required. Reading public editorial content and communicating with the operator involve different data flows.
What is processed and why
Optional analytics, if enabled in the future, will require your consent. It is currently disabled. Technical requests are processed to deliver and protect the site. Information sent to legal@varvar.tech is processed to review and answer the request. This notice is information, not blanket consent.
| Purpose | Information | Storage and duration |
|---|---|---|
| Optional analytics | Currently disabled. If enabled later: public route, event type, permitted content identifiers, category and result-count band; visitor key only if repeat-visit measurement is separately enabled | When disabled, no analytics event database or delivery queue is used. The implemented maximums are 30 days for raw events and 24 hours for a temporary delivery queue. |
| Remember privacy choices | Analytics allowed/declined, notice version, choice time and expiry | First-party preference cookie: up to 180 days; optional visitor cookie: up to 90 days and never beyond consent expiry. |
| Operational delivery and security | Technical request and security metadata, potentially including IP addresses in firewall, authentication and service error logs | Routine Caddy and application access logging is disabled. Security logs are rotated; system error journals are retained under host limits. |
| Direct requests | Contact address and the text you send | Only for handling the request, maintaining necessary correspondence and meeting applicable obligations. |
Analytics choices
Optional analytics is off by default. Where enabled, it starts only after permission. Refusal leaves public features available. Use the Cookie settings control on the Cookies page to change or withdraw your choice; withdrawal stops future analytics based on that choice and removes the visitor cookie.
A Global Privacy Control or Do Not Track signal blocks optional analytics. Removing that signal is not itself consent. Consent is specific to this browser and site hostname. Clearing browser storage resets the choice.
Data minimisation
The measurement client does not send full page URLs, query strings, fragments, referrers, search text or free-form notes. Private editor and operator routes are excluded. It does not create advertising IDs or device fingerprints, and the event store does not add IP addresses or full User-Agent strings.
A random visitor cookie can be converted to a keyed hash to link visits. This is a pseudonymous identifier, not a guarantee of anonymity. Raw visitor cookie values are not written to the analytics event store. Infrastructure still receives technical requests necessary to deliver the service and privacy controls.
Public market and wallet data
Market information, wallet addresses and activity may come from public platforms, APIs or blockchains. Some addresses may be associated with identifiable people. Public availability does not remove the need for an appropriate processing basis or consideration of rights. We do not claim to verify the identity or intent behind an address.
Recipients and external platforms
The site runs on a netcup VPS. The server network is registered in Germany. REG.RU provides DNS services. No CDN is configured. Google Analytics, Yandex Metrica and first-party visitor measurement are disabled. Infrastructure providers process technical information needed to deliver and protect the site. We do not sell personal information or use it for behavioural advertising. Disclosures required by law may apply.
Telegram and X process activity under their own policies after you follow an external link. Reading a public channel is different from sending a message to a bot. This notice does not grant blanket permission to send private correspondence to AI services.
Access, correction and deletion
Depending on the applicable law and processing basis, you may request access, correction, deletion, restriction, portability or object to processing, and complain to the relevant supervisory authority. Consent can be withdrawn without changing the lawfulness of earlier processing.
Contact us with enough information to locate the relevant record. We may need proportionate identity verification, but do not send identity documents unsolicited. We do not collect extra identity data merely to identify otherwise unlinked visitors. We will explain applicable exceptions or inability to locate a record. Browser cookies can also be removed through your browser's site-data settings.
Retention and security
Optional analytics is disabled and no visitor analytics table is present. Firewall and authentication logs use host rotation; application error records may remain in the system journal. CMS backups can include editor account and correspondence-related records and are access controlled. Records needed to investigate security incidents or meet obligations may be retained for the relevant period.
Access controls, HTTPS and restricted storage permissions support protection; no system can guarantee absolute security. Requests about data and reported incidents are handled separately from editorial review.
Updates
We will update this notice before introducing materially different processing, recipients or purposes, and seek new consent where required. Accounts, payments and marketing subscriptions are not described as existing features.
Privacy requests and content corrections
For a request, identify the relevant page or message and describe the issue. Do not send passwords, private keys or seed phrases. Contact: legal@varvar.tech.