Opposition · USPTO

Opposition 91299168

OtherUSPTO

Opposition 91299168 at USPTO between Box, Inc. and Elevux LLC, over the mark INFOBOX.AI, filed May 21, 2025. Status in the office record: other.

View INFOBOX.AIGet this data via the API
Status
Other
Result
Other
Filed
May 21, 2025
Marks involved
26
Parties

Who is involved

The parties as named in the office record.

Opponent

Box, Inc.

Company trademarks
Respondent

Elevux LLC

Timeline

How the case has moved

Dates from the USPTO record and the INFOBOX.AI filing.

  1. INFOBOX.AI filed

    Application 98240135 filed at the USPTO.

  2. Opposition filed

    Box, Inc. started opposition 91299168 at USPTO against INFOBOX.AI.
Marks

Marks involved

1 contested mark, 25 marks the challenger relies on.

MarkRoleApplicationOffice
INFOBOX.AIContested98240135USPTO
BOXRelied on77015157USPTO
BOXRelied on85022983USPTO
BOX SYNCRelied on85450245USPTO
BOX NOTESRelied on85918109USPTO
BOXWORKSRelied on85977267USPTO
BOXWORKSRelied on85978767USPTO
BOX NOTESRelied on85979605USPTO
BOX VIEWRelied on86137624USPTO
BOXDEVRelied on86176928USPTO
BOX PLATFORMRelied on86790304USPTO
BOX PLATFORMRelied on86982702USPTO

+14 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_6c541b3f-12d6-45c4-baf5-8c0e6d3a3db5
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_6c541b3f-12d6-45c4-baf5-8c0e6d3a3db5",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91299168",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-05-21",
  "parties": [
    {
      "name": "Box, Inc.",
      "role": "opponent"
    },
    {
      "name": "Elevux LLC",
      "role": "respondent"
    }
  ]
}