We want to hear about security problems in Partyhat, and we would rather hear about them from you than from an attacker. This page says what is in scope, how to report, what we promise in return, and what we ask of you.
How to report
Email security@partyhat.ai with:
- what you found and where (URL, endpoint, app version);
- the steps to reproduce it;
- what an attacker could do with it, as far as you know.
Please don't include more personal data than you need to show the problem. If you'd like to encrypt your report, say so in a first email and we'll arrange it.
What we promise
- We'll acknowledge your report within 3 business days.
- We'll tell you within 10 business days whether we've confirmed it and what we plan to do.
- We'll keep you updated until it's fixed, and tell you when it is.
- We'll credit you when we publish an advisory, if you want to be credited.
- We won't pursue legal action against good-faith research that follows this policy (see Safe harbour).
In scope
- partyhat.ai and www.partyhat.ai, including the web app
- auth.partyhat.ai (the account and API server)
- The Partyhat desktop app for macOS and Windows, as downloaded from partyhat.ai/downloads
Out of scope
- Third-party services we use (for example our hosting, payment and email providers). Please report those to the provider.
- Denial-of-service, load or volume testing.
- Social engineering of Partyhat staff, contractors, customers or Participants, and physical attacks.
- Automated scanner output without a demonstrated impact.
- Missing best-practice headers or email records with no demonstrated impact (we still welcome a note).
Safe harbour
If you make a good-faith effort to follow this policy, we will consider your research authorised, we won't bring legal action against you for it, and we'll say so if anyone else does. Good faith means you:
- only access as much data as you need to show the problem, and never more than your own account's data where you can avoid it;
- don't change or delete data, and don't degrade the service for others;
- don't use what you find for anything other than reporting it;
- give us reasonable time to fix the problem before you disclose it publicly, normally 90 days from your report, sooner if we've fixed it and agree.
Advisories
When we fix a vulnerability that affected customers or Participants, we publish an advisory here with what happened, who was affected, and what we changed.
No advisories have been published yet.
Machine-readable contact
Our security.txt follows RFC 9116.