BizPlans
Kenya-first insights, practical and grounded.
Published 03/08/2026 - 1 min read
Restrictions may follow identity or location inconsistencies, duplicate accounts, shared credentials, unauthorized tools, copied work, confidentiality breaches, suspicious work patterns or repeated quality failures. A restriction is not proof of a specific violation, so rely on the notice and official support rather than rumours.
Outlier prohibits masking a restricted location with a VPN. Handshake requires the verified person alone to access and submit through the account. Handshake also prohibits external AI tools for project work unless expressly authorized in writing and requires some preparatory records to be retained for 90 days. Project rules on other platforms can differ, so read the instructions for each task.
Stop tasking if instructed. Save the restriction notice, project name, timestamps and relevant account history. Write a short factual appeal: identify the account, state what happened, attach requested evidence and ask which policy or verification step needs resolution. Never fabricate travel records, edit documents or hire an “unbanner.”
Avoid opening another account while the first is under review. If access followed legitimate travel or relocation, provide the facts and follow the platform's location-update procedure. If the issue was a technical failure, document browser errors and outage evidence without exposing client data.
Use one account, your own device where required, your real identity and approved tools only. Read the latest rubric at the start of each batch. Separate personal notes from confidential task content and retain only what the platform allows.
For a compliance log and appeal template, see the AI Training & Data Annotation Work Guide for Kenya.
Next step
If you are ready to turn the idea into an execution plan, browse the downloadable guides or generate a custom plan for your business model.
More insights
Use the full model