Privacy and cookies
Updated 26 October 2026. This notice covers the website, enquiries and orders.
Controller and contact
Jan Jaroš, Czech business ID 07960883, Lesní Albrechtice 2, 74744 Březová, Czech Republic. Contact: [email protected].
Data and purposes
Contact details, correspondence and supplied materials are used for enquiries and contract performance (GDPR Article 6(1)(b)). Billing and accounting data are retained for legal obligations (c). Necessary contractual evidence and correspondence protect legal rights, while technical logs support security, based on legitimate interests (f). Technical data may include IP address, request time, requested URL and browser information. The public website does not require login. Separate review previews use email and authentication records to restrict access.
Recipients
Cloudflare supplies hosting and security; Access authentication is used only for protected review previews. Domain email uses Seznam.cz Email Profi. GoDaddy is the domain registrar; customer domain-holder details are supplied when registration is agreed. GitHub stores source code; customer personal data must not be placed in public repositories. If you contact us on WhatsApp, WhatsApp Ireland Limited and its group also process communications under their own rules; email is available as an alternative. Necessary information may also be disclosed to accounting or legal advisers and authorised public bodies.
GoPay and Paystack payments and Fakturoid invoicing are planned but not yet connected. This notice will be updated to reflect the actual integrations before launch.
Transfers outside the EEA
Cloudflare and other global suppliers may process data outside the EEA, particularly in the USA. Transfers require GDPR safeguards such as an adequacy decision or standard contractual clauses with necessary supplementary measures. Cloudflare publishes its data processing terms and standard contractual clauses. Contact us for information about applicable safeguards.
Retention
Enquiries without a contract are retained for no more than 12 months after the last substantive communication. Necessary contract records are normally kept during the contract and for 3 years after its documented end, or as necessary for an ongoing dispute. Only the evidence needed for legal obligations is retained under the applicable statutory schedule: accounting documents generally for 5 years after the relevant accounting period, and VAT documents for 10 years after the relevant tax period where those duties apply. These periods do not require us to retain every project brief, working material or contact detail. Technical and access logs are retained only as necessary for security under the relevant service settings, longer only for a specific security incident.
Sources and security
We obtain information from you during enquiries and projects, and technical data through website use. Access is limited to people who need it. We do not require identity document copies or card details for a quotation. Do not include sensitive information in an ordinary enquiry.
Your rights
Subject to legal conditions, you may request access, correction, erasure, restriction and portability, and object to processing based on legitimate interests. Any consent may be withdrawn without affecting earlier lawful processing. We respond without undue delay, normally within one month. You may complain to the Czech Office for Personal Data Protection. Data required for a quotation or contract are necessary to process it; without them we may be unable to provide the service. We do not use automated decisions with legal or similarly significant effects.
Cookies and local storage
We do not use visitor analytics or advertising tracking. Language and currency preferences are stored as kitonyo-language and kitonyo-currency in localStorage until changed or cleared in the browser. Cloudflare may use necessary security cookies and an Access authentication cookie to maintain the verified session (configured duration: 24 hours). Specific technical lifetimes depend on the cookie and security context. These technologies support requested functions and security, rather than advertising analytics. Preferences also work without persistent storage; authentication may require necessary cookies.
Planned GoPay payments
The gateway is not active and this website does not currently send data to GoPay to create payments. Once enabled, the provider will be GoPay Czech, a branch of Worldline NV, Czech business ID 22177469. Payment processing will require the amount, currency, order reference, contact details and, where needed, billing details. Card details will be entered directly with the payment provider; Kitonyo will not request them by email or store them. This description will be checked against the actual integration before activation. GoPay documents.
For orders actually paid through GoPay, necessary evidence of ordering and service delivery will be retained for 10 years from the transaction to demonstrate performance, handle payment disputes and meet the gateway’s contractual requirements (legitimate interests under GDPR Article 6(1)(f)). This specific period overrides the general three-year period above for those records; it does not automatically apply to all correspondence or working materials. Any longer statutory retention duties remain applicable.
PayNecta orders
The basket processes your email, project brief, any additional contact details you supply, order items including any requested domain name, KSh total, acceptance of terms and optional early-start request to handle your order. Records are stored in the Cloudflare backend. You enter your M-Pesa phone number and verification code directly in the secure PayNecta frame at pay.paynecta.co.ke; Kitonyo does not collect these details. We send PayNecta the amount, currency and a random order reference. Our server verifies payment status with PayNecta. The basket is stored locally in your browser and the pending payment session in the current window storage. These records support basket and payment functionality, not advertising.
Retention of PayNecta orders
For definitively closed unpaid or expired orders, unnecessary contact details, project briefs and requested domain names are removed 30 days after recorded confirmation of closure. Before automated cleanup, the operator must approve the order as requiring no further contract performance and having no outstanding debt, dispute or other reason to retain those details. A timeout, browser cancellation, provider error or old pending status is not confirmation that no payment was made.
After this removal, a minimal payment and reconciliation record may remain for up to 1,095 days (approximately three years) after confirmed closure to preserve the payment history and prevent duplicate processing. Its identifiers can still be linked to a person, so this is a reduced, pseudonymous record rather than fully anonymous data. The remaining record is then erased unless a specific legal or dispute-related hold is documented. Automatic erasure requires a fresh, matching confirmation from the payment provider that no payment exists; cases closed through manual reconciliation require operator-reviewed erasure. Any exception must have a recorded reason and be reviewed. The 30-day and 1,095-day periods for failed orders are our retention choices, not universal statutory periods.
Payments whose outcome remains unclear are referred for manual reconciliation after 7 days and reviewed at least monthly until resolved. They are not erased solely because of their age. Paid orders and necessary evidence of contracts, payments, refunds, complaints, accounting and tax obligations are protected from the unsuccessful-order cleanup. Their retention follows the applicable periods above; an ongoing dispute or other documented legal need protects only the evidence needed for that purpose and is reviewed regularly.
These rules are introduced through a controlled rollout. Automated cleanup is enabled only after the necessary safeguards and operator approval are in place; publication of this notice alone does not enable it. The same retention rules apply to exports and separate copies. Earlier data versions may remain available for recovery within the provider's recovery window, currently up to 30 days for Cloudflare D1 depending on the plan. Logical erasure does not immediately wipe that recovery history. Following a restoration, required erasures must be reapplied before the restored data returns to ordinary service.
Checkout bot protection
Cloudflare Turnstile checks browser and network signals before a new checkout can open. Our server validates the one-time result with Cloudflare, including the source hostname and network address, to reduce automated abuse. This check protects checkout and is not used for advertising.