Opposition · USPTO

Opposition 91275844

OtherUSPTO

Opposition 91275844 at USPTO between Fox Head, Inc. and Guangzhou Bingsheng Electronic CommerceCo., Ltd., over the mark DELICATE FOX, filed Apr 27, 2022. Status in the office record: other.

View DELICATE FOXGet this data via the API
Status
Other
Result
Other
Filed
Apr 27, 2022
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Opponent

Fox Head, Inc.

Company trademarks
Respondent

Guangzhou Bingsheng Electronic CommerceCo., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the DELICATE FOX filing.

  1. DELICATE FOX filed

    Application 90790596 filed at the USPTO.

  2. Opposition filed

    Fox Head, Inc. started opposition 91275844 at USPTO against DELICATE FOX.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
DELICATE FOXContested90790596USPTO
FOXRelied on73401867USPTO
FOXRelied on75170440USPTO
FOXGIRLRelied on76443623USPTO
FOXRelied on77744940USPTO
FOXRelied on78774602USPTO
MOTO-X FOXRelied on78981502USPTO
FOX HEADRelied on85723669USPTO
FOX RACINGRelied on85824168USPTO
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_61f8efc3-d87a-4f2c-bfa5-0d01f6112ea7
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_61f8efc3-d87a-4f2c-bfa5-0d01f6112ea7",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91275844",
  "status": "other",
  "office_code": "US",
  "filed_date": "2022-04-27",
  "parties": [
    {
      "name": "Fox Head, Inc.",
      "role": "opponent"
    },
    {
      "name": "Guangzhou Bingsheng Electronic CommerceCo., Ltd.",
      "role": "respondent"
    }
  ]
}