Opposition 91302494
PendingUSPTO
Opposition 91302494 at USPTO between Alo, LLC and Glo Digital, Inc., over the mark GLO, filed Oct 16, 2025. Status in the office record: pending.
- Status
- Pending
- Filed
- Oct 16, 2025
- Marks involved
- 19
Parties
Who is involved
The parties as named in the office record.
Opponent
Alo, LLC
Respondent
Glo Digital, Inc.
Timeline
How the case has moved
Dates from the USPTO record and the GLO filing.
GLO filed
Application 77956879 filed at the USPTO.GLO registered
Opposition filed
Alo, LLC started opposition 91302494 at USPTO against GLO.- Next
Awaiting decision
No decision is recorded at USPTO yet.
Marks
Marks involved
3 contested marks, 16 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| GLO | Contested | 77956879 | USPTO |
| GLO | Contested | 85810776 | USPTO |
| GLO | Contested | 88250265 | USPTO |
| ALO | Relied on | 77891801 | USPTO |
| ALO SPORT | Relied on | 85981400 | USPTO |
| ALO YOGA | Relied on | 86741208 | USPTO |
| ALO | Relied on | 86741238 | USPTO |
| ALO MOVES | Relied on | 87709225 | USPTO |
| ALO | Relied on | 87781772 | USPTO |
| ALO | Relied on | 87782928 | USPTO |
| ALO GIVES | Relied on | 87793293 | USPTO |
| ALOSOFT | Relied on | 88595042 | USPTO |
+7 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 /v1/proceedings/{id}
ID=prc_8d7eae67-d334-4a59-a19d-4113238eb6c7
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_8d7eae67-d334-4a59-a19d-4113238eb6c7",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91302494",
"status": "pending",
"office_code": "US",
"filed_date": "2025-10-16",
"parties": [
{
"name": "ALO, LLC",
"role": "opponent"
},
{
"name": "Glo Digital, Inc.",
"role": "respondent"
}
]
}