Cancellation · USPTO

Cancellation 92065118

OtherUSPTO

Cancellation 92065118 at USPTO between KIND Management Inc. and Kynd Clothing Inc. dba Kynd, over the mark KYND, filed Jan 9, 2017. Status in the office record: other.

Status
Other
Result
Other
Filed
Jan 9, 2017
Marks involved
16
Parties

Who is involved

The parties as named in the office record.

Petitioner

KIND Management Inc.

Respondent

Kynd Clothing Inc. dba Kynd

Timeline

How the case has moved

Dates from the USPTO record and the KYND filing.

  1. KYND filed

    Application 86976431 filed at the USPTO.
  2. KYND registered

  3. Cancellation filed

    KIND Management Inc. started cancellation 92065118 at USPTO against KYND.
Marks

Marks involved

1 contested mark, 15 marks the challenger relies on.

MarkRoleApplicationOffice
KYNDContested86976431USPTO
KINDRelied on76596770USPTO
KINDRelied on77333800USPTO
KIND FRUIT + NUTRelied on77721453USPTO
KINDTASTICRelied on77816084USPTO
KINDELICIOUSRelied on77816085USPTO
KINDRelied on77827342USPTO
KINDINGSRelied on77903894USPTO
KINDRelied on77981723USPTO
KINDRelied on85579711USPTO
KINDRelied on86676861USPTO
KINDRelied on86676867USPTO

+4 more marks in this case

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 /v1/proceedings/{id}
ID=prc_ee27ad34-25c3-4fc0-80ef-f84bacc4e181
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_ee27ad34-25c3-4fc0-80ef-f84bacc4e181",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92065118",
  "status": "other",
  "office_code": "US",
  "filed_date": "2017-01-09",
  "parties": [
    {
      "name": "KIND Management Inc.",
      "role": "petitioner"
    },
    {
      "name": "Kynd Clothing Inc. dba Kynd",
      "role": "respondent"
    }
  ]
}