Acceptable Use Policy

Effective date: January 1, 2026. This revision applies to a user after it is made available and, where required, accepted. This policy sets conditions for using Akmelo. A breach of a contractual restriction does not by itself establish an administrative or criminal offence.

1. Lawful tasks

Use the Service only when you have a sufficient legal basis for obtaining, processing, and further using data. Before running a task, check your rights to the source, materials, and databases, as well as the applicable access terms and restrictions concerning contracts, confidentiality, and information about people. A public page and the absence of a sign-in requirement do not automatically grant permission to copy and distribute its contents.

If you carry out a task for a client, you must be authorized to act on its behalf. On the Provider's justified request, supply a description of the purpose and evidence of the legal basis to the extent needed for review. Do not send unnecessary personal data or secrets.

2. Prohibited activities

You must not use the Service for:

• unauthorized access, exploitation of vulnerabilities, theft of data, or use of another person's account, token, or session without authority;
• circumvention of access restrictions where doing so breaches the law, rights, or contractual obligations you have accepted;
• infringement of copyright, related rights, database maker's rights, trade secrets, or other protected rights;
• collection, transfer, sale, or publication of personal data without the necessary legal basis;
• creation of unlawful dossiers, harassment, discrimination, fraud, spam, or unlawful decisions about people;
• overloading resources, attacks, distribution of malicious code, falsifying activity, or interfering with websites;
• unlawful distribution of materials, concealing the origin of stolen information, or facilitating the violations listed above;
• circumventing a justified restriction on cloud features through other accounts, tasks, or domains;
• breaching applicable sanctions or export restrictions, including by supplying false information about participants in a transaction.

The availability of a technical function, proxy, browser, or automated assistant does not remove these prohibitions. The ban on unauthorized access does not prohibit lawful use of your own account or use authorized by its owner.

3. Additional conditions for cloud execution

Execution on resources supplied by the Provider is cloud execution. In this mode, collecting, analysing, storing, or transferring pornographic materials, including materials involving adults, is also prohibited. This contractual restriction is broader than prohibitions imposed directly by law. Lawful medical, educational, and other materials are not considered pornographic merely because they discuss anatomy or sexual health. If the nature of the materials is unclear, the task may be referred for clarification of its purpose and content; uncertainty alone does not confirm a violation.

Cloud tasks must not seek to obtain other people's passwords, tokens, payment secrets, private information, or other protected data without authority. Processing special categories of personal data, biometric data, or children's data requires a separate prior agreement on the legal basis, scope, and necessary conditions. Public availability of information about a person does not itself provide that basis.

Do not include personal data or secrets in messages to the automated assistant, examples, or attachments. For necessary lawful access, use the designated settings rather than plain text in code. General terms do not replace specific processing instructions or legally required consent.

4. Reviewing a cloud task

Before a cloud run, the Provider checks the code, source settings, and necessary parameters for signs of prohibited activity. Automated tools, including intelligent analysis, may be used. Analysis results and information about the reviewed code revision are retained for repeat checks. Changes to code, material parameters, or review rules may require a new check.

If signs of a violation are detected, the particular run is put on hold. The user receives a notice explaining the reason and how to contact the Provider. An automated signal does not establish a violation, replace assessment of the circumstances, or count as a confirmed violation on its own. Unavailability of a review tool is not a user violation either.

Advance security review of code and intelligent risk assessment are paid for by the Provider. The user is not charged for that review, and it does not consume the user's automated assistant quotas or traffic allowances. If signs of a violation are detected during cloud execution, task work actually performed before the stop is accounted for under the ordinary billing terms. Disputed usage and refunds are handled under the payment terms and applicable law.

A review result is not a legal opinion, permission from a source owner, or a guarantee that a task is lawful or safe. The user remains responsible for checking the legal basis. The Provider may request necessary explanations and documents without excessive personal data or secrets.

5. Confirmed violations and restrictions

A violation is counted only after an authorised member of the Provider's staff reviews and confirms a particular case with reasons. Repeated submission of the same disputed task must not in itself cause one case to be counted more than once. A violation overturned on review is excluded from the count.

Three separate confirmed violations during the preceding 365 days result in a restriction on the account's cloud working features. When confirming a case, staff assess the circumstances, evidence, recurrence, and proportionality of the measure. Rights to contractual information, enquiries, appeals, and account security remain available. A restriction does not automatically forfeit a balance or end statutory obligations.

To investigate circumvention, the Provider may compare verified sign-in information, verified native application connections, and links between accounts and a browser. A matching browser, application installation, device, corporate network, or individual technical signal does not establish that the same person uses the accounts. Such signals support further staff review and do not independently justify restricting another user. Sharing a computer or lawfully belonging to the same organisation is not a violation in itself.

Urgent safeguards against a real threat to infrastructure, binding requirements of competent authorities, and consequences of other violations are addressed under applicable law and the Terms of Service independently of the number of cases above.

6. Notices and appeals

Notices of a hold, confirmed violation, or restriction are delivered in the application. Acknowledging receipt does not admit a violation, waive objections, or accept a new agreement revision.

You can submit an appeal and check its status in Account status. Explain what you dispute, the purpose of the task, and the necessary evidence of authority. Do not attach passwords, tokens, complete third-party documents, or other information unnecessary for review. An authorised staff member considers the appeal. The result and reasons are provided within 30 calendar days after receipt, or sooner where the law requires a shorter period.

If a violation is overturned, related restrictions are reassessed in light of any remaining valid grounds. Cloud restrictions alone cannot justify refusing to consider an appeal. If you cannot sign in, contact support@insoweb.ru. Rights infringement complaints are accepted at support@insoweb.ru, and personal data enquiries at support@insoweb.ru. Your right to approach a competent authority or court remains unaffected.

7. Execution on the client's resources

The additional advance cloud code review and content restrictions in section 3 do not apply to tasks executed entirely on the client's own resources. Moving a task to the cloud requires compliance with cloud conditions and review. Using the application to manage local execution does not itself make it subject to the cloud review.

The client independently ensures lawful access and processing on its resources. This mode does not authorise breaches of law, third-party rights, or the security of the Provider's infrastructure. Technical isolation, connection safeguards, and protection of the platform remain in place. Data sent back to the cloud is assessed under the conditions of the relevant cloud feature and applicable law.