Opposition · USPTO

Opposition 91284398

OtherUSPTO

Opposition 91284398 at USPTO between Uber Technologies, Inc. and Gorilla Skin LLC, over the mark UBERDERM, filed Apr 10, 2023. Status in the office record: other.

Status
Other
Result
Other
Filed
Apr 10, 2023
Marks involved
36
Parties

Who is involved

The parties as named in the office record.

Opponent

Uber Technologies, Inc.

Company trademarks
Respondent

Gorilla Skin LLC

Timeline

How the case has moved

Dates from the USPTO record and the UBERDERM filing.

  1. UBERDERM filed

    Application 90829605 filed at the USPTO.
  2. Opposition filed

    Uber Technologies, Inc. started opposition 91284398 at USPTO against UBERDERM.
Marks

Marks involved

1 contested mark, 35 marks the challenger relies on.

MarkRoleApplicationOffice
UBERDERMContested90829605USPTO
UBERRelied on85170655USPTO
UBERXRelied on86198791USPTO
UBER HEALTHRelied on86496538USPTO
UBER EATSRelied on86541663USPTO
UBERPOOLRelied on86645284USPTO
UBER FREIGHTRelied on87195689USPTO
UBERRelied on87256010USPTO
UBER AIRRelied on87430754USPTO
UBER HEALTHRelied on87445745USPTO
UBERRelied on87662754USPTO
UBER MOVEMENTRelied on87818737USPTO

+24 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_2a97ec95-bc3f-4606-980c-f9307b05e177
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_2a97ec95-bc3f-4606-980c-f9307b05e177",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91284398",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-04-10",
  "parties": [
    {
      "name": "Uber Technologies, Inc.",
      "role": "opponent"
    },
    {
      "name": "Gorilla Skin LLC",
      "role": "respondent"
    }
  ]
}