Opposition · USPTO

Opposition 91292287

OtherUSPTO

Opposition 91292287 at USPTO between Apple, Inc. and Shenzhen Jiashixin Technology Co., Ltd., over the mark MACSECOR, filed Jun 25, 2024. Status in the office record: other.

Status
Other
Result
Other
Filed
Jun 25, 2024
Marks involved
13
Parties

Who is involved

The parties as named in the office record.

Opponent

Apple, Inc.

Company trademarks
Respondent

Shenzhen Jiashixin Technology Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the MACSECOR filing.

  1. MACSECOR filed

    Application 97899548 filed at the USPTO.
  2. Opposition filed

    Apple, Inc. started opposition 91292287 at USPTO against MACSECOR.
Marks

Marks involved

1 contested mark, 12 marks the challenger relies on.

MarkRoleApplicationOffice
MACSECORContested97899548USPTO
MACRelied on74357318USPTO
MAC OSRelied on74547403USPTO
IMACRelied on76070198USPTO
MACINTOSHRelied on77532612USPTO
MACBOOKRelied on78821058USPTO
MAC PRORelied on78885695USPTO
MACBOOK PRORelied on85236152USPTO
MAC MINIRelied on86751917USPTO
MACOSRelied on87158259USPTO
MACOSRelied on87158287USPTO
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_d7661971-24f2-487b-8c49-56490bc2d739
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_d7661971-24f2-487b-8c49-56490bc2d739",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91292287",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-06-25",
  "parties": [
    {
      "name": "Apple, Inc.",
      "role": "opponent"
    },
    {
      "name": "Shenzhen Jiashixin Technology Co., Ltd.",
      "role": "respondent"
    }
  ]
}