Opposition · USPTO

Opposition 91268542

OtherUSPTO

Opposition 91268542 at USPTO between JUUL Labs, Inc. and Cloverleaf Services, Inc., over the mark CÜL, filed Apr 2, 2021. Status in the office record: other.

View CÜLGet this data via the API
Status
Other
Result
Other
Filed
Apr 2, 2021
Marks involved
15
Parties

Who is involved

The parties as named in the office record.

Opponent

JUUL Labs, Inc.

Company trademarks
Respondent

Cloverleaf Services, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the CÜL filing.

  1. CÜL filed

    Application 88422450 filed at the USPTO.

  2. Opposition filed

    JUUL Labs, Inc. started opposition 91268542 at USPTO against CÜL.
Marks

Marks involved

1 contested mark, 14 marks the challenger relies on.

MarkRoleApplicationOffice
CÜLContested88422450USPTO
JUULRelied on86156947USPTO
JUULRelied on86683423USPTO
JUULSALTSRelied on87374462USPTO
JUUL LABSRelied on87455960USPTO
JUUL LABSRelied on87657660USPTO
JUULRelied on88052996USPTO
JUULRelied on88052998USPTO
JUULRelied on88053004USPTO
JUULPODSRelied on88289543USPTO
JUUL C1Relied on88524986USPTO
JUUL C2Relied on88524992USPTO

+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_ac466db1-2ee9-4bb3-a075-fb1f83ae8e92
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_ac466db1-2ee9-4bb3-a075-fb1f83ae8e92",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91268542",
  "status": "other",
  "office_code": "US",
  "filed_date": "2021-04-02",
  "parties": [
    {
      "name": "JUUL Labs, Inc.",
      "role": "opponent"
    },
    {
      "name": "Cloverleaf Services, Inc.",
      "role": "respondent"
    }
  ]
}