Opposition · USPTO

Opposition 91256617

OtherUSPTO

Opposition 91256617 at USPTO between Lyft Inc. and Bridge Enterprises Co., over the mark BRITELIFT, filed Jun 24, 2020. Status in the office record: other.

View BRITELIFTGet this data via the API
Status
Other
Result
Other
Filed
Jun 24, 2020
Marks involved
31
Parties

Who is involved

The parties as named in the office record.

Opponent

Lyft Inc.

Company trademarks
Respondent

Bridge Enterprises Co.

Timeline

How the case has moved

Dates from the USPTO record and the BRITELIFT filing.

  1. BRITELIFT filed

    Application 88564451 filed at the USPTO.

  2. Opposition filed

    Lyft Inc. started opposition 91256617 at USPTO against BRITELIFT.
Marks

Marks involved

2 contested marks, 29 marks the challenger relies on.

MarkRoleApplicationOffice
BRITELIFTContested88564451USPTO
BRITELIFT INCContested88585427USPTO
LYFTRelied on85743120USPTO
LYFTRelied on86183222USPTO
LYFTRelied on86183253USPTO
LYFTRelied on86183891USPTO
LYFTRelied on86183906USPTO
LYFT LINERelied on86872085USPTO
LYFTRelied on86982665USPTO
UNDERCOVER LYFTRelied on87182313USPTO
LYFTRelied on87254350USPTO
LYFTRelied on87913906USPTO

+19 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_6a65e6e9-67e0-4c9e-af84-85ef08989716
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_6a65e6e9-67e0-4c9e-af84-85ef08989716",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91256617",
  "status": "other",
  "office_code": "US",
  "filed_date": "2020-06-24",
  "parties": [
    {
      "name": "Lyft Inc.",
      "role": "opponent"
    },
    {
      "name": "Bridge Enterprises Co.",
      "role": "respondent"
    }
  ]
}