Opposition · USPTO

Opposition 91302740

OtherUSPTO

Opposition 91302740 at USPTO between Snap, Inc. and SelfieStyler Inc., over the mark SNAP - STYLE - SHARE - SHOP, filed Oct 29, 2025. Status in the office record: other.

View SNAP - STYLE - SHARE - SHOPGet this data via the API
Status
Other
Result
Other
Filed
Oct 29, 2025
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

Snap, Inc.

Respondent

SelfieStyler Inc.

Timeline

How the case has moved

Dates from the USPTO record and the SNAP - STYLE - SHARE - SHOP filing.

  1. SNAP - STYLE - SHARE - SHOP filed

    Application 87310797 filed at the USPTO.

  2. Opposition filed

    Snap, Inc. started opposition 91302740 at USPTO against SNAP - STYLE - SHARE - SHOP.
Marks

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
SNAP - STYLE - SHARE - SHOPContested87310797USPTO
SNAPRelied on85368311USPTO
SNAPRelied on85639822USPTO
SNAPCHATRelied on85800506USPTO
SNAPCHATRelied on86619184USPTO
SNAPCODERelied on86619662USPTO
SNAP ADSRelied on86721820USPTO
SNAPRelied on87673618USPTO
SNAPRelied on87980668USPTO
SNAP ORIGINALSRelied on88150480USPTO
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_c5ae964b-c3f7-4ccd-9ced-7611d2bd6c03
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_c5ae964b-c3f7-4ccd-9ced-7611d2bd6c03",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91302740",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-10-29",
  "parties": [
    {
      "name": "Snap, Inc.",
      "role": "opponent"
    },
    {
      "name": "SelfieStyler Inc.",
      "role": "respondent"
    }
  ]
}