CoHub

Effective 8 September 2026

Trust & Safety Policy

How CoHub keeps the Platform safe for Hosts, Members, Posters and Workers. CoHub Pty Ltd (ACN 701 652 557, ABN 88 701 652 557) — Market: Australia (national).

This policy operates alongside our Terms of Service, our Host Licence Agreement, our Gigs Agreement, and our Privacy Policy. It restates and consolidates safety-related commitments that already exist across those documents into one place, and adds a small number of new commitments (including the minimum insurance figure in Section 9). Where this policy and another CoHub document overlap, the more specific document (the Host Licence Agreement or Gigs Agreement, as applicable) governs the details of a particular Booking or Task; this policy sets the platform-wide safety standard that sits underneath all of them.

Status: CoHub is a genuinely early marketplace, and some of the mechanisms described below — particularly the visual badges in Section 6 and the automated detection in Section 8 — are being built rather than fully live today. Anywhere that’s the case, this policy says so plainly rather than implying it’s already running. The rules themselves (Sections 2, 3, 7, 9, 10) are binding platform policy from the date this document takes effect, regardless of which supporting tools are live yet.

1. Verification

CoHub verifies Users in layers, appropriate to what they’re doing on the Platform.

  • Email verification — live, required. Every User must verify their email address before booking a Space, listing a Space, posting a Task, or applying to one.
  • Payment identity verification — live, required to get paid. Anyone who wants to receive a payout (a Host or a Worker) completes identity verification through CoHub’s payments provider (Stripe Connect) as part of onboarding, before their first payout.
  • Credential verification for Gigs — live, optional. A Worker may upload a certificate, licence or other credential to their profile for CoHub to review; once approved, this earns a Verified badge shown to Posters reviewing applicants. This is currently opt-in, not a requirement to apply for every Task.
  • Business verification for Hosts — not yet live. A Host currently confirms their compliance obligations by declaration (see Section 9) rather than through an independent business-registration check. Building a genuine business-verification step (for example, an ABN lookup) is on CoHub’s roadmap.
  • Optional ID verification for Members — not yet live. The same credential-review mechanism used for Gigs Workers could extend to Members who simply book Space, but this isn’t offered to Members today.
  • Space verification (insurance and safety compliance) — not yet live. A Host declares their Space meets safety and insurance requirements (Section 9) at listing time; CoHub does not yet independently verify the underlying insurance certificate or safety compliance documents. This is planned alongside the badges in Section 6.

2. Safety Rules

Every User must not, anywhere on the Platform or in connection with a Booking or Task:

  • Harass, threaten, or discriminate against another person on any ground protected by Australian law.
  • Behave in a way that is unsafe — to another person, to a Space, or to the public.
  • Use the Platform, a Space, or a Task for any unlawful activity.
  • Misuse a Space — including using it outside its permitted use, capacity, or house rules.
  • Arrange payment for a Booking or a Task outside the Platform in order to avoid CoHub’s fee.

These rules are not new: they restate obligations already binding under the Terms of Service (Section 10, Acceptable Use), the Host Licence Agreement (Sections 3, 7), and the Gigs Agreement (Section 3). Breach of any of them may result in content removal, a suspension, or account termination under those documents.

3. Conduct Guidelines

For messaging, networking, Gigs, and in-person interactions (including a MeetGreet event or a CoHub Live session), every User must:

  • Be respectful and professional.
  • Not send spam or unsolicited commercial messages.
  • Not solicit another User to work outside the Platform in a way that avoids CoHub’s fee, or for a purpose unrelated to CoHub.
  • Not behave aggressively, or in a way that makes another User feel unsafe.
  • Not send or post inappropriate content — including anything sexually explicit, violent, or otherwise unsuitable for a professional marketplace.

Messaging on CoHub is already structurally limited to reduce cold spam: a User can only message someone they’re connected with, have an active Booking with, or have an active Gigs hire with (see Section 8 for the limits of this today).

4. Incident Reporting

If something goes wrong, a User can report it to CoHub.

  • Report a problem — live for Bookings, not yet for Gigs. Every Booking has a “Report a problem” link (on the guest and host dashboards) that sends a flagged report, with the Booking’s details attached, to CoHub. CoHub Gigs doesn’t have the equivalent link yet — a Poster or Worker with an issue today should use the general Contact form instead.
  • Response target. CoHub aims to respond to a safety report within 24 hours. This is a target CoHub is committing to, not yet a tracked service-level agreement — there’s no ticketing system behind it today; reports land as flagged emails reviewed directly by CoHub.
  • Evidence. A User can attach evidence relevant to a report (for example, by replying with screenshots) through the Contact form. Gigs applications already support a file attachment for proof of work; a dedicated evidence-upload field for incident reports specifically is not yet built.
  • Temporary suspension during investigation. CoHub may suspend an account, Listing, Task, or Booking while it investigates a report, consistent with the platform-protection powers already set out in the Terms of Service (Section 16) and the Host Licence Agreement / Gigs Agreement (Section 12 of each).
  • Clear outcomes. CoHub will tell a reporting User the outcome of their report in plain terms — a warning issued, a suspension, or a removal — once a decision is made. There is no formal outcome-categorisation system yet; today this happens by direct message from CoHub.

5. Emergency & On-Site Safety

For a Space that Members visit in person, a Host must be able to provide:

  • The location of emergency exits.
  • Confirmation of fire-safety compliance (see Section 9).
  • The Space’s maximum capacity.
  • Any accessibility notes relevant to the Space (step-free access, accessible parking or toilets, and similar).
  • House rules that apply to the Space.
  • A contact the Member can reach for an urgent on-site issue during the Booking.

Status: Capacity is already a required field on every Listing. Accessibility notes, structured house rules, and an on-site emergency contact are not yet separate, structured fields on a Listing — today a Host includes this information in the Listing description, and CoHub is working towards making each of these a distinct, always-visible field.

6. Listing Safety Badges

CoHub’s goal is for every Listing to show, at a glance:

  • Insurance Verified
  • Fire Safety Compliant
  • Business Verified
  • Host Identity Verified

Status: None of these badges are live on a Listing today. A Verified badge currently exists only for Gigs Workers who’ve had a credential reviewed (Section 1). Displaying the four Listing badges above depends on the independent verification steps in Sections 1 and 9 actually being built — this section states the goal CoHub is building towards, not a feature live on the site yet, and CoHub will not claim these badges are live in marketing or Listing content until they are.

7. Gig Worker Safety

Every Task on CoHub Gigs must give a Worker:

  • A clear scope of work (see the Gigs Agreement, Schedule 1).
  • Any equipment the Worker is expected to bring, versus equipment the Poster will provide.
  • Any certification, licence, or permit the work requires.
  • The safe-conduct rules in Sections 2 and 3 above.

CoHub’s goal is that a higher-risk Task — particularly in Construction & Trades — should not be able to hire an unverified Worker. Today, a Worker’s credential verification (Section 1) is optional and is not yet enforced as a gate before an unverified Worker can apply to or be hired for any Task, including a higher-risk one. Building that gate is on CoHub’s roadmap; until then, a Poster hiring for higher-risk work should check an applicant’s credentials and Verified status themselves before accepting.

8. Messaging Safety

CoHub’s goal is automated detection, across Platform messaging, of:

  • Harassment
  • Hate speech
  • Scams
  • Spam
  • Attempts to bypass CoHub payments

Status: This automated detection is not built yet — there is no content scanning of message text today. What does exist today is a structural limit on who can message whom at all: a User can only message someone they have an accepted connection with, an active (pending or confirmed) Booking with, or an active (hired) Gigs engagement with. That already meaningfully limits cold spam and unsolicited contact, even without content-level scanning. A User who receives a harassing, scam, or payment-bypass message today should use Incident Reporting (Section 4).

9. Host Compliance Requirements

Before a Listing is submitted for CoHub’s approval, a Host must actively confirm each of the following (not just accept a general Terms of Service):

  • They have the legal right to offer the Space for booking, and doing so will not breach any lease, strata by-law, mortgage, council approval, or zoning restriction that applies to it.
  • The Space complies with applicable building, fire-safety, work health & safety, and public-health requirements for its intended use.
  • They hold, or will hold before their first Booking, public liability insurance of at least $10,000,000, appropriate for the Space category. This is CoHub’s current minimum for every Space category; a higher-risk category (such as Warehouse & Industrial) may require a higher limit or additional cover, per CoHub’s then-current requirements.
  • The information, photos, and pricing in the Listing are accurate and not misleading.
  • The Space will not be used for any unlawful, hazardous, or prohibited activity.

This declaration step is live today for every new Listing. It’s a self-declaration, not an independently verified certificate (see Sections 1 and 6) — CoHub may still request evidence of insurance or compliance at any time, and may suspend a Listing if it isn’t provided (Terms of Service, Section 4).

10. Platform Liability Disclaimers

The following is not new — it restates, in one place, disclaimers already set out in the Terms of Service (Sections 4, 13, 14):

  • CoHub operates a platform. It is not the operator of any listed Space, is not a real estate agent, landlord, or sub-landlord, and never takes possession of any Space.
  • A Host is an independent provider, not CoHub’s employee, agent, or franchisee. A Worker completing a Task is an independent contractor engaged directly by the Poster, not by CoHub (see the Gigs Agreement, Section 2).
  • CoHub does not guarantee any business outcome for a Host, Member, Poster, or Worker — including bookings, hires, income, or the standard or legality of work performed under a Task.
  • CoHub is not liable for the acts or omissions of any Host, Member, Poster, or Worker, except to the extent required by law or expressly stated in the Terms of Service. CoHub’s own liability is governed solely by that document, not by this policy, the Host Licence Agreement, or the Gigs Agreement.

Nothing in this policy excludes, restricts, or modifies any consumer guarantee, right, or remedy under the Australian Consumer Law that cannot lawfully be excluded.

11. General

This policy is governed by the laws of New South Wales, Australia (CoHub Pty Ltd’s state of registration). CoHub may update this policy from time to time, with notice given the same way as for the Terms of Service (Section 19).

  • CoHub Pty Ltd (ACN 701 652 557, ABN 88 701 652 557)
  • Suite 9, 39 Stanley Street, Bankstown NSW 2200, Australia
  • support@cohub.com.au