Founding beta
Security & Data
Masterplan is being built with privacy and tenant separation as product requirements, not an afterthought. This page describes the current founding-beta position and should be kept current as infrastructure changes.
Current controls
- Individual authenticated accounts; no shared customer admin password.
- Company-scoped memberships and server-side permission checks.
- Access levels separated from real-world job titles.
- Controlled Standard versions and retained training/assessment evidence.
- HTTPS in production and Django CSRF/session protections.
- Private video playback can use signed Cloudflare Stream URLs when configured.
- Privacy requests and incident-response procedures are documented.
Hosting and subprocessors
Masterplan currently uses Railway for its application and PostgreSQL infrastructure. Video uploads may use Cloudflare Stream. Transactional email uses the provider configured for the production service. The founder launch-readiness process requires the intended data region, processor terms and backup arrangements to be checked before external workforce data is accepted.
What customers should avoid in the founding beta
Do not upload special-category personal data, highly confidential HR case material, payment-card data, medical records or accounts for under-18s without prior written agreement and a specific risk assessment.