Vulnerability Disclosure Policy

Paddle.com Market Limited (and our subsidiaries) (the "Paddle Group") offers SaaS companies a completely different approach to their payments infrastructure. Instead of assembling and maintaining a complex stack of payments-related apps and services, we're a merchant of record for our customers, taking away 100% of the pain of payments fragmentation. It's faster, safer, simpler, and above all, way better. ProfitWell helps over 30,000 companies to measure and automate their subscription revenue growth. ProfitWell’s Metrics product is the number one real-time subscription reporting product on the market. Retain is the industry-leading automatic churn reduction tool. And Price Intelligently is synonymous with optimizing SaaS and subscription pricing.

This vulnerability disclosure policy applies to any vulnerabilities you are considering reporting to us. We recommend reading this vulnerability disclosure policy fully before you report a vulnerability and always acting in compliance with it.

We value those who take the time and effort to report security vulnerabilities according to this policy. However, we do not offer monetary rewards for vulnerability disclosures. For the first report of any accepted vulnerability, we would be happy to list the reporter's name (with their consent) on our hall of fame.

Reporting

If you believe you have found a security vulnerability, please submit your report here.

In your report please include details of:

• The website, IP or page where the vulnerability can be observed.
• A brief description of the type of vulnerability, for example; "XSS vulnerability".
• Steps to reproduce. These should be a benign, non-destructive, proof of concept. This helps to ensure that the report can be triaged quickly and accurately. It also reduces the likelihood of duplicate reports, or malicious exploitation of some vulnerabilities, such as sub-domain takeovers.
  

What to expect

After you have submitted your report, it will be triaged and we aim to respond all valid/accepted reports promptly, usually within 5 working days. For reports that relate to an issue we are already aware of, or where we we do not believe a vulnerability exists, we will not routinely follow up by email. If we require further details from you we will get in touch, but you are always welcome to contact us as outlined below to enquire on the status of a report. Every submission that we receive will be triaged and routed accordingly.

Priority for remediation is assessed by looking at the impact, severity and exploit complexity. Vulnerability reports might take some time to triage or address. You are welcome to enquire on the status by contacting appsec+vdp [at] paddle [dot] com, but should avoid doing so more than once every 14 days. This allows our teams to focus on the remediation.

If your report is accepted, we will notify you when the vulnerability is remediated, and you may be invited to confirm that the solution covers the vulnerability adequately.

Once your vulnerability has been resolved, we welcome requests to disclose your report. We'd like to unify guidance to affected users, so please do continue to coordinate public release with us.

Guidance

This policy is applicable to paddle.com, any subdomains of paddle.com, profitwell.com, any subdomains of profitwell.com, priceintelligently.com and any subdomains of priceintelligently.com.

You must not:

• Break any applicable law or regulations.
• Access unnecessary, excessive or significant amounts of data.
• Continue the test if any personal data (other than your own) is encountered.
• Modify data in the Paddle Group's systems or services.
• Use high-intensity invasive or destructive scanning tools to find vulnerabilities.
• Attempt or report any form of denial of service, e.g. overwhelming a service with a high volume of requests.
• Disrupt the Paddle Group's services or systems.
• Submit reports detailing non-exploitable vulnerabilities, or reports indicating that the services do not fully align with "best practice", for example missing security headers.
• Submit reports detailing TLS configuration weaknesses, for example "weak" cipher suite support or the presence of TLS1.0 support.
• Communicate any vulnerabilities or associated details other than by means described in the published security.txt.
• Social engineer, 'phish' or physically attack the Paddle Group's staff or infrastructure.
• Demand financial compensation in order to disclose any vulnerabilities.

You must always:

• Comply with data protection rules and must not violate the privacy of the Paddle Group's users, staff, contractors, services or systems. You must not, for example, share, redistribute or fail to properly secure data retrieved from the systems or services.
• Securely delete all data retrieved during your research as soon as it is no longer required or within 1 month of the vulnerability being resolved, whichever occurs first (or as otherwise required by data protection law).
  

Legalities

This policy is designed to be compatible with common vulnerability disclosure good practice. It does not give you permission to act in any manner that is inconsistent with the law, or which might cause the Paddle Group or partner companies to be in breach of any legal obligations.

Security disclosure acknowledgments