Privacy Policy

Version dated 17 October 2026.

This Policy describes data processing in the Modoos service at modoos.pro and in the cloud workspace. Modoos (“we”, the “controller”) is responsible for this processing; contact details are in section 11.

1. Data we process

Account and communications: email address, phone number, language, browser time zone, selected solution and information needed for sign-in, address verification and service messages. The time zone is used to show dates and deadlines in the User's local time. The User gives the phone number themselves when starting with a template; it is used to contact the User about their work with the Service.

Acceptance of terms and consents: which versions of the Terms and of this Policy the User accepted, when, by what action and in which language; when the User gave or withdrew consent to news and offers, with which version of the consent text, in which language and where. These records are needed to show on what terms the contract was made and what the User agreed to.

Where the User came from: which version of the website the User came from to registration, a random visit number and records of the steps of the User's journey and of the state of the workspace and credits. These records are needed to understand where people come from and at which step they stop.

Service and payments: plan, workspace periods, ways of accessing the assistant, orders, payment status, free and purchased AI credits, and the volume and price of supplied requests. Payment credentials are processed by the payment provider and do not reach the controller.

Materials and requests: workspace files and text, tasks given to the assistant, answers and results, selected model, request usage and information needed for history and continued work.

Technical data: network address, time, device and browser type, and service logs of requests, faults and abuse prevention measures.

Website visits: the modoos.pro pages run the Google Analytics (Google) and Yandex Metrica (Yandex) visitor counters. They receive the network address, the page address and where the visitor came from, and information about the device and browser; Yandex Metrica also records actions on the page: scrolling, pointer movement and clicks. This information is needed to understand how many people visit the website, where they come from and how they use it. These counters are not present in the account area or the workspace.

2. Purposes and legal bases

Account, service, payment, material and request data are processed to enter into and perform the contract: open and maintain the workspace, perform a task, preserve history, handle billing (record payments and usage), return data to the User's device and provide support.

Data are also processed to comply with law and protect the Service and other users where the controller has a corresponding legal obligation or legitimate interest. Voluntarily providing data does not by itself amount to consent for every purpose.

Records of accepted terms and consents are processed to enter into and perform the contract and to demonstrate consent where law requires it. Records of where the User came from and website counter data are processed in the controller's legitimate interest in understanding where people come from and how to make the Service easier to use.

News and offers are sent only with separate optional consent. Refusal does not prevent use of the Service; consent can be withdrawn in the account area by clearing the checkbox, or through the contact in section 11. Service messages about the contract, security, payments and workspace operation are not marketing.

3. Materials and artificial intelligence

Materials remain the User's materials. The controller does not use them to train artificial intelligence models.

When the User gives a task, the content needed from the task, selected files and history is shared with an engaged model provider to perform that request. When the User works through their own subscription, data are sent to the third-party service they selected under its rules. When the User works with AI credits, the controller engages the provider and remains responsible to the User for the Modoos service.

A technical specialist may receive limited access where a fault or the User's support request cannot otherwise be handled. Access is limited to its purpose and necessary scope.

4. Connected services

Connecting an external service is optional and starts with the User's action in that service's window. For GitHub, account information, the repository list used for selection and the contents of selected repositories are processed. If Google Drive connection becomes available, only files and folders selected by the User through Google's picker are processed.

The data are used to bring selected materials into the workspace and return changes at the User's request. Access can be withdrawn in the external service. Files already brought into the workspace remain there until the User deletes them or the general retention rules apply.

5. Recipients

The controller does not sell data. As needed, data are received by engaged infrastructure hosting, artificial intelligence model, payment, email and other service-message providers, website visitor counter providers, and by external services connected by the User. Data are disclosed to public authorities where law requires it.

Account, terms acceptance, payment, material and request data, records of where the User came from and technical data are stored on servers rented from Hetzner in data centres in Germany and Finland; connections to the website, the account area and workspaces pass through an entry server that forwards encrypted traffic without decrypting it. The content of tasks, selected files and history needed for a request is passed through OpenRouter to the provider of the model the User selected. Website visit information goes to Google (Google Analytics) and Yandex (Yandex Metrica). The email address, amount, currency and order number of a payment in US dollars or euros, and the payment credentials the User enters on the payment page, go to the lava.top payment platform (operated by LAVALANE LTD, Cyprus); payments in roubles go to the acquiring bank. Service emails are sent through Yandex Cloud Postbox. Service notifications to the team, which include the User's email address and information about their payments and workspace, go through Telegram. Data the User passes to external services and to their own subscription go to those services. These recipients may process data in other countries under their own terms. This Policy does not promise an unchanging list of providers or storage countries.

6. Retention

Data are kept while needed for the stated purposes, contract performance, legal duties, dispute resolution and protection of rights. Workspace materials (files and conversations) are kept while the workspace operates and for 30 days after the trial or a paid period ends: during those days they can be obtained and work can be resumed (section 2 of the Terms). After that, trial workspace materials are deleted. Materials of a workspace whose paid period has ended are kept without User access after those 30 days and are deleted no later than 90 days after the end of the paid period. Particular records are kept longer where law requires it.

7. Security

The controller applies reasonable technical and organisational measures appropriate to the nature of the data and risk. No measure gives an unconditional security guarantee.

8. Cookies

The website and the account area use cookies needed for operation, sign-in, security and remembering the selected language and the solution chosen on the website. The website also remembers the selected price currency in the modoos_cur cookie so that the website shows prices in it. In addition, the account area keeps two arrival markers for one day: __Host-modoos-from (which version of the website the person came from) and __Host-modoos-visit (a random visit number that says nothing about the person); on registration their values are transferred to the account (section 1). The Google Analytics and Yandex Metrica counters set their own cookies on the website to count visits (section 1). The User can delete them in browser settings, but some functions will require a new sign-in.

9. User rights

The User may request information about processing, access, correction or deletion, restriction or cessation of processing, data portability and objection where applicable law provides those rights. Consent can be withdrawn without affecting processing carried out lawfully before withdrawal. Requests go to the address in section 11; the controller may request information needed to verify identity.

The User may complain to the competent data protection authority. The applicable mandatory law determines the available rights and response periods.

10. Changes

A new version is published on this page with its date. If a change materially affects the User's rights, the controller gives notice through an available contact method where applicable law requires it.

11. Contact

Questions about data, deletion requests and complaints go to support@modoos.pro. The conditions of the service are set out in the Terms of Service.