Opposition · USPTO

Opposition 91300033

SuspendedUSPTO

Opposition 91300033 at USPTO between Swimwear Anywhere, Inc. and Coco Brands International, LLC, over the mark COCO BRANDS, filed Jun 30, 2025. Status in the office record: suspended.

View COCO BRANDSGet this data via the API
Status
Suspended
Filed
Jun 30, 2025
Marks involved
6
Parties

Who is involved

The parties as named in the office record.

Opponent

Swimwear Anywhere, Inc.

Company trademarks
Respondent

Coco Brands International, LLC

Timeline

How the case has moved

Dates from the USPTO record and the COCO BRANDS filing.

  1. COCO BRANDS filed

    Application 98474631 filed at the USPTO.

  2. Opposition filed

    Swimwear Anywhere, Inc. started opposition 91300033 at USPTO against COCO BRANDS.
  3. Next

    Suspended

    No decision is recorded at USPTO yet.
Marks

Marks involved

1 contested mark, 5 marks the challenger relies on.

MarkRoleApplicationOffice
COCO BRANDSContested98474631USPTO
COCO REEFRelied on75026087USPTO
COCO RAVERelied on77251072USPTO
COCO REEFRelied on77797598USPTO
CONTOURS BY COCO REEFRelied on87016539USPTO
COCO COCO CONTOURSRelied on97878454USPTO
API

Get this data via the API

Every fact on this page comes from the Signa API. Track oppositions and cancellations on any mark with one request.

  • GET/v1/proceedings/{id}

    Parties, dates, outcome and every mark in the case

  • GET/v1/proceedings?trademark_id={trademark_id}

    Every proceeding on a mark

Get API keyView docs
GET /v1/proceedings/{id}
ID=prc_23780328-3e9f-4660-ae1a-4d7fa23c8387
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_23780328-3e9f-4660-ae1a-4d7fa23c8387",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91300033",
  "status": "suspended",
  "office_code": "US",
  "filed_date": "2025-06-30",
  "parties": [
    {
      "name": "Swimwear Anywhere, Inc.",
      "role": "opponent"
    },
    {
      "name": "Coco Brands International, LLC",
      "role": "respondent"
    }
  ]
}