Security Overview & Scope Disclosure
VidSynth is engineered with strict separation between public client code and privileged backend operations. In accordance with our transparency rules, we document only the security controls implemented in this codebase and do not claim unverified third-party compliance certifications (such as SOC 2, ISO 27001, or formal GDPR certification).
All PostgreSQL tables (`profiles`, `projects`, `render_jobs`, `credit_ledger`) enforce `auth.uid() = user_id` policies in `001_initial_schema.sql` so tenants can never query or mutate another user's records.
Browser JavaScript uses only the public Supabase `anon` key combined with user JWT sessions. Privileged `service_role` keys are strictly prohibited from frontend bundles.
Data Processing for Source Videos, Generated Content & Accounts
1. Uploaded Source Plates & Conditioning Inputs: Source footage, depth maps, and segmentation masks configured within a Studio project are scoped strictly to the owning account ID. Customer media is processed solely to execute requested conditioning passes and is never used to train shared foundation models without explicit written authorization.
2. Synthesized Video & Multi-Pass Outputs: Generated MP4, WebM, ProRes, and 16-bit OpenEXR sequences are associated with the user's project record. When a project is deleted via the Studio Dashboard, its project metadata record is removed immediately.
3. Account & Telemetry Records: Account profiles store full name, email address, organization name, and credit ledger history required for session authentication and usage accounting.
Privacy Policy
VidSynth collects only the information you explicitly provide when registering an account, configuring a project, or submitting an Early Access inquiry (`full_name`, `work_email`, `company`, `use_case`).
In Local Sandbox Mode, account and project records are stored exclusively inside your browser's `localStorage` and are never transmitted to third-party analytics trackers. When connected to a configured Supabase instance, data is stored in your designated PostgreSQL database under RLS protection.
Terms of Service
Acceptable Use & Authorized Likeness: Users must hold appropriate rights, licenses, and performer consent for any source footage or likeness submitted for character transformation or identity conditioning. Creating deceptive non-consensual likenesses is strictly prohibited.
Output Ownership: Subject to compliance with these Terms, you retain all rights, title, and interest in your original source media and the conditioned output sequences generated within your workspace.
Pipeline Documentation & Database Schema Reference
- ArrowLeft / ArrowRight : Adjust A/B split divider by 2% increments
- Shift + ArrowLeft / ArrowRight : Adjust A/B split divider by 10% increments
- -1F / +1F Buttons : Step synchronized plates by 1 frame (1/24s = 41.67ms)
- public.profiles : User identity, organization, plan_tier, available_credits
- public.projects : Studio conditioning projects with transformation_mode & model_id
- public.render_jobs : Auditable execution & simulation telemetry logs
- public.credit_ledger : Immutable credit grants and pass deductions
- public.early_access_leads : Validated cohort registration leads
Contact & Technical Support
In compliance with our data integrity rules, we do not publish fabricated office street addresses or fictional support phone numbers. For direct founder and executive inquiries, reach out via our official configured address, or use our validated registration flow: