Opposition · USPTO

Opposition 91252842

OtherUSPTO

Opposition 91252842 at USPTO between Snap Inc. and CSNAPS Corp., over the mark CHARITY SNAP, filed Dec 11, 2019. Status in the office record: other.

View CHARITY SNAPGet this data via the API
Status
Other
Result
Other
Filed
Dec 11, 2019
Marks involved
13
Parties

Who is involved

The parties as named in the office record.

Opponent

Snap Inc.

Company trademarks
Respondent

CSNAPS Corp.

Timeline

How the case has moved

Dates from the USPTO record and the CHARITY SNAP filing.

  1. CHARITY SNAP filed

    Application 88094602 filed at the USPTO.

  2. Opposition filed

    Snap Inc. started opposition 91252842 at USPTO against CHARITY SNAP.
Marks

Marks involved

1 contested mark, 12 marks the challenger relies on.

MarkRoleApplicationOffice
CHARITY SNAPContested88094602USPTO
SNAPRelied on85368311USPTO
SNAPRelied on85639822USPTO
SNAPCHATRelied on85800506USPTO
SNAPCHATRelied on86335306USPTO
SNAPCHATRelied on86619184USPTO
SNAPCODERelied on86619662USPTO
SNAP ADSRelied on86721820USPTO
SNAPCHATRelied on86978618USPTO
SNAP PUBLISHERRelied on87693210USPTO
SNAP PIXELRelied on87726793USPTO
SNAPRelied on87980668USPTO

+1 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_8d53ffe3-05dc-4d14-a747-fe5675835a63
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_8d53ffe3-05dc-4d14-a747-fe5675835a63",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91252842",
  "status": "other",
  "office_code": "US",
  "filed_date": "2019-12-11",
  "parties": [
    {
      "name": "Snap Inc.",
      "role": "opponent"
    },
    {
      "name": "CSNAPS Corp.",
      "role": "respondent"
    }
  ]
}