Last updated: 21. 6. 2026
1. Data controller
WebSEOHost is operated by ADYWEB s. r. o.
2. Data we process
When you send an enquiry, we process the selected package or service, preferred contact method and supplied email address or telephone number. If you voluntarily add a name, company, existing website or message, those details are also processed. The form also submits language, source page and technical data needed to protect it from abuse.
3. Purposes and legal bases
Enquiry data is used to reply, clarify requirements and prepare a proposal. The legal basis is taking steps at your request before entering into a contract. Technical security checks and repeated-submission limits rely on the legitimate interest in protecting the website and communication channels from abuse.
4. Retention
Enquiries that do not lead to a contract are retained for no more than 12 months after the last communication unless longer retention is needed to establish, exercise or defend legal claims. If a contract is formed, data is retained under applicable legal and accounting obligations. Security data used for rate limiting is short-lived and pseudonymized.
5. Recipients and transfers
Hosting, server infrastructure and email delivery providers may process data to the extent necessary to operate the website and deliver an enquiry. Optional analytics and advertising are not enabled in this release. If a provider outside the European Economic Area is used, the controller must ensure an appropriate transfer mechanism.
6. Your rights
You may request access, correction, erasure, restriction and portability, object to processing based on legitimate interests and lodge a complaint with a supervisory authority. Send requests to info@webseohost.sk. The supervisory authority is the Office for Personal Data Protection of the Slovak Republic.
7. Required information and automated decisions
Without a valid email address or telephone number for the chosen contact method, the enquiry cannot be answered. All other fields are optional. The website does not use automated decision-making with legal or similarly significant effects.
8. Security
The form uses one-time signed tokens, timing checks, a hidden protection field, request limits and server-side validation. Production traffic should use HTTPS, and server and email access should be restricted to authorized people.