Opposition · USPTO

Opposition 91294516

OtherUSPTO

Opposition 91294516 at USPTO between Apple Inc. and Shenzhen Disan Technology Co., Ltd., over the mark MACLE, filed Oct 11, 2024. Status in the office record: other.

Status
Other
Result
Other
Filed
Oct 11, 2024
Marks involved
13
Parties

Who is involved

The parties as named in the office record.

Opponent

Apple Inc.

Company trademarks
Respondent

Shenzhen Disan Technology Co., Ltd.

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the MACLE filing.

  1. MACLE filed

    Application 98235008 filed at the USPTO.
  2. Opposition filed

    Apple Inc. started opposition 91294516 at USPTO against MACLE.
Marks

Marks involved

1 contested mark, 12 marks the challenger relies on.

MarkRoleApplicationOffice
MACLEContested98235008USPTO
MACRelied on74357318USPTO
MAC OSRelied on74547403USPTO
IMACRelied on76070198USPTO
MACBOOK AIRRelied on77371650USPTO
MACINTOSHRelied on77532612USPTO
MACBOOKRelied on78821058USPTO
MAC PRORelied on78885695USPTO
MACBOOK PRORelied on85236152USPTO
MAC MINIRelied on86751917USPTO
MACOSRelied on87158259USPTO
IMAC PRORelied on87527432USPTO

+1 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_6585b56f-516d-40e4-8adb-34dee13709ec
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_6585b56f-516d-40e4-8adb-34dee13709ec",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91294516",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-10-11",
  "parties": [
    {
      "name": "Apple Inc.",
      "role": "opponent"
    },
    {
      "name": "Shenzhen Disan Technology Co., Ltd.",
      "role": "respondent"
    }
  ]
}