Trust & Safety Policy

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.
• Optional verification badges for Hosts — live, opt-in. A Host may upload a document to support a verification badge on their Listings: business registration, identity, public liability insurance, or fire-safety compliance. A CoHub admin reviews the document and, if it supports the claim, applies the matching badge. This is voluntary. A Host who doesn’t take it up can still list, and is still bound by the compliance declaration in Section 9.
• What a badge means. A CoHub admin has sighted a document the Host provided that appears, on its face, to support that claim, on the date shown. CoHub does not contact an insurer, a regulator, or any issuing body to confirm the document is genuine or current, does not inspect the Space, and does not guarantee that cover or compliance is in place at the time of any particular Booking. A badge is a risk-control step, not an endorsement, accreditation or certification.
• Badges expire after 12 months. A badge is removed automatically 12 months after it is granted. A Host who wants to keep a badge must submit a current document again. The absence of a badge does not mean a Host is unverified or non-compliant — only that they have not used this optional step, or that their badge has lapsed and not yet been renewed.
• CoHub does not keep the document. It is deleted once the admin has made a decision. CoHub retains only the outcome, the category, and the dates the badge was granted and expires.
• Optional ID verification for Members — not currently available. The same credential-review mechanism could extend to Members who only book Space. This is not currently available to Members, and CoHub makes no guarantee about timing or implementation.

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).

Externally organised MeetGreet events. A MeetGreet host may mark their event as “externally organised” where it is actually a conference, webinar, or other event run by a different business or organisation, and CoHub is only listing and promoting it. These conduct guidelines, and the Safety Rules in Section 2, apply to how that event is listed and described on the Platform in exactly the same way they apply to any other MeetGreet event or CoHub Live session — but CoHub has no visibility into, and no ability to moderate, what actually happens on the external organiser’s own website, registration process, or at the event itself. A concern about the event’s own content or conduct (as opposed to how it’s listed on CoHub) should be raised directly with that organiser; Incident Reporting (Section 4) covers concerns about the CoHub listing itself.

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. Until a dedicated Gigs reporting tool is released, a Poster or Worker with an issue must submit it through the general Contact form instead.
• Report a Feed post — live. Any post on the Community Feed has a “Report” option, letting a User flag it for spam, inappropriate content, harassment, a scam, or another reason, with optional details. This is a separate mechanism from the Booking-specific “Report a problem” link above — it goes straight to CoHub’s admin team, who can dismiss the report or remove the post.
• Response target. CoHub endeavours to respond promptly to a safety report, typically within 24 hours. This is an indicative timeframe only, not a guaranteed service level — 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.
• Asking CoHub to review a decision. A User whose account, Listing, Task or content has been suspended, removed or rejected may ask CoHub to review that decision through the Contact form, and should include anything they want considered. CoHub will look at the decision again and confirm the outcome in writing. A Worker on CoHub Gigs has a further process set out in the Terms of Service, Section 16.

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. Until those structured fields are introduced, a Host must clearly include this information — accessibility notes, house rules, and an on-site emergency contact — within the Listing description.

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: Status: these badges are live and opt-in for Hosts, and a Verified badge is also available to Gigs Workers who have a credential reviewed (Section 1). A badge appears on a Host’s Listings only where that Host has completed the optional check for that category, and is removed automatically 12 months after it is granted unless renewed. Section 1 sets out what CoHub does and does not check before granting one. CoHub will not describe a badge, in marketing or in Listing content, as meaning more than Section 1 says it means.

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 does not currently restrict a higher-risk Task — particularly in Construction & Trades — from hiring an unverified Worker. A Worker’s credential verification (Section 1) is optional today and is not enforced as a gate before any Task, including a higher-risk one, can be applied to or hired for. Posters are responsible for verifying an applicant’s licences, permits, and safety credentials themselves before accepting them, particularly for higher-risk work.

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 at or above CoHub’s minimum for that Space category, set out in the table below.
• 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.

Minimum public liability insurance by Space category

These figures are CoHub’s current platform minimums, set by CoHub as a starting point for a genuinely early marketplace — they are not the product of an actuarial or insurance-broker review, and a Host should confirm the right level of cover for their own circumstances with their own insurer or broker. CoHub may revise a category’s minimum, or require a higher limit or additional cover for a specific Listing, at its discretion; any change will be communicated directly to affected Hosts and reflected in this table.

This declaration step is live today for every new Listing, and applies whether or not a Host holds any verification badge. The declaration itself is not independently verified: CoHub does not check the underlying policy or compliance position of a Host who has only declared it. A Host may separately choose the optional document review described in Section 1, which is limited to what that section describes and expires after 12 months. Hosts remain solely responsible for ensuring their Space meets all legal and safety requirements. 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.
• CoHub does not inspect, audit, or certify any Space or Task, and makes no representation regarding its safety, legality, or suitability.
• 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.
• For a MeetGreet event marked “externally organised”, CoHub is not the organiser, does not vet or endorse the organiser or the event’s content, and is not responsible for the event’s conduct, safety, or cancellation, or for the organiser’s own website, registration process, or ticketing (see the Terms of Service, Section 9, for the full clause this restates).

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