Last updated: 24 May 2026
This is a practical website policy draft for Ninth Theory MXF Viewer. It should be reviewed before public launch, especially before accepting client uploads, payments, analytics, or production Google/Dropbox access.
1. Current protection model
The current version is a local development MVP. Media files, Google tokens, job files, and preview outputs are stored on the machine running the app.
2. Google Drive
Google Drive access uses OAuth and read-only Drive permissions. The app is designed to import only files selected by the user.
3. Review links
Review links use generated tokens and password checks. For production, review links should include expiry dates, signed media URLs, rate limiting, stronger password hashing, and access logging.
4. Recommended production security
- Use proper user authentication before accessing cloud imports or media jobs.
- Store OAuth tokens encrypted in a database or secure secret storage.
- Store source files and previews in private object storage such as S3/R2/Supabase Storage.
- Use signed URLs for previews and downloads.
- Add automatic deletion/retention rules for uploaded and generated media.
- Add rate limiting for uploads, imports, review unlocks, and transcode jobs.
- Use bcrypt or Argon2 for review passwords instead of simple hashing.
- Separate FFmpeg processing onto a dedicated worker/server.
5. Reporting security issues
Please report security concerns to mark@initialone.co.uk with the subject line “Ninth Theory MXF Viewer Security”.