Opposition · USPTO

Opposition 91264814

OtherUSPTO

Opposition 91264814 at USPTO between Apple Inc. and Silver Brush, Inc, over the mark CLEANMYPODS, filed Sep 16, 2020. Status in the office record: other.

View CLEANMYPODSGet this data via the API
Status
Other
Result
Other
Filed
Sep 16, 2020
Marks involved
15
Parties

Who is involved

The parties as named in the office record.

Opponent

Apple Inc.

Company trademarks
Respondent

Silver Brush, Inc

Timeline

How the case has moved

Dates from the USPTO record and the CLEANMYPODS filing.

  1. CLEANMYPODS filed

    Application 88758296 filed at the USPTO.

  2. Opposition filed

    Apple Inc. started opposition 91264814 at USPTO against CLEANMYPODS.
Marks

Marks involved

1 contested mark, 14 marks the challenger relies on.

MarkRoleApplicationOffice
CLEANMYPODSContested88758296USPTO
IPODRelied on75982871USPTO
IPODRelied on77013000USPTO
IPODRelied on78089144USPTO
IPODRelied on78521796USPTO
IPODRelied on78653661USPTO
IPODRelied on78653667USPTO
IPODRelied on78981523USPTO
APPLE EARPODSRelied on85728401USPTO
EARPODSRelied on85743152USPTO
AIRPODSRelied on86764566USPTO
HOMEPODRelied on87486392USPTO

+3 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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_e3c262d1-a4cd-4658-9834-73d5927d1b47
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_e3c262d1-a4cd-4658-9834-73d5927d1b47",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91264814",
  "status": "other",
  "office_code": "US",
  "filed_date": "2020-09-16",
  "parties": [
    {
      "name": "Apple Inc.",
      "role": "opponent"
    },
    {
      "name": "Silver Brush, Inc",
      "role": "respondent"
    }
  ]
}