Responsible disclosure

Last updated: May 10, 2024

Data security is a top priority for Assembled, Inc., and Assembled, Inc. believes that working with skilled security researchers can identify weaknesses in any technology.

If you believe you've found a security vulnerability in Assembled, Inc.'s service, please notify us; we will work with you to resolve the issue promptly.

Disclosure policy

If you believe you've discovered a potential vulnerability, please let us know by emailing us at security@assembledhq.com. We will acknowledge your email within 48 hours.
Provide us with a reasonable amount of time to resolve the issue before disclosing it to the public or a third party. We aim to resolve critical issues within 90 days of disclosure.
Make a good faith effort to avoid violating privacy, destroying data, or interrupting or degrading the Assembled, Inc. service. Please only interact with accounts you own or for which you have explicit permission from the account holder.

Exclusions

While researching, we'd like you to refrain from:

Distributed Denial of Service (DDoS)
Spamming
Social engineering or phishing of Assembled, Inc. employees or contractors
Any attacks against Assembled, Inc.'s physical property or data centers

We do not accept reports of the following categories:

Ability to perform an action unavailable via user interface without identified security risks
Ability to send emails with no control over content without any limits
Any activity that could lead to the disruption of our service (DoS)
Attacks that require MiTM or physical access to a user's device
Clickjacking
Content spoofing and text injection
CSV injection without demonstrating a vulnerability
Disclosure of non-sensitive information, like product version, file path on a server, stack trace, etc.
Disclosure of private IP addresses or domains pointing to private IP addresses
Leakage of sensitive tokens (e.g. password reset token) to trusted third parties on secure connection (HTTPS)
Missing best practices in SSL/TLS configuration
Missing best practices in DNS configuration (DKIM/DMARC/SPF/TXT)
Missing best practices in HTTP headers without demonstrating a vulnerability
Missing notifications about important actions
Missing protection mechanism or best practices without demonstration of real security impact for user or system
Previously known vulnerable libraries without a working proof of concept
Unauthenticated/login/logout CSRF
User enumeration
Vectors that require browser versions released 6 or more months before report submission
Disclosure of JavaScript API keys (e.g. API key for external map service)

Thank you for helping to keep Assembled, Inc. and our users safe!

Changes

We may revise these guidelines from time to time. The most current version of the guidelines will be available at assembled.com/responsible-disclosure.

Contact

Assembled, Inc. is always open to feedback, questions, and suggestions. If you would like to talk to us, please feel free to email us at security@assembledhq.com.

Disciplinary action

Employees who violate this policy may face disciplinary consequences in proportion to their violation. Assembled, Inc. management will determine how serious an employee's offense is and take the appropriate action.

Responsibility