Responsible disclosure

Keeping user information safe and secure is a top priority for us at Seamly, and we welcome the contribution of external security researchers.

Scope

If you believe you’ve found a security issue in any of the websites, services, or software as owned or operated by Seamly listed below, we encourage you to notify us.

The following areas are considered to be in scope:

The following areas are considered to be out of scope and are prohibited:

  • Social engineering (e.g. phishing, vishing, smishing)
  • Spam (unless a specific vulnerability leads to easily sending spam)
  • Distributed Denial of Service attacks (DDoS)

What not to report

We will not accept any trivial issues, or vulnerabilities that cannot be exploited. The responsible disclosure is meant for issues that can immediately be exploited.

Examples of issues that will not be accepted:

  • HTTP 404 codes, or any non-200 codes
  • Fingerprinting on public services
  • Public files, or files with harmless information (i.e. robots.txt)
  • Clickjacking-related issues
  • SPF, DKIM or DMARC issues
  • Reports about old software versions without a POC for a working concept
  • Issues related to the use of old browser versions

How to Submit a Report

To submit a vulnerability report to Seamly, please contact us at security@seamly.ai and make sure you encrypt your findings using our PGP key. Your submission will be reviewed and validated by a member of our security team.

Safe Harbor

Seamly supports safe harbor for security researchers who:

  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our services.
    Only interact with accounts you own or with explicit permission of the account holder. If you do encounter Personally Identifiable Information (PII) contact us immediately, do not proceed with access, and immediately purge any local information.
  • Provide us with a reasonable amount of time to resolve vulnerabilities prior to any disclosure to the public or a third-party.
  • We will consider activities conducted consistent with this policy to constitute “authorized” conduct and will not pursue civil action or initiate a complaint to law enforcement. We will help to the extent we can if legal action is initiated by a third party against you.

Please submit a report to us before engaging in conduct that may be inconsistent with or unaddressed by this policy. We will send you a response within three business days.

Preferences

  • Please provide detailed reports with reproducible steps and a clearly defined impact.
  • Submit one vulnerability per report.
  • Encrypt your findings using our PGP key to prevent unauthorised users from accessing the information.
© Copyright 2024 -