Opposition · USPTO

Opposition 91309636

SuspendedUSPTO

Opposition 91309636 at USPTO between Alo, LLC and Mingrong Xue, over the mark ALOFREE, filed Aug 13, 2026. Status in the office record: suspended.

View ALOFREEGet this data via the API
Status
Suspended
Filed
Aug 13, 2026
Marks involved
12
Parties

Who is involved

The parties as named in the office record.

Opponent

Alo, LLC

Company trademarks
Respondent

Mingrong Xue

Timeline

How the case has moved

Dates from the USPTO record and the ALOFREE filing.

  1. ALOFREE filed

    Application 99653372 filed at the USPTO.

  2. Opposition filed

    Alo, LLC started opposition 91309636 at USPTO against ALOFREE.
  3. Next

    Suspended

    No decision is recorded at USPTO yet.
Marks

Marks involved

1 contested mark, 11 marks the challenger relies on.

MarkRoleApplicationOffice
ALOFREEContested99653372USPTO
ALORelied on77891801USPTO
ALORelied on86741238USPTO
ALORelied on87782928USPTO
ALORelied on88759109USPTO
ALORelied on97411962USPTO
ALORelied on97902657USPTO
ALORelied on98085815USPTO
ALO STACKABLE WELLNESSRelied on98214658USPTO
ALO WELLNESS SYSTEMRelied on98423417USPTO
ALORelied on98805132USPTO
ALORelied on99032896USPTO
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_705c813b-4939-4d30-b341-3466b7d0caa6
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_705c813b-4939-4d30-b341-3466b7d0caa6",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91309636",
  "status": "suspended",
  "office_code": "US",
  "filed_date": "2026-08-13",
  "parties": [
    {
      "name": "ALO, LLC",
      "role": "opponent"
    },
    {
      "name": "Mingrong Xue",
      "role": "respondent"
    }
  ]
}