Agnes Video GeneratorLocal drafts
This privacy policy distinguishes preparing a scene from submitting one. The studio keeps your text prompt, mode and selected settings in local browser storage so they can survive navigation to sign in. The privacy policy does not describe that draft as an account backup. Anyone with access to the same browser profile may be able to read it. Under this privacy policy, use the Clear draft control when you finish on a shared device.
Selected photographs
The privacy policy treats a selected image differently from a text draft. During preparation, a temporary browser object URL displays the file locally. The image itself is not saved in local storage, and leaving the studio may require selecting it again. This privacy policy does not claim a local preview has been uploaded or moderated. When live uploads open, this privacy policy requires a separate authenticated, size-limited and content-reviewed submission before provider processing.
Future account information
This privacy policy covers account information only when an identity service has actually been connected. Email addresses and profile information would support authentication, account recovery and project ownership. The privacy policy does not imply that a submitted form currently creates an account. Passwords must be handled by the configured identity service rather than written into project records. Before activation, this privacy policy requires the operator to publish the identity processor and the applicable retention and recovery practices.
Generation instructions
The privacy policy asks you to keep sensitive personal details out of prompts. A live video request would require processing the scene description, settings and any approved source image to perform the requested task. The privacy policy does not authorize using those materials for unrelated purposes. Provider-specific handling and model training terms must be reviewed before service activation. Until then, this privacy policy makes no claim that a particular external provider has accepted your content or agreed to a retention commitment.
Project records
This privacy policy anticipates private job records containing ownership, request parameters, status, timestamps and result references. These records support progress checks, failure recovery and credit reconciliation. The privacy policy favors private access rather than public project listings. An authenticated user should only receive their own records. Under this privacy policy, public scene illustrations remain distinct from private user projects, and a share button for a public page must not silently publish a user image or generation.
Storage and retention
The privacy policy does not promise a deletion interval that has not been implemented. Before live processing, the operator must set retention schedules for inputs, outputs, account records and financial audit entries. This privacy policy requires those schedules to reflect actual service behavior. Private media should use restricted object access and expiring links. Under this privacy policy, expired access links are not a substitute for deleting the underlying object when its retention period ends.
Payments and balances
This privacy policy separates credit accounting from card handling. The website reserves a checkout connection to an existing billing service and does not currently collect card information. The privacy policy anticipates storing verified transaction identifiers and credit changes to reconcile purchases. A browser redirect must not become payment proof. Under this privacy policy, financial records may need a different retention period from creative drafts, which must be explained when verified paid creation opens.
Operational requests
The privacy policy allows the minimum technical processing needed to deliver pages, prevent abuse and investigate service failures. Server requests may expose network information to the hosting operator. The privacy policy does not currently advertise a configured analytics account or optional marketing tracking. Any later tracking integration requires an updated disclosure. Under this privacy policy, operational logs should avoid unnecessary prompts, source images, authentication secrets and complete private result URLs.
Your choices
This privacy policy gives browser users a practical first action: remove the saved draft from the studio and clear site storage when appropriate. A future account service must provide a way to request access, correction or deletion through a verified support route. The privacy policy does not claim to fulfill account requests before identity verification exists. If you believe content was exposed improperly, follow the contact page. The privacy policy will be updated before a live data workflow materially changes.
Read before uploading
The privacy policy is a description of the current preparation interface and the requirements for future service activation. Do not submit confidential material through an unverified contact route. This privacy policy does not name an unavailable support mailbox or an unconfigured processor as operational. The studio is an independent third-party service. Review the privacy policy again before using live generation, and check the terms and disclaimer for content permissions and the current limits of service availability.