AutoGineer

Content policy and automated review

What may appear in public posts, listings, and attachments — how screening works, and what happens if you are held.

EveryoneUpdated 2026-07-30

Jobs, hire requests, services, and their attachments are visible to other users, so they are screened as they are created. Screening is automatic and immediate; a person is involved when the automatic check is unsure, and a human decision overrides the automatic one in both directions.

Not allowed

  • Contact details or any attempt to move work off-platform — phone numbers, email addresses, external links, messaging handles, or a spelled-out address meant to dodge detection.
  • Advertising, promo codes, or promotion of external brands and channels.
  • Vulgar, sexual, hateful, political, or discriminatory content.
  • Misleading, scam-shaped, or illegal content, including claims that cannot be true.
  • Images unrelated to the work, or images that themselves carry contact details.
  • Credentials, tokens, or another party’s personal data — including inside an attached workflow export.

How screening actually runs

  1. 1

    Submitted

    You create a post, listing, or attachment.

    Automatic policy check
  2. 2

    Cleared

    Low risk. It goes live immediately — this is the overwhelming majority.

  3. 3

    Held for review

    The check is unsure or recommends rejection. It is not public yet, and it is not deleted.

    A person decides
  4. 4

    Approved by a person

    The human decision overrides the automatic one. It goes live.

  5. 5

    Rejected

    It stays hidden. Edit the cause and submit again.

An automated verdict is never the last word. That is the point of the human override — an unappealable machine decision on someone’s livelihood is not acceptable.

If your content is held

The usual cause is contact details or an external link, often in an attachment rather than the text you were looking at. Remove it and resubmit. If you believe the hold is wrong, say so — a person can and does overturn it.

Attachments are checked too

Images are screened visually, and documents and workflow JSON are scanned. Files that fail are rejected at upload, so they never become public. Read your workflow exports before attaching them — they routinely contain credential references and real sample data.

content policymoderationautomated reviewattachmentsappeal

34 articles · Ask a question