Opposition · USPTO

Opposition 91266244

OtherUSPTO

Opposition 91266244 at USPTO between Apple Inc. and Millcreek Tech LLC, over the mark APPLELEMONS, filed Nov 30, 2020. Status in the office record: other.

View APPLELEMONSGet this data via the API
Status
Other
Result
Other
Filed
Nov 30, 2020
Marks involved
12
Parties

Who is involved

The parties as named in the office record.

Opponent

Apple Inc.

Respondent

Millcreek Tech LLC

Timeline

How the case has moved

Dates from the USPTO record and the APPLELEMONS filing.

  1. APPLELEMONS filed

    Application 88788957 filed at the USPTO.

  2. Opposition filed

    Apple Inc. started opposition 91266244 at USPTO against APPLELEMONS.
Marks

Marks involved

2 contested marks, 10 marks the challenger relies on.

MarkRoleApplicationOffice
APPLELEMONSContested88788957USPTO
APPLELEMONSContested88788993USPTO
APPLERelied on77172511USPTO
APPLERelied on77428980USPTO
[Design mark]Relied on78156920USPTO
[Design mark]Relied on78943482USPTO
APPLE WATCHRelied on86389914USPTO
APPLE WATCHRelied on86390028USPTO
WATCHRelied on86390778USPTO
WATCHRelied on86390818USPTO
WATCH EDITIONRelied on86512737USPTO
WATCH SPORTRelied on86512828USPTO
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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_1fa0e697-170a-4ba6-b6fb-f33f57d3c3fd
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_1fa0e697-170a-4ba6-b6fb-f33f57d3c3fd",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91266244",
  "status": "other",
  "office_code": "US",
  "filed_date": "2020-11-30",
  "parties": [
    {
      "name": "Apple Inc.",
      "role": "opponent"
    },
    {
      "name": "Millcreek Tech LLC",
      "role": "respondent"
    }
  ]
}