Vulnerability disclosure policy

Effective date: 6 November 2026

SunDevs (Pvt) Ltd welcomes feedback from security researchers and the general public to help improve the security of SunLicense. If you believe you have discovered a vulnerability, privacy issue, exposed data or other security issue in any of our assets, we want to hear from you. This policy explains how to report it, what we expect from you and what you can expect from us.

This policy is based on the disclose.io Core Terms (CC0), with the scope and channels filled in for SunLicense.

Systems in scope

• sunlicense.com, app.sunlicense.com, api.sunlicense.com, docs.sunlicense.com, portal.sunlicense.com and status.sunlicense.com
• The official SDKs and starter templates published under github.com/sunlicense-com, and the sunlicense CLI
• The SunLicense Discord app and the remote MCP server at api.sunlicense.com/mcp

Out of scope

• Assets or other equipment not owned by parties participating in this policy, including our providers (Cloudflare, Oracle Cloud, Paddle, Brevo, Sentry, Google, GitHub, Discord). Report issues in their systems to them.
• Organizations' own domains pointing at their customer portal, and the software our customers sell (report those to the organization concerned)
• Denial-of-service, load or volumetric testing, spam, social engineering and phishing of our staff or customers, and physical attacks
• Findings without a demonstrated security impact, such as missing best-practice headers on pages with no sensitive content, banner or version disclosure, or self-XSS

Vulnerabilities discovered or suspected in out-of-scope systems should be reported to the appropriate vendor or applicable authority.

Our commitments

When working with us under this policy, you can expect us to:

• respond to your report promptly (we acknowledge every report within 3 business days), and work with you to understand and validate it;
• strive to keep you informed about the progress of a vulnerability as it is processed;
• work to remediate discovered vulnerabilities in a timely manner, within our operational constraints;
• credit you, if you wish, once the issue is fixed; and
• extend Safe Harbor for your vulnerability research that is related to this policy.

Our expectations

In participating in our vulnerability disclosure program in good faith, we ask that you:

• play by the rules, including following this policy and any other relevant agreements. If there is any inconsistency between this policy and any other applicable terms, the terms of this policy will prevail;
• report any vulnerability you've discovered promptly;
• avoid violating the privacy of others, disrupting our systems, destroying data and/or harming user experience;
• use only the official channel below to discuss vulnerability information with us;
• provide us a reasonable amount of time to resolve the issue before you disclose it publicly;
• perform testing only on in-scope systems, and respect systems and activities which are out of scope;
• if a vulnerability provides unintended access to data: limit the amount of data you access to the minimum required for effectively demonstrating a proof of concept; and cease testing and submit a report immediately if you encounter any user data during testing, such as personal data, credit card data or proprietary information;
• only interact with test accounts you own or with explicit permission from the account holder. A free organization of your own is the right place to test; and
• do not engage in extortion.

Official channel

Please report security issues by email to [email protected] with "Security" in the subject, providing all relevant information: the affected URL or component, steps to reproduce, and the impact you observed. The more details you provide, the easier it will be for us to triage and fix the issue. Our security.txt lists the same contact.

Safe Harbor

When conducting vulnerability research according to this policy, we consider this research to be:

• authorized concerning any applicable anti-hacking laws, and we will not initiate or support legal action against you for accidental, good-faith violations of this policy;
• authorized concerning any relevant anti-circumvention laws, and we will not bring a claim against you for circumvention of technology controls;
• exempt from restrictions in our Terms of Service and Acceptable use policy that would interfere with conducting security research, and we waive those restrictions on a limited basis; and
• lawful, helpful to the overall security of the Internet, and conducted in good faith.

You are expected, as always, to comply with all applicable laws. If legal action is initiated by a third party against you and you have complied with this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report through the official channel before going any further.

Note that the Safe Harbor applies only to legal claims under the control of SunDevs, and that this policy does not bind independent third parties.

We don't run a paid bug bounty at the moment.