Opposition · USPTO

Opposition 91294130

OtherUSPTO

Opposition 91294130 at USPTO between Golo, LLC and Emmanuel Mendoza Gonzalez, over the mark GOL UP, filed Sep 23, 2024. Status in the office record: other.

View GOL UPGet this data via the API
Status
Other
Result
Other
Filed
Sep 23, 2024
Marks involved
20
Parties

Who is involved

The parties as named in the office record.

Opponent

Golo, LLC

Company trademarks
Respondent

Emmanuel Mendoza Gonzalez

Timeline

How the case has moved

Dates from the USPTO record and the GOL UP filing.

  1. GOL UP filed

    Application 98308650 filed at the USPTO.

  2. Opposition filed

    Golo, LLC started opposition 91294130 at USPTO against GOL UP.
Marks

Marks involved

1 contested mark, 19 marks the challenger relies on.

MarkRoleApplicationOffice
GOL UPContested98308650USPTO
GOLORelied on85374201USPTO
GOLO FOR LIFERelied on85380655USPTO
GOLORelied on87075500USPTO
MYGOLORelied on87076408USPTO
GOLO SMART CARDRelied on87088646USPTO
GOLORelied on87439564USPTO
GOLORelied on87858964USPTO
GOLORelied on87978072USPTO
GOLORelied on90850117USPTO
GOLORelied on97098983USPTO
GOLORelied on97098987USPTO

+8 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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_e156a66d-5843-42df-b2d3-226c4dff86ac
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_e156a66d-5843-42df-b2d3-226c4dff86ac",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91294130",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-09-23",
  "parties": [
    {
      "name": "GOLO, LLC",
      "role": "opponent"
    },
    {
      "name": "Emmanuel Mendoza Gonzalez",
      "role": "respondent"
    }
  ]
}