This describes the current development setup. A public privacy policy needs review before Befosync launches.
Uploaded videos, original audio, transcription caches and exports are stored in the installation's configured private object storage. Project settings, edit plans and transcripts are stored in its MySQL database. Local development may instead keep media on the machine running Docker.
In production, authenticated Modal jobs run speech recognition, pause and repeated-take analysis, optional face retouch, and FFmpeg rendering. Modal receives temporary signed download and upload URLs; the long-lived object-storage credentials remain with Befosync. The first job can download model files and later jobs reuse a private model cache.
Sign-in uses Befosync's dedicated Keycloak setup. Configured billing, email, support and analytics integrations are retained and may contact their providers. PostHog page analytics may run when configured; DOM autocapture and session recording are disabled in the app.
There is no automatic clip-deletion schedule in this preview. Originals remain after an edit, and re-edits create additional export files. Protect access to the Befosync account and deployment, and review this draft policy before uploading sensitive material.