Vulnerability Disclosure Policy
GrabDocs welcomes reports of security vulnerabilities from researchers and customers. This policy explains how to report issues in good faith and how we respond.
Last updated: November 19, 2026
1. Scope
This policy covers security vulnerabilities in GrabDocs products and services, including:
- https://grabdocs.com (marketing and account site)
- https://app.grabdocs.com (application)
- GrabDocs APIs and related authentication flows tied to those domains
Out of scope: third-party services we do not operate, social engineering of GrabDocs staff or customers, physical attacks, denial-of-service or volumetric flooding, and spam or phishing campaigns.
2. How to report
Email [email protected] with a clear description of the issue. Helpful reports include:
- Affected URL, product area, or API endpoint
- Steps to reproduce
- Impact (what an attacker could do)
- Proof of concept (screenshots, request/response samples without sensitive customer data)
- Your preferred contact method and whether you want acknowledgment by name
Do not access, modify, or exfiltrate data that is not yours. If you encounter personal or customer data while testing, stop and report immediately.
3. Allowed and prohibited testing
Allowed (when done in good faith within scope):
- Testing against accounts you own or are explicitly authorized to test
- Non-destructive probing for authentication, authorization, injection, and similar application flaws
Prohibited:
- Denial of service, resource exhaustion, or intentional degradation of service
- Social engineering, phishing, or physical intrusion
- Accessing or downloading other customers’ data
- Automated scanning that generates excessive traffic
- Public disclosure before we have had a reasonable chance to remediate (see coordinated disclosure below)
4. Safe harbor
GrabDocs will not pursue civil or criminal legal action, or initiate a complaint to law enforcement, against researchers who discover and report security vulnerabilities in good faith and in accordance with this policy.
If legal action is initiated by a third party against you for research conducted under this policy, we will take reasonable steps to make it known that your research was conducted pursuant to this policy. Safe harbor does not apply if your testing intentionally harms GrabDocs, our customers, or exceeds the limits above.
5. Response timelines (triage SLAs)
- Acknowledgment: within 2 business days of receiving a valid report
- Initial assessment / status update: within 5 business days
- Remediation: prioritized by severity; we aim to keep you informed of material progress
This is a disclosure program, not a bug bounty. We may thank researchers publicly on our Security Advisories page when appropriate; we do not currently offer monetary rewards.
6. Coordinated disclosure
Please give us a reasonable opportunity to investigate and fix the issue before public disclosure. Our default expectation is coordinated disclosure after remediation, typically within about 90 days of the report, unless we agree otherwise or a longer timeline is needed for a complex fix.
When a vulnerability warrants public notice, we publish an advisory (and may request a CVE) on our Security Advisories page.
7. How we handle reports
Reports are triaged by severity, fixed according to risk, and closed with feedback to the reporter when contact details are provided. Significant product vulnerabilities may result in a published advisory and, when appropriate, a CVE identifier. Operational details of our internal process are maintained by the GrabDocs security team.
8. Contact
Security team: [email protected]