Understanding the Data Lifecycle: Browser Uploads vs. Cloud Processing
When using an online video generator, personal images move through several distinct computing environments. Understanding where your images travel—and where they reside—is the foundation of digital privacy.
- Client-side preparation: When you select photos in your web browser, the files initially reside on your local device. Selecting a file is different from submitting it. Check when the particular service uploads it; do not generalize that every AI tool must run remotely.
- Encrypted transit and server ingestion: Uploading transmits your images over encrypted HTTPS connections to cloud storage. Claiming that media is private does not mean it never leaves your browser; a cloud generation workflow may transfer files to its processing providers.
- Account-authenticated isolation: Under our documented privacy policy, uploaded portraits and generated outputs are private, meaning access is restricted to the owning account holder who holds a valid login session. These account controls are intended to prevent public access; do not publish private links or assume a privacy label alone proves implementation.
- Service provider handling: Private account access isolates your files from other users, but cloud infrastructure providers and backend services still process the raw media during generation. Documented terms govern whether intermediate frames or source images are retained for service maintenance or purged after delivery.
Pre-Upload Verification Checklist: Five Privacy Safeguards
Before submitting any portrait to a synthesis platform, work through these five practical verification checks:
- Verify explicit consent and adult eligibility: Automated dance generators animate expressive movements across bodily frames. In the NEON DUO architecture, generating a duo choreography requires two separate consenting adult photos, as detailed in our neon dance workflow guide. Never upload photos of friends, colleagues, or acquaintances without their direct knowledge and documented agreement.
- Confirm authenticated access controls: Ensure that the platform stores your source files and resulting video clips behind account-level credentials. Curated preview clips displayed on public pages represent fixed reference animations rather than user uploads. Your personal media should never appear in a public gallery without explicit opt-in.
- Inspect cloud processing and service boundaries: Distinguish between local file privacy and backend processing. When source images are transferred to remote GPUs, check whether third-party model providers process the data. Platforms should clearly state their architectural boundaries rather than implying that automated generation happens entirely offline.
- Examine data retention and training commitments: Review the platform's privacy policy to see if source photos are deleted after task completion or retained for model fine-tuning. Never assume automatic zero-retention unless explicitly specified in governing policy text. Do not infer a retention period or training exclusion that the policy does not state.
- Review usage rights and commercial terms: Synthesizing an animation does not automatically grant universal commercial exploitation rights. Consult the terms of service to understand copyright scope, licensing limitations, and soundtrack restrictions before publishing clips across social networks.
Worked Hypothetical Scenario: Auditing a Two-Photo Dance Project
To understand how privacy safeguards function during a real project, consider this worked hypothetical scenario.
Suppose a creator plans to produce a planned 15-second H.264 MP4 dance video featuring two adults. The creator prepares two portrait files: an illustrative 4.2 MB JPG for dancer A and an illustrative 6.8 MB PNG for dancer B, both well under the platform's 10 MB per-file threshold.
- Phase 1: Pre-upload likeness audit: The creator confirms that both adults are over 18 and have explicitly consented to their likenesses being animated in a stylized dance routine. The creator inspects each image to ensure no unintentional private information—such as visible employer ID badges, house numbers, or family photographs in the background—is present.
- Phase 2: Verifying data handling: Before transmitting the files, the creator confirms that generation requires an authenticated account. The creator recognizes that private access restricts the files from public view, but understands that the images will be transmitted to secure cloud processors for rendering.
- Phase 3: Post-processing verification: In the intended workflow, soundtrack processing finishes before the completion notification, and the silent version is retained. The creator verifies that the output requires an active login session to stream or download. If an unauthenticated browser attempts to open the asset URL, access is denied.
Distinguishing Photo Composition from Privacy Protection
Technical photo preparation and privacy safeguards serve two distinct purposes. As explained in our companion photo preparation guide, lighting and framing help make the source appearance visible for comparison.
However, visual quality does not equal data privacy:
- A high-resolution, well-lit portrait provides clear facial features for dance mapping, but it also contains rich personal biometric information.
- Cropping can remove visible personal surroundings from the copy you upload; inspect the saved copy and its metadata as well.
- Choosing solid, neutral attire helps visual clarity, but ethical consent remains the non-negotiable safeguard regardless of photo clarity.
Technical image adjustments should always accompany, rather than replace, a thorough privacy check.
Frequently asked questions
Does a 'private' setting mean my photos never leave my device?
No. Private access and local processing are different claims. This site uses a cloud workflow with owner-authenticated media access. Read the policy for processing and retention details rather than assuming your files stay only in the browser.
Can I upload portraits of friends or public figures without permission?
No. NEON DUO requires consenting adults. Legal requirements vary by location and use; this checklist does not provide a universal legal determination. NEON DUO's planned workflow requires two separate consenting adult photos. Uploading images of non-consenting individuals, minors, or unauthorized public figures violates platform terms and basic privacy ethics.
What happens to uploaded portraits after the video is generated?
File handling depends on published provider terms. On NEON DUO, access to private uploads and completed outputs requires logging into the owning account under our privacy policy. In the event of a confirmed generation failure, reserved credits are released, but source image retention is governed strictly by platform policy rather than undocumented automatic purge timers.
Do I automatically own all commercial rights to generated dance clips?
Not necessarily. Commercial usage requires checking the people, source material, music and the platform's terms of service. While users retain their personal likeness rights, platforms often apply specific licensing conditions to synthetic outputs, model weights, and integrated background soundtracks. Always check platform licensing before deploying videos commercially.
Next steps: Preparing photos and reviewing standards
Evaluating privacy practices before uploading portraits helps you understand how likenesses will be handled while establishing clear expectations around cloud processing. While live AI generation and credit purchases remain closed on NEON DUO, you can explore our system architecture on the dance project overview and consult our library of technical guides. If you plan to create dual-dancer choreography in the future, review our photo preparation guide to learn how to prepare two separate, consenting adult photos in JPG, PNG, or WebP format up to 10 MB each.