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. Who we are
Ninth Theory MXF Viewer is a media utility created by Ninth Theory to help users upload, import, preview, and share MXF video files through a browser friendly workflow.
Contact: mark@initialone.co.uk. Instagram: @NinthTheory.
2. Information we may process
- Media files you upload locally, including MXF source files and generated preview files.
- Google Drive file metadata when you connect Google Drive, including file name, file ID, size, modified date, parent folder information, and Drive open link.
- Google OAuth tokens stored locally during development so the app can list and import your Drive files.
- Generated job data, including job ID, file name, file size, status, progress, selected quality, rotation, and preview path.
- Password protected review link data, including a share token and password hash.
- Technical information generated by FFmpeg/FFprobe, such as codec, duration, resolution, and preview progress.
3. Why we use this information
- To upload or import selected MXF files.
- To generate browser playable previews such as MP4/HLS.
- To show job history and progress.
- To provide client review links where enabled.
- To let you download generated preview files.
- To troubleshoot errors and improve the workflow.
4. Google Drive access
When Google Drive is connected, the app requests read-only Drive access. The app is designed to list MXF files, show file metadata and folder paths, and import only the file you choose. It should not alter, delete, or write to your Google Drive files.
Google Drive tokens are stored locally in this development version under the project storage folder. A production version should store tokens securely using encrypted storage and authenticated user accounts.
5. File storage and retention
In the current local MVP, uploaded/imported files and generated previews are stored on the machine running the app inside the local project storage folder. You can remove jobs from the History page or manually clear the storage folder.
A production version should define a clear retention period, for example automatically deleting uploaded media and generated previews after a fixed number of days unless the user chooses to keep them.
6. Sharing
If you create a client review link, anyone with the link and password may be able to access the generated preview. Do not share review links publicly unless you are happy for the preview to be viewed by the people who receive it.
7. Your rights
Depending on how the app is deployed and your location, you may have rights to access, correct, delete, restrict, object to, or request a copy of personal data processed about you. You can contact mark@initialone.co.uk for privacy requests.
8. Production note
This local development version is not yet a final hosted service. Before a public production launch, Ninth Theory should add account authentication, encrypted token storage, defined retention periods, signed media URLs, audit logging, and a reviewed legal notice.