1. Desktop-first architecture

vEdition is presented as desktop software for Windows. Screen video, local session files, generated media, and project assets are processed on the customer device during normal operation.

2. Local project data

The product workflow is intentionally structured so that capture output, step timing, render files, and local session artifacts remain under customer control unless the customer independently exports or shares them.

3. AI-related data handling

AI-enabled features may transmit textual prompts, step descriptions, and narration content to the customer-selected AI provider. The current commercial model assumes customer-supplied API credentials and customer-paid AI usage.

4. Dependency model

The workflow may rely on third-party dependencies such as FFmpeg and external AI providers. Availability, performance, and compliance of those external components remain subject to their own providers and the customer’s deployment choices.

5. Operational safeguards

Reasonable safeguards should include controlled access to operator email and billing systems, credential rotation, least-privilege access, secure handling of support materials, and timely updates to the website and business tooling.

6. Customer responsibilities

Customers remain responsible for endpoint security, lawful source data handling, secure storage of local project files, secure management of their AI credentials, and review of any third-party integrations used in their workflow.

7. Security contact

Security-related and privacy-related communications may be directed to admin@vedition.pro unless a dedicated security mailbox is published later.

8. Important limitation

This page is a high-level public overview, not a certification statement and not a substitute for a signed security addendum, detailed questionnaire response, or formal audit report.