If you process a private request, you must make a deposit of 100,000 rubles to your security deposit in your profile. More details here – https://zelenka.guru/threads/5329699/ 1. In the topic, you must specify which requests you will process. Example – Steam / Blizzard / PayPal / Twitch / Private request (if the request is private, you must specify it under a hide for KF). Why should I specify my private request? By providing a link to your private request, you are not disclosing the processing methodology. This is required so that if someone files an arbitration against you, the person reviewing the case can verify why there was no private request in the client's **** and view the actual service you are processing, without the possibility of misleading the arbitrators. 2. If you provide your services for free, the topic must specify which requests you assign to yourself. 3. In the topic, you must specify the method you use to check (software or manual) and whether you use proxies for this. 4. It is forbidden to take **** "into a queue" (i.e., start processing them later). Only take material if you are ready to begin working immediately. Exception – if the person who gave you the **** agreed to the specified timeframe. (The client has the right to file a complaint against the topic creator if they have proof of violation of this rule.) 5. The client has the right to request lowering or increasing the selling price of the account. 6. The processor is обязed to provide full reporting, including video recording* of the processing of the client’s ****. (Exception: if the client explicitly states that reporting is not required, it may be omitted.) 6.1. For the Facebook, Tinder, and LinkedIn categories, the processor must record video of their work. The recording must begin before receiving the material from the client and continue until the work is fully completed. The processor must store this video for at least five days. 6.2. If the number of suitable **** for the processor’s request exceeds 100, the reporting percentage for such **** may be reduced to 25% (example: if there are 100 ****, you must provide reporting for at least 25 ****). Does not apply to p.6.1. 6.3. The processor must notify the client that reporting will not be provided for all **** if their number exceeds the limit – see rule 7. 7. It is prohibited to create topics for processing material that will be transferred to third parties. The client has the right to file a complaint against the topic creator if they have proof of violation of this rule. 8. If you work as part of a team, you must specify the profiles of all participants who will be involved in processing the material. This is necessary to ensure transparency and trust between the contractor and the client. 8.1. If the material will be processed not personally by you, you must obtain the client’s consent in advance, specifying exactly who will perform the work. The client must know beforehand who will handle the material and decide whether to proceed under these conditions. 9. If a user has more than one request, they must place them in a single topic. If it is necessary to create additional topics, up to three topics are allowed, provided that the additional privilege “Topic Pin” is purchased for each of them. 10. Topics created for purchasing material at a fixed price must be placed in the Trading section (**** / Databases, requests from emails). * — mandatory categories are listed in p.6.1; for other categories, video recording is at the processor’s discretion. In case of fraud detection on the part of the processor (for example: processing requests not specified in the topic, selling **** to third parties, falsifying reports to mislead the client), the processor will receive a “scam” badge for 3 months.