Privacy Policy
Last updated: September 22, 2026.
This Privacy Policy governs the collection, use and protection of information about users of the service. The service collects account identifiers, technical information and interaction history. The data is used to operate the service, to communicate with the user and for analytics. Information may be disclosed to third parties only in cases established by law or with the user's consent. Data is stored for as long as necessary and protected to a reasonable extent.
The user bears sole responsibility for the risks associated with transmitting data. The Administration may amend the Policy without notice; continued use of the service constitutes acceptance of the changes.
1. General Provisions
1.1. This Privacy Policy (the “Policy”) governs how the information that the User provides when using the service (the “Service”) is processed and protected.
1.2. By using the Service, the User confirms their acceptance of the terms of this Policy. If the User does not agree with these terms, the User must stop using the Service.
2. Collection of Information
2.1. The Service may collect the following types of data:
- account identifiers (login, ID, nickname, etc.);
- technical information (IP address, browser, device and operating system data);
- history of interactions with the Service.
2.2. The Service does not require the User to provide passport details, documents, photographs or any other personal information beyond the minimum necessary for the Service to work.
2.3. Yandex Metrica is used to analyze visits. The Service stores the first landing page without arbitrary URL parameters, permitted UTM tags, the yclid ad click identifier (if present) and the ClientID visitor identifier. Upon sign-in, this information is linked to the account; later observations of a ClientID do not replace the original acquisition source.
3. Use of Information
3.1. The Service may use the information it receives solely for:
- providing the Service's functionality;
- communicating with the User (including notifications and support);
- analyzing and improving the Service.
3.2. Funnel analytics covers registration, an installer request, opening the job auto-apply section, the first successfully completed non-empty AI response for a new cohort of accounts, and the first confirmed payment of a positive amount. The ClientID, the account identifier, the event name and time, and the payment amount and currency may be sent to Metrica. The text of questions, AI responses, resumes, passwords and one-time tokens are not included in these events. Whether an event appears in a report depends on the availability of the counter and on whether it can be linked to a visit.
4. Disclosure of Information to Third Parties
4.1. The Administration does not disclose the data it receives to third parties, except where:
- this is required by law;
- this is necessary to fulfil obligations to the User (for example, when working with payment systems);
- the User has given their consent.
5. Data Storage and Protection
5.1. Data is stored for the period necessary to achieve the purposes of processing.
5.2. The Administration takes reasonable measures to protect data but does not guarantee the absolute security of information transmitted over the internet.
6. Disclaimer of Liability
6.1. The User understands and agrees that transmitting information over the internet always involves risks.
6.2. The Administration is not liable for the loss, theft or disclosure of data if this occurred through the fault of third parties or of the User.
7. Changes to the Policy
7.1. The Administration may change the terms of this Policy without prior notice.
7.2. Continued use of the Service after changes are made means that the User accepts the revised Policy.