Opposition · USPTO

Opposition 91299045

OtherUSPTO

Opposition 91299045 at USPTO between JUUL Labs, Inc. and Kangvape LLC, over the mark BLUE JEWEL, filed May 16, 2025. Status in the office record: other.

View BLUE JEWELGet this data via the API
Status
Other
Result
Other
Filed
May 16, 2025
Marks involved
13
Parties

Who is involved

The parties as named in the office record.

Opponent

JUUL Labs, Inc.

Company trademarks
Respondent

Kangvape LLC

Timeline

How the case has moved

Dates from the USPTO record and the BLUE JEWEL filing.

  1. BLUE JEWEL filed

    Application 98789549 filed at the USPTO.

  2. Opposition filed

    JUUL Labs, Inc. started opposition 91299045 at USPTO against BLUE JEWEL.
Marks

Marks involved

1 contested mark, 12 marks the challenger relies on.

MarkRoleApplicationOffice
BLUE JEWELContested98789549USPTO
JUULRelied on86156947USPTO
JUULRelied on86683423USPTO
JUUL LABSRelied on87455960USPTO
JUULRelied on88052996USPTO
JUULRelied on88052998USPTO
JUULRelied on88053004USPTO
JUULPODSRelied on88289543USPTO
JUUL C1Relied on88524986USPTO
JUUL PASSRelied on88550676USPTO
JUULPODRelied on88630166USPTO
JUUL2Relied on98552754USPTO

+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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_1071fbc6-6323-49b1-b516-a6b25e9531eb
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_1071fbc6-6323-49b1-b516-a6b25e9531eb",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91299045",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-05-16",
  "parties": [
    {
      "name": "JUUL Labs, Inc.",
      "role": "opponent"
    },
    {
      "name": "Kangvape LLC",
      "role": "respondent"
    }
  ]
}