Cancellation · USPTO

Cancellation 92090414

PendingUSPTO

Cancellation 92090414 at USPTO between Alconox, LLC and Stoner Incorporated, over the mark CRITICAL CLEANING, filed Dec 18, 2025. Status in the office record: pending.

View CRITICAL CLEANINGGet this data via the API
Status
Pending
Filed
Dec 18, 2025
Marks involved
4
Parties

Who is involved

The parties as named in the office record.

Petitioner

Alconox, LLC

Respondent

Stoner Incorporated

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the CRITICAL CLEANING filing.

  1. CRITICAL CLEANING filed

    Application 98704785 filed at the USPTO.

  2. CRITICAL CLEANING registered

  3. Cancellation filed

    Alconox, LLC started cancellation 92090414 at USPTO against CRITICAL CLEANING.
  4. Next

    Awaiting decision

    No decision is recorded at USPTO yet.
Marks

Marks involved

1 contested mark, 3 marks the challenger relies on.

MarkRoleApplicationOffice
CRITICAL CLEANINGContested98704785USPTO
TECHNOTES CRITICAL CLEANING ADVICE FROM ALCONOX INC.Relied on88912558USPTO
CRITICAL CLEANING EXPERTSRelied on99357662USPTO
ALCONOX CRITICAL CLEANING EXPERTSRelied on99357693USPTO
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_78f7169e-1aae-4d04-8472-5161aa74e06e
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_78f7169e-1aae-4d04-8472-5161aa74e06e",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92090414",
  "status": "pending",
  "office_code": "US",
  "filed_date": "2025-12-18",
  "parties": [
    {
      "name": "ALCONOX, LLC",
      "role": "petitioner"
    },
    {
      "name": "Stoner Incorporated",
      "role": "respondent"
    }
  ]
}