Opposition · USPTO

Opposition 91297977

OtherUSPTO

Opposition 91297977 at USPTO between Apple Inc. and My Limited, over the mark [Design Mark], filed Mar 31, 2025. Status in the office record: other.

Status
Other
Result
Other
Filed
Mar 31, 2025
Marks involved
13
Parties

Who is involved

The parties as named in the office record.

Opponent

Apple Inc.

Company trademarks
Respondent

My Limited

Timeline

How the case has moved

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

  1. [Design Mark] filed

    Application 98334998 filed at the USPTO.
  2. Opposition filed

    Apple Inc. started opposition 91297977 at USPTO against [Design Mark].
Marks

Marks involved

1 contested mark, 12 marks the challenger relies on.

MarkRoleApplicationOffice
[Design mark]Contested98334998USPTO
[Design mark]Relied on73162799USPTO
APPLERelied on77172511USPTO
[Design mark]Relied on77356362USPTO
[Design mark]Relied on77648705USPTO
[Design mark]Relied on78155196USPTO
[Design mark]Relied on78408365USPTO
[Design mark]Relied on78408618USPTO
APPLE WATCHRelied on86390028USPTO
WATCHRelied on86390778USPTO
WATCH EDITIONRelied on86512737USPTO
MADE FOR APPLE WATCHRelied on86984141USPTO

+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_4ad7af4c-8682-4743-82b0-8da49f1ae3fc
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_4ad7af4c-8682-4743-82b0-8da49f1ae3fc",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91297977",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-03-31",
  "parties": [
    {
      "name": "Apple Inc.",
      "role": "opponent"
    },
    {
      "name": "My Limited",
      "role": "respondent"
    }
  ]
}