Opposition · USPTO

Opposition 91299424

OtherUSPTO

Opposition 91299424 at USPTO between DoorDash, Inc. and LeadDash Marketing LLC, over the mark LEADDASH, filed Jun 4, 2025. Status in the office record: other.

Status
Other
Result
Other
Filed
Jun 4, 2025
Marks involved
18
Parties

Who is involved

The parties as named in the office record.

Opponent

DoorDash, Inc.

Company trademarks
Respondent

LeadDash Marketing LLC

Timeline

How the case has moved

Dates from the USPTO record and the LEADDASH filing.

  1. LEADDASH filed

    Application 98606176 filed at the USPTO.
  2. Opposition filed

    DoorDash, Inc. started opposition 91299424 at USPTO against LEADDASH.
Marks

Marks involved

1 contested mark, 17 marks the challenger relies on.

MarkRoleApplicationOffice
LEADDASHContested98606176USPTO
DOORDASHRelied on86401868USPTO
DOORDASHRelied on87020177USPTO
D DOORDASHRelied on87735124USPTO
D DOORDASHRelied on87735147USPTO
DASHPASSRelied on87803545USPTO
D DOORDASHRelied on88363301USPTO
D DOORDASHRelied on88363360USPTO
DOORDASH DRIVERelied on88616468USPTO
DASHERRelied on88616508USPTO
DP DASHPASSRelied on88660281USPTO
DOORDASH STOREFRONTRelied on88928126USPTO

+6 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_eb0d55df-2f1c-41af-a899-95c6c1d37239
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_eb0d55df-2f1c-41af-a899-95c6c1d37239",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91299424",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-06-04",
  "parties": [
    {
      "name": "DoorDash, Inc.",
      "role": "opponent"
    },
    {
      "name": "LeadDash Marketing LLC",
      "role": "respondent"
    }
  ]
}