Cancellation · USPTO

Cancellation 92079749

OtherUSPTO

Cancellation 92079749 at USPTO between Lanning Janosov and Shenzhen Yuanping Fuxing Technology Co., Ltd., over the mark HIPLAYGIRL, filed May 18, 2022. Status in the office record: other.

Status
Other
Result
Other
Filed
May 18, 2022
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Petitioner

Lanning Janosov

Respondent

Shenzhen Yuanping Fuxing Technology Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the HIPLAYGIRL filing.

  1. HIPLAYGIRL filed

    Application 87500507 filed at the USPTO.
  2. HIPLAYGIRL registered

  3. Cancellation filed

    Lanning Janosov started cancellation 92079749 at USPTO against HIPLAYGIRL.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
HIPLAYGIRLContested87500507USPTO
PLAYGIRLRelied on72430794USPTO
PLAYGIRLRelied on73706458USPTO
PLAYGIRLRelied on75819517USPTO
PLAYGIRLRelied on75983473USPTO
PLAYGIRL ENTERTAINMENT FOR WOMENRelied on78317618USPTO
PLAYGIRLRelied on78324067USPTO
PLAYGIRL BLUERelied on86431837USPTO
PLAYGIRL.COMRelied on86478165USPTO
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_78982e27-28b2-4988-874a-29cebad362c1
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_78982e27-28b2-4988-874a-29cebad362c1",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92079749",
  "status": "other",
  "office_code": "US",
  "filed_date": "2022-05-18",
  "parties": [
    {
      "name": "Lanning Janosov",
      "role": "petitioner"
    },
    {
      "name": "Shenzhen Yuanping Fuxing Technology Co., Ltd.",
      "role": "respondent"
    }
  ]
}