Cancellation · USPTO

Cancellation 92070826

OtherUSPTO

Cancellation 92070826 at USPTO between Chanel, Inc. and Camsi Int'l Holding Limited, over the mark COVERCOCO, filed Mar 14, 2019. Status in the office record: other.

View COVERCOCOGet this data via the API
Status
Other
Result
Other
Filed
Mar 14, 2019
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Petitioner

Chanel, Inc.

Company trademarks
Respondent

Camsi Int'l Holding Limited

Timeline

How the case has moved

Dates from the USPTO record and the COVERCOCO filing.

  1. COVERCOCO filed

    Application 87867902 filed at the USPTO.

  2. COVERCOCO registered

  3. Cancellation filed

    Chanel, Inc. started cancellation 92070826 at USPTO against COVERCOCO.
Marks

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
COVERCOCOContested87867902USPTO
COCORelied on72237534USPTO
COCORelied on73206836USPTO
COCO CHANELRelied on73535356USPTO
COCORelied on73653479USPTO
COCORelied on73818611USPTO
COCO MADEMOISELLERelied on76054884USPTO
ROUGE COCORelied on77768562USPTO
COCO NOIRRelied on85360730USPTO
COCO CODERelied on86925184USPTO
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_f3c0e67b-4f27-4ddc-9485-77650dcfc6b7
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_f3c0e67b-4f27-4ddc-9485-77650dcfc6b7",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92070826",
  "status": "other",
  "office_code": "US",
  "filed_date": "2019-03-14",
  "parties": [
    {
      "name": "Chanel, Inc.",
      "role": "petitioner"
    },
    {
      "name": "Camsi Int'l Holding Limited",
      "role": "respondent"
    }
  ]
}