Opposition · USPTO

Opposition 91247699

OtherUSPTO

Opposition 91247699 at USPTO between The Insights Group Limited and The Sentry Marketing Group, LLC DBA Sentry Insights, over the mark SENTRY INSIGHTS, filed Apr 22, 2019. Status in the office record: other.

Status
Other
Result
Other
Filed
Apr 22, 2019
Marks involved
7
Parties

Who is involved

The parties as named in the office record.

Opponent

The Insights Group Limited

Company trademarks
Respondent

The Sentry Marketing Group, LLC DBA Sentry Insights

Timeline

How the case has moved

Dates from the USPTO record and the SENTRY INSIGHTS filing.

  1. SENTRY INSIGHTS filed

    Application 87943508 filed at the USPTO.
  2. Opposition filed

    The Insights Group Limited started opposition 91247699 at USPTO against SENTRY INSIGHTS.
Marks

Marks involved

1 contested mark, 6 marks the challenger relies on.

MarkRoleApplicationOffice
SENTRY INSIGHTSContested87943508USPTO
INSIGHTSRelied on77464026USPTO
INSIGHTS DISCOVERYRelied on77464077USPTO
INSIGHTS NAVIGATORRelied on77464183USPTO
INSIGHTS NAVIGATORRelied on77464258USPTO
INSIGHTSRelied on77464297USPTO
INSIGHTS DISCOVERYRelied on77464322USPTO
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_14749bb3-38a5-4245-8eeb-e7c274abd470
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_14749bb3-38a5-4245-8eeb-e7c274abd470",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91247699",
  "status": "other",
  "office_code": "US",
  "filed_date": "2019-04-22",
  "parties": [
    {
      "name": "The Insights Group Limited",
      "role": "opponent"
    },
    {
      "name": "The Sentry Marketing Group, LLC DBA Sentry Insights",
      "role": "respondent"
    }
  ]
}