How imagicv handles your data.

We do not want a generic policy here. This page explains what this project stores, which providers are involved, how private-first rendering works, and what happens when you publish or delete a job.

What data the product actually collects.

imagicv is an account-based video stylization product, so the information we collect is mostly the information required to authenticate you, run a render, store the result, and show it back inside your account.

• Account data: your Firebase user ID, email address, display name, profile photo URL, account timestamps, credit balance, and trial-usage counters.
• Creation data: uploaded source video files, file paths, selected style or custom prompt, title, render status, timestamps, provider task IDs, finished output URLs, and cover image URLs.
• Billing data: Stripe checkout session and payment status records, purchased credit amounts, and the account that received those credits. Full payment card details are handled by Stripe rather than stored by us.
• Operational data: limited technical information needed to keep the service running, such as authentication state, storage references, request context, and analytics signals made available through configured platform tooling.

Why we use that information.

The data we keep is tied to concrete product behavior rather than broad secondary uses.

• To create and secure your imagicv account, let you sign in with email/password or Google, and keep your profile and credits attached to the right user.
• To upload source media, start rendering jobs, poll job progress, save finished outputs, generate cover images, and display render history in the profile area.
• To support optional gallery publication, including showing the output, title, display name, and profile photo associated with a work you explicitly publish.
• To operate billing, reconcile credit top-ups, detect failures or abuse, and troubleshoot processing problems across the rendering pipeline.

How your data moves through third-party infrastructure.

imagicv depends on cloud providers for authentication, storage, rendering, and payments. Those providers only receive the information needed for the part of the workflow they handle.

• Firebase is used for authentication, database records, cloud storage, server functions, and analytics tooling. That means account records, job metadata, uploads, outputs, covers, and credit records are stored in Firebase services.
• When you start a render, the app sends the source video URL and the selected style or prompt into the external rendering workflow used by this project. The finished file is later fetched back from the provider response and stored under your account.
• Payments are handled through Stripe checkout. We receive payment status and purchased-credit information, but Stripe processes the payment instrument itself.
• Security checks such as Firebase App Check or related Google verification tooling may be used where enabled to protect sensitive actions like rendering, checkout, publication, or deletion.

Private in the product does not mean every file URL is secret forever.

The application keeps new renders out of the public gallery by default, but file sharing still has practical consequences.

• A newly finished render is stored as a private account item unless you switch it to public visibility from your profile.
• If you publish a work, the system creates or updates a public gallery record containing the output, cover, title, and the display name and profile photo tied to your account.
• Rendered video and cover files are stored as cloud download URLs. Anyone who obtains one of those direct file URLs may be able to access that file, even if the work is not listed in the public gallery.
• We may also share data with service providers acting on our behalf or when required by law, security process, or to protect the service and its users.

How long information stays, and what deletion does.

Retention in this product is mostly driven by whether the account or render still needs to exist for the user-facing workflow.

• Account profile and job records remain available while the account is active unless they are removed through product actions, administrative cleanup, or a support-handled request.
• When you delete a completed or failed render from the profile page, the system attempts to delete the related source upload, rendered output, cover image, and public gallery entry tied to that job.
• Payment and credit records may be retained longer than media files where needed for accounting, fraud prevention, dispute handling, or legal compliance.
• If you need help with a broader deletion request that is not available directly in the interface, contact [email protected].

What you can control inside the current product.

The current build already gives users meaningful control over visibility and stored work product.

• You can choose whether to sign in, which sign-in method to use, and whether to continue using the service at all.
• You can edit your display name, keep renders private, publish a render to the gallery, unpublish it later, or delete eligible renders entirely.
• You can decide whether to upload source footage, what title or prompt to attach to a job, and whether to purchase credits through checkout.
• If you have questions about a specific privacy scenario, you can reach support directly at [email protected].