Security at ParcelPilot

We take security seriously and appreciate the security research community’s efforts in keeping our platform safe.

Responsible Disclosure

If you believe you’ve found a security vulnerability in ParcelPilot, please let us know. We appreciate your help in keeping our users safe.

What to Include in Your Report

• Description: Detailed description of the vulnerability
• Steps to Reproduce: Clear, step-by-step instructions to reproduce the issue
• Impact: Your assessment of the vulnerability’s potential impact
• Affected Components: URLs, API endpoints, or features affected
• Evidence: Screenshots, videos, or POC code (if applicable)

Our Response Timeline

Safe Harbor

ParcelPilot supports safe harbor for security researchers who:

• Make a good faith effort to avoid privacy violations and data destruction
• Do not exploit a security issue for personal gain
• Report vulnerabilities promptly
• Keep vulnerability details confidential until we’ve resolved it

If you follow these guidelines, we will not pursue legal action against you for security research activities.

Out of Scope

The following issues are generally considered out of scope:

• Denial of Service (DoS) attacks
• Social engineering or phishing
• Physical testing against ParcelPilot property or offices
• Reports from automated scanners without validation
• Missing security headers without demonstrable impact
• SSL/TLS configuration issues on third-party services we don’t control

Our Security Measures

Questions? Contact us at security@parcelpilot.com