Opposition · USPTO

Opposition 91303936

PendingUSPTO

Opposition 91303936 at USPTO between Salesforce, Inc. and Entertainment Software Association, over the mark [Design Mark], filed Dec 19, 2025. Status in the office record: pending.

Status
Pending
Filed
Dec 19, 2025
Marks involved
7
Parties

Who is involved

The parties as named in the office record.

Opponent

Salesforce, Inc.

Company trademarks
Respondent

Entertainment Software Association

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the [Design Mark] filing.

  1. [Design Mark] filed

    Application 98859201 filed at the USPTO.
  2. Opposition filed

    Salesforce, Inc. started opposition 91303936 at USPTO against [Design Mark].
  3. Next

    Awaiting decision

    No decision is recorded at USPTO yet.
Marks

Marks involved

2 contested marks, 5 marks the challenger relies on.

MarkRoleApplicationOffice
[Design mark]Contested98859201USPTO
ACCESSIBLE GAMES INITIATIVEContested98859267USPTO
[Design mark]Relied on88264327USPTO
[Design mark]Relied on88781359USPTO
[Design mark]Relied on88781370USPTO
[Design mark]Relied on90067946USPTO
[Design mark]Relied on90067948USPTO
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_a40a441f-2c86-4123-adde-a24a5319e60a
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_a40a441f-2c86-4123-adde-a24a5319e60a",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91303936",
  "status": "pending",
  "office_code": "US",
  "filed_date": "2025-12-19",
  "parties": [
    {
      "name": "Salesforce, Inc.",
      "role": "opponent"
    },
    {
      "name": "Entertainment Software Association",
      "role": "respondent"
    }
  ]
}