Opposition 91308954
PendingUSPTO
Opposition 91308954 at USPTO between SIC Enterprise, Inc. and Tru Beauty, LLC, over the mark BOUNCE BOOSTER, filed Jul 20, 2026. Status in the office record: pending.
- Status
- Pending
- Filed
- Jul 20, 2026
- Marks involved
- 10
Parties
Who is involved
The parties as named in the office record.
Respondent
Tru Beauty, LLC
Timeline
How the case has moved
Dates from the USPTO record and the BOUNCE BOOSTER filing.
BOUNCE BOOSTER filed
Application 99307134 filed at the USPTO.Opposition filed
SIC Enterprise, Inc. started opposition 91308954 at USPTO against BOUNCE BOOSTER.- Next
Awaiting decision
No decision is recorded at USPTO yet.
Marks
Marks involved
1 contested mark, 9 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| BOUNCE BOOSTER | Contested | 99307134 | USPTO |
| EDGE BOOSTER | Relied on | 86947797 | USPTO |
| LOCK BOOSTER | Relied on | 88250630 | USPTO |
| EDGEBOOSTER | Relied on | 88414993 | USPTO |
| EDGEBOOSTER | Relied on | 90086337 | USPTO |
| WAVEBOOSTER | Relied on | 90307203 | USPTO |
| WAVEBOOSTER | Relied on | 90789019 | USPTO |
| WAVEBOOSTER | Relied on | 90833116 | USPTO |
| BRAIDBOOSTER | Relied on | 97122710 | USPTO |
| EDGE BOOSTER | Relied on | 98835037 | USPTO |
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_a89c8dfb-a6a8-4ed7-9e4a-6dc44db686a9
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_a89c8dfb-a6a8-4ed7-9e4a-6dc44db686a9",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91308954",
"status": "pending",
"office_code": "US",
"filed_date": "2026-07-20",
"parties": [
{
"name": "SIC Enterprise, Inc.",
"role": "opponent"
},
{
"name": "Tru Beauty, LLC",
"role": "respondent"
}
]
}