Legal
Security
Current security posture, reporting channel, and explicit limits on assurance claims.
Version 2026-09-11-v1Effective 11 September 2026
Contents · 3 sections
1. Controls
- Application-enforced tenant and workspace membership boundaries for direct server database access.
- Private storage and authenticated downloads for sensitive material, with stronger file lifecycle work required before paid launch.
- Encryption in transit and provider encryption at rest; designated critical fields require application encryption.
- Rate limits, signed/revocable external links, immutable financial approvals, optimistic concurrency, dependency scanning, and checksummed migrations.
- Structured security logging with sensitive-key redaction; live alert-provider completion remains a launch gate.
2. Reporting
Report a suspected vulnerability or security incident privately to support@tourganise.com. Include affected URL, impact, reproduction steps, and safe contact details. Do not access other customers' data or disrupt service.
3. Assurance limits
Tourganise does not currently claim SOC 2, ISO 27001, PCI certification, independent penetration-test certification, WCAG conformance, or guaranteed security. Stripe handles card data when billing is enabled; Tourganise must not store raw card numbers.