We secure our platform
with the same tools we give you.
Spoorder is a security product. We hold ourselves to a high standard and run our own platform through our own scanning toolchain.
Security controls
Encryption in transit
All traffic is served over HTTPS. HSTS is set with a one-year max-age and includeSubDomains.
Encryption at rest
Database encrypted at rest. Sensitive fields such as TOTP secrets and integration credentials are additionally encrypted with AES-256-GCM before storage. API keys are stored only as SHA-256 hashes.
Authentication & 2FA
Passwords stored as bcrypt hashes (cost 12). TOTP multi-factor authentication available to all users. Session tokens are random values held in HTTP-only, Secure, SameSite=Lax cookies; only a hash of the token is kept in the database. Sessions expire after 8 hours.
Infrastructure
Hosted on Railway with a PostgreSQL database on a private network. No database port exposed to the internet. Cloudflare DDoS protection and WAF at the edge. Internal services isolated on a private network.
Access control
Multi-tenant isolation is enforced at the database query level with organisation-scoped filtering. Role-based access control applies across the API. Audit log entries cannot be edited and are retained for 730 days by default.
Vulnerability management
We run Spoorder's own DAST and SCA engines against our application on every deploy. Dependency vulnerabilities monitored continuously and triaged weekly. Critical/High findings patched within 14/30 days.
Responsible Disclosure Policy
We appreciate the security community's efforts to keep Spoorder safe. If you discover a vulnerability, please report it responsibly. We commit to responding quickly and treating all reports with respect.
In Scope
- ✓ *.spoorder.com (all subdomains)
- ✓ app.spoorder.com (main platform)
- ✓ trust.spoorder.com (Trust Centre)
- ✓ app.spoorder.com/api/v1 (REST API)
- ✓ Spoorder CLI (sprdr) binary
Out of Scope
- ✗ Third-party services and infrastructure
- ✗ Social engineering or phishing attacks
- ✗ Physical security attacks on hardware
- ✗ Denial of service (DoS / DDoS)
- ✗ Issues requiring physical access to devices
- ✗ Automated scanner results without proof of impact
Response Timeline
Safe Harbour
We will not pursue legal action against security researchers who: follow this policy in good faith, make every effort to avoid privacy violations and data destruction, do not access data beyond what is necessary to demonstrate the vulnerability, and report findings to us before public disclosure. We ask that you give us reasonable time to address the issue before any public disclosure.
Found a vulnerability?
Send your report to security@spoorder.com. Please include:
- Affected URL or component
- Vulnerability type (e.g. XSS, IDOR, SQLi, SSRF)
- Step-by-step reproduction instructions
- Screenshots or video where applicable
- Your assessment of potential impact
Hall of Fame
We publicly acknowledge researchers who report valid, in-scope vulnerabilities (with their permission). We do not currently offer a monetary bug bounty programme, but we provide written acknowledgement and Hall of Fame recognition.
Machine-readable policy at /.well-known/security.txt
Security enquiries: security@spoorder.com