Community Guidelines

These guidelines explain what a good listing, interest note, message and review looks like on TakeoverWork. They apply to everyone and form part of our Terms of Use. Listings or messages that break them may be edited for formatting, paused for review or removed.

Listings

The work must have already started

Every listing is a takeover. There must be something to take over: code in a repository, a no-code app, a WordPress or Shopify site, a mobile build, or an automation that partly runs. You will be asked to confirm "This project has already started" before you publish.

"Build me an app from scratch" is not a takeover, however detailed the idea. We will decline those listings politely. If you only have an idea or a design, a general freelance site is a better fit for now.

Describe what exists, honestly

• Explain what works today, what is broken or blocked, and what still needs to be done. Specific beats general: "Stripe checkout works in test mode but webhooks never reach the server" is more useful than "payments are broken".
• List what the project is built with, such as the AI builder, framework, database and hosting.
• The completion estimate is shown as your approximate estimate. If you are not sure, choose "Not sure". Developers will form their own view.
• Say what you can hand over: repository access, domain, hosting, database, app store accounts, payment provider, third-party APIs.

Describe, don't blame

Explain the situation, not the person. "The previous developer is no longer available" or "the agency closed" is enough. Never name, criticise or accuse a previous developer, agency or employee in a listing, and do not post private conversations with them. If you have a legal dispute, deal with it outside TakeoverWork.

No contact details in listing text

Do not put phone numbers, email addresses, messaging handles or links such as wa.me or t.me in your listing. They are hidden automatically. Developers contact you through the platform, and contact details are shared only when both sides approve.

No credentials or secrets, anywhere

Never post passwords, API keys, private keys, database connection strings, tokens or .env contents in a listing, attachment, question, answer or message. Our systems try to detect and block them, but you are responsible for not posting them. If a secret was ever exposed, rotate it. When it is time to give access, use collaborator or team invites, as explained on the safety page.

Screenshots and attachments

• Crop or blur anything showing keys, tokens, admin URLs with tokens, or other people's names, emails, orders or personal details.
• Do not upload source code archives. Link to a public repository instead, or give access later through a collaborator invite.
• Location data in photos is removed automatically, but check screenshots for other personal information.

One project, one listing

Do not post the same project more than once or in several categories to get more attention. Edit or renew your existing listing instead.

Interest notes

Interest notes are how developers introduce themselves. They are structured on purpose.

• Be honest. Describe how you would start, what relevant work you have done, when you are available and a realistic effort band. If you need to look at the code before you can judge effort, choose "Need to review code first".
• No prices, quotes or bidding. Interest notes do not include a price. Discuss pricing in messages once both sides are interested.
• Write for this listing. Generic copy-and-paste notes that ignore the project will be treated as spam.
• Only claim what is true. Do not exaggerate experience, team size or past results, and do not present other people's work as your own.

Messages

• Be respectful and professional, even when you disagree or decide not to continue.
• Keep conversations on the platform until both sides approve sharing contact details. Do not pressure anyone to move to another app early.
• Never ask for, or send, passwords, one-time codes or keys.
• No harassment, threats, discrimination, sexual content or spam.
• If someone is not interested, accept it. Do not keep messaging after a clear no.
• Use Block if you no longer want to hear from someone, and Report if they break these guidelines.

Questions and answers

Public questions on a listing should be about the project. Answers are public, so customers should not include contact details, secrets or anything they would not want every visitor to see.

Reviews

Reviews on TakeoverWork are interaction reviews. They reflect one customer's experience of working or talking with a developer; we do not supervise projects or check the work. A customer can leave a review only after a connection has reached "selected", "continued" or "completed".

• Describe your own experience, factually.
• Do not offer or accept payment, discounts or favours for a review, and do not review yourself or a business you are connected to.
• Do not include personal data, contact details or private messages.
• The developer can post one public reply. Reviews that break these rules can be reported.

Reporting

Use the Report button on any listing, profile, message, question or review. Choose the closest reason, such as spam, scam, wrong category, work not started, prohibited, misleading, harassment or a request for credentials, and add details. We aim to acknowledge reports within 24 hours and resolve them within 15 days. For complaints under Indian law, see the Grievance Officer page.

Some projects are never allowed. See Prohibited Items.