Secure infrastructure
MoviePrepper’s production architecture is designed for Microsoft Azure App Service, Azure SQL Database, and Azure Blob Storage. The API enforces HTTPS in production and applies HSTS and defensive browser headers.
Security & Reliability
Production work deserves careful protection
MoviePrepper uses authenticated access, project-scoped permissions, private file storage, and monitored infrastructure to help keep scripts, schedules, budgets, contacts, and production media with the people who are meant to work with them.
- Authenticated by default
- Project-scoped access
- Private production files
Practical controls
Security built into the production workflow
Security is more than a login screen. MoviePrepper applies access checks at the API, project, module, record, and file boundaries, while operational checks watch the services the application depends on. The controls below describe what is implemented today without making unsupported compliance or uptime claims.
How work is protected
Controls across accounts, projects, files, and payments
Private project workspaces
API access is authenticated by default. Project membership, write access, workspace state, and feature-level permissions are checked before protected project work is returned or changed.
Project separation
Project ownership is enforced across request validation, application mapping, database filtering, and save checks. These layers are designed to stop one project’s identifiers from selecting another project’s records.
Private production files
Managed files are stored in a non-public blob container. Authorized reads use project-validated, database-backed references and short-lived, read-only links instead of permanent public media URLs.
Account security
MoviePrepper uses ASP.NET Core Identity password hashing and policy enforcement, unique email accounts, failed-login lockout, validated signed sessions, password recovery, and session invalidation after security changes.
Secure payments
Card checkout is handled by Stripe’s hosted Checkout flow. MoviePrepper receives the transaction state needed to activate a project, while full card numbers are not stored on MoviePrepper servers.
Reliability and recovery
Readiness checks cover the application, database, storage, and required configuration. Request and error telemetry supports diagnosis. Backup retention and restore readiness are verified in the hosted Azure environment, where those operational settings are controlled.
Responsible development
Release checks include builds, automated tests, secret scanning, dependency vulnerability audits, SEO checks, and production-package validation. Security-sensitive project and file boundaries have dedicated regression tests.
Your production content
Your work remains yours
You retain ownership of the scripts, schedules, budgets, call sheets, contacts, media, and other production material you upload or create. MoviePrepper uses that content to provide and support the service, as described in our Privacy Policy and Terms of Service.
Portable production records
Take essential documents with you
MoviePrepper can generate downloadable production documents across the workflow, including schedules, call sheets, sides, breakdowns, budgets, reports, and shot-list spreadsheets. Available outputs depend on the module and the records prepared in the project.
Questions or concerns
Talk to the people behind MoviePrepper
If you have a security question, believe you found a vulnerability, or need help with access to production work, contact us with enough detail to investigate safely. Please do not include passwords, payment card data, or other secrets in your message.