Personal data processing policy

1. Controller and legal bases

Controller: Самозанятый (плательщик налога на профессиональный доход) Зубович Евгений Михайлович, tax ID 381112632312. Personal data contact: e.zubovich@yandex.ru.

Processing follows Russian law, including Federal Law No. 152-FZ on Personal Data. Data necessary for registration, order fulfilment and claims are processed to enter into and perform a contract at the user’s initiative and meet applicable controller duties. Where consent is the legal basis, it is requested separately and is not concealed in the offer.

The controller does not use uploaded photos to identify people, collect special-category data or make decisions with legal effects solely through automated processing. Do not upload documents, faces, vehicle plates or other third-party data; remove or obscure them before submission.

2. Categories, purposes and retention

Data subjects are visitors, registered users, customers and support enquirers. Sources are information users supply and technical interaction data. Processing is limited to the specific purposes below; combining data for incompatible purposes or collecting excessive information is not permitted.

Legal bases: account creation, orders and payment servicing rely on entering into and performing a user-initiated contract (article 6(1)(5), No. 152-FZ); mandatory records and statutory requests rely on controller duties; external AI processing and optional visitor statistics rely on separate consent where applicable (articles 6 and 9). Reading the policy is not consent to every type of processing.

Accounts and access: email, user ID, role, balance and protected authentication/session data. Users log in with a single-use emailed code valid for 10 minutes; plaintext codes and passwords are not stored in the user database. Sessions last up to 7 days. Email supports accounts, services, login codes, results, support replies and receipts. Users separately consent to email processing; the text and confirmation date are saved. Advertising emails are excluded. Contract fulfilment and mandatory records may have an independent legal basis. Account data remain until account deletion or the relationship ends, then only where legally justified.

Generation and history: garden photos, layout and dimensions, preferences and style, results, times, task identifiers and status. Purposes are three options from a photo or one layout in three styles from the planner, delivery of descriptions and reports, account storage and handling enquiries. A recognised uploaded plan or aerial image may give one design from three angles. Garden design does not include a work plan or estimate; interior design includes an action plan and an indicative materials and furnishings budget. Generation materials and results are stored for one year or deleted earlier following a lawful user request. Unpaid preliminary AI-analysis photos are kept for the configured period, 30 days by default. Material retention does not override mandatory payment-record retention periods.

Payment and records: tariff, amount, credits, order/payment IDs and statuses, credit/debit records and accepted terms version; receipt email is sent to the payment provider. Purposes are settlement, service provision, refunds and legal requirements. Records are retained as required by applicable tax, accounting and other laws; unrelated information is not retained merely because payment documents exist.

Enquiries: contact details and information voluntarily provided for support, refunds or rights requests. Purposes are handling the enquiry and proving fulfilment of obligations. Once resolved, only legally justified information remains for the necessary period.

Security: login hash and failed-login counts/times; infrastructure logs may contain IP addresses, times, request URLs and browser information. They serve protection and troubleshooting, not advertising profiles. Failed attempts are blocked for 10 minutes; successful login clears the relevant counter. Retention is limited to security review and incident resolution, followed by deletion unless another legal basis exists.

3. Methods, recipients and processing location

Processing is mainly automated: collection, recording, organisation, accumulation, storage, correction, retrieval, use, disclosure to specified recipients, blocking, deletion and destruction. Authorised staff may handle support and enquiries. Data sales, public publication of materials and advertising mail are not service purposes.

Server account data and results are hosted by Amvera LLC under a personal-data processing instruction. For the selected Moscow_0 region, the primary data centre is at Россия, Московская область, г. Мытищи, ул. Силикатная, д. 19. Amvera performs storage, transfer, backup, recovery and deletion; backups may use other Russian data centres listed by Мытищи, ул. Силикатная, д. 19. Amvera. Primary recording, organisation, accumulation, storage, correction and retrieval of Russian citizens’ personal data use databases within Russia.

Login codes, results and support replies use nic.ru (RU-CENTER) email hosting. The recipient email and service message are transmitted, with a PDF report when sending results. This fulfils user requests and services accounts or orders; advertising mail is excluded.

Only user-selected task materials — the garden image or plan and wishes with parameters — are sent to AITunnel (aitunnel.ru). Emails, passwords, balances, payment details and other account data are excluded. The service is not intended for personal data in task materials: users must remove or obscure faces, address plates, vehicle plates, documents and other identifiers before upload. If personal data are nevertheless submitted, the material is technically processed within the request until detected or deleted; this policy and the separate AI-processing consent apply.

Оператор не осуществляет трансграничную передачу персональных данных.

Robokassa receives the order number, amount, service description and receipt email to process payments, payment documents and refunds. The site does not receive CVV/CVC, bank passwords or verification codes. Disclosure to public authorities requires a legal basis.

4. Cookies and local data

The technical dacha_session cookie enables account access; JavaScript cannot read it and its lifetime is limited to the session. Browser IndexedDB stores plans and recent reports, and sessionStorage stores a wishes draft, supporting selected features. Browser tools can delete these local copies without deleting the server account.

Web analytics purpose: collecting and analysing site visits to improve user experience and site quality using analytics systems. The legal basis is separate voluntary visitor consent (article 6(1)(1) and article 9, No. 152-FZ). Yandex Metrica starts only after consent; refusal does not prevent site use.

Data subjects are site visitors. Analytics data include IP address, cookie IDs, browser/device details, visit time and public-page address. Processing is automated over the internet, not via a legal entity’s internal network. Actions include collection, recording, organisation, accumulation, storage, use, transfer (disclosure/access), deletion and destruction. The recipient is YANDEX LLC, Yandex Metrica; applicable service terms and the processing instruction under article 6(3), No. 152-FZ govern processing.

Session replay, form recording, click maps, link tracking and ecommerce are disabled in the integration. Analytics events exclude logins, emails, photos, wishes, balances and result contents. Page addresses omit query strings and fragments. This purpose excludes advertising mail, publication of user materials and AI design generation.

Processing for this purpose stops when achieved or consent is withdrawn. The browser choice lasts at most 180 days, then must be renewed; this is a choice-retention period, not permission for indefinite data storage. Deletion and destruction follow article 21, No. 152-FZ unless an independent legal basis permits continued processing. Withdrawal is available under “Documents and provider details” and by email to the controller. It stops future statistics without invalidating earlier lawful processing. Service information: https://yandex.ru/legal/metrica_termsofuse/ and https://yandex.ru/legal/confidential/.

5. Rights and ending processing

Enquiries: e.zubovich@yandex.ru. Support requests are processed within 7 days.

Users may obtain processing information, request correction, blocking or destruction where provided by law, withdraw consent, request processing to stop and complain to Roskomnadzor or a court. Login and request details may identify the data; the controller requests only necessary proof of ownership, not the account password.

Access requests are answered within article 20 deadlines of No. 152-FZ, normally 10 working days; extensions require the statutory procedure and reasoned notice. Requests to stop processing follow article 21 deadlines and exceptions. Withdrawal does not end processing required on another independent legal basis.

When purposes are achieved or consent withdrawn, processing stops and data are destroyed within statutory time limits, generally 30 days absent another retention basis. If immediate destruction is impossible, blocking and the statutory procedure apply. Backups must also be excluded from ordinary use and destroyed within applicable periods. Mandatory records remain only on their respective legal basis.

6. Protection and policy changes

Safeguards include access separation, result ownership checks, password and session hashing, server-held keys, private-file restrictions and HTTPS for public deployment. The provider must organise backups, staff access controls, incident response and communication with Roskomnadzor within statutory deadlines.

The current policy is available without login. Significant changes to purposes or processing scope are communicated; fresh consent is requested where required. Updating the policy is not automatic user consent to new purposes.

Uploaded photo checks

Все загружаемые фотографии направляются на автоматическую проверку наличия признаков персональных данных до передачи изображения внешнему ИИ-провайдеру. Проверка выполняется локально на сервере «3D-Дача», без передачи фотографии внешним сервисам для проведения самой проверки. Её цель — выявление лиц людей, автомобильных номеров и явно распознаваемых контактных данных (email и телефонов). Идентификация личности не проводится; распознанные строки контактов и номеров отдельно не сохраняются и не записываются в журналы проверки.

On confirmed detection, the photo is rejected and not sent to AI. Generation is not delivered for that material; another garden photo without these elements is required. The rejected photo is removed from the task and its draft. No final credit deduction occurs and any reservation is returned. Rejection is not service delivery and does not remove rights to recover unused prepayment under the offer and law.

Автоматическая проверка имеет ограничения и не гарантирует выявления всех персональных данных. Обычные надписи и водяные знаки сами по себе не служат основанием для отказа. Сомнительный результат либо техническая недоступность проверки не блокируют продолжение генерации и не означают подтверждения отсутствия персональных данных. Пользователь должен самостоятельно проверить материалы перед загрузкой и не включать в них персональные данные; обязанности оператора по защите фактически полученных данных при этом сохраняются.

Interior design from a photo

For interiors, materials include the room photo, room type, style, change level, wishes and items to keep. They are processed to create and store the room design with the same AI provider and the access, photo-checking, retention and deletion rules described here.