Privacy Policy

This Privacy Policy applies to the ViralBatch website, account workspace, Product and media tools, AI-generation service, billing and referral features, and related support interactions. It does not govern independent websites or services you choose to visit.

Depending on how you use ViralBatch, information can include:

• Account and profile information: email address, authentication and account identifiers, display name, profile image URL, account status, confirmation state, and account timestamps. ViralBatch does not store your password in its application database.
• Security and technical information: session and authentication events, administrative multi-factor authentication status where applicable, request paths and IDs, timestamps, IP or network information, browser or device information, error details, security events, and operational logs made available through the application and infrastructure.
• Products, imports, and User Content: Product names and descriptions, source URLs and identifiers, variants and source metadata, imported or uploaded images and clips, primary and reference media, prompts, exact narration scripts, brand materials, and related media metadata.
• Generation and Library information: Formula and Product selections, Batch configuration, generation settings, quotes, job and provider-processing status, safe error information, generation history, generated videos and audio, stored-media metadata, and creation timestamps.
• Billing and credit information: Stripe customer, checkout, payment, invoice, and subscription identifiers; purchase amount and status; plan and billing-period information; storage allowance and usage; credit lots, balances, reservations, transactions, expirations, and account history. ViralBatch does not store full payment-card numbers in its application database.
• Referral information: referral codes, the referrer and referred-account relationship, signup attribution, qualifying purchase type and payment reference, qualification status, and referral reward and credit ledger records.
• Support and administrative information: support messages and the account, transaction, referral, generation, audit, or technical details needed to investigate a request, security event, or service issue.

We receive information from you when you register, confirm or recover an account, update your profile, create a Product, upload media, provide a prompt, script, reference, or URL, request a Product import, configure a Batch, start a generation, enter a referral code, make a purchase, manage a subscription, or contact support.

We also receive information from authentication, payment, Product- import, AI and media-generation, hosting, storage, analytics, and security providers when they perform requested or operational services.

ViralBatch uses information to:

• create, authenticate, secure, and manage accounts;
• store and organize Products, Batches, and private media;
• import requested Product information and persist selected media;
• process prompts, Formulas, narration, reference media, and requested AI videos;
• store completed media and provide history and Library access;
• calculate quotes and administer credit reservations, settlement, releases, balances, and history;
• process purchases, subscriptions, and billing events;
• attribute, qualify, display, and audit referrals;
• provide support and authorized administrative operations;
• prevent fraud, misuse, and unauthorized access;
• diagnose errors, monitor reliability, secure, maintain, and improve the service;
• enforce the Terms; and
• comply with applicable legal obligations.

ViralBatch uses service providers to operate the service. Current repository and deployment configuration support the following providers and roles:

• Supabase provides authentication and the hosted database. It processes account identifiers, authentication and confirmation information, and application records stored in the database.
• Vercel hosts the Web application and provides cookie-free Web Analytics for aggregate site usage.
• Google Cloud hosts API and background-worker compute that processes requests, job state, and generation workflows.
• Cloudflare R2 stores private uploaded, imported, reference, and generated media.
• Stripe provides hosted payment, subscription, invoice, and billing- portal services.
• CometAPI provides access to active AI and media-generation workloads, including Seedance video generation and Gemini analysis where a feature requires it.
• ScrapeCreators retrieves requested public TikTok Shop showcase and Product data.

ViralBatch also uses managed queue, logging, security, and network infrastructure. Providers receive information needed for their role and handle it under their own applicable terms and policies. This Policy does not promise that an external provider has zero retention or make an unverified statement about provider model training.

Content necessary for a requested AI workflow may be transmitted to AI and media-generation service providers. Depending on the feature, this can include Product images, reference images or video, prompts, Formula-derived instructions, generation settings, Product context, and an exact narration script.

ViralBatch currently routes supported Seedance and Gemini workloads through CometAPI. This does not mean that ViralBatch sends customer data directly to the companies behind those model families. The service stores the job state and the validated results needed to provide the feature, which can include generated media, bounded analysis results, prompts derived for a job, safe error information, and provider request metadata.

When you request a supported Product import, ViralBatch may send a public creator handle, Product URL, or Product identifier to the Product-import provider and receive public Product metadata, variants, source identifiers, and image locations. Selected images are validated and copied to ViralBatch's private media storage.

Source URLs and bounded source metadata may be retained for provenance and re-import behavior. Temporary signed media URLs are generated when needed and are not used as permanent media identity.

Payment transactions use Stripe's hosted Checkout and billing tools. You enter card details and payment credentials on Stripe's payment page rather than into a ViralBatch-hosted card form. Stripe handles full card information under its terms and privacy practices.

ViralBatch receives and retains identifiers and status information needed to connect a Stripe customer, checkout, invoice, payment, or subscription to the correct account; grant credits exactly once; show billing state; and process signed billing events. ViralBatch also retains its own immutable or append-only credit, reservation, entitlement, purchase, and transaction records.

ViralBatch processes referral codes, immutable signup attribution, the referrer and referred-account relationship, qualifying payment identity and status, and each credit reward. A referrer sees only a masked identifier for referred accounts, not the full referred-user email.

Authorized support administrators may access referral, user, generation, transaction, and audit information when needed for support, accounting, security, fraud prevention, or service operations. Administrative business access requires verified role authorization and multi-factor assurance.

Information may be disclosed to the service providers described above; when you direct an integration, import, hosted checkout, or AI workflow; to comply with law or valid legal process; to protect rights, safety, security, and ViralBatch; or as part of a business transaction where permitted by law and subject to appropriate safeguards.

ViralBatch's current product does not use customer information for third-party behavioral advertising or exchange personal information for money. Service-provider processing needed to operate ViralBatch is not described in this Policy as a sale. Legal definitions of “sale” or “sharing” can differ by location.

ViralBatch uses secure cookies for authentication and session refresh. The Web application uses limited local browser storage for core workflow continuity, such as remembering the current Composer generation. Blocking required storage may prevent login or other authenticated features from working correctly.

ViralBatch uses Vercel Web Analytics to understand aggregate visits, page views, referrers, general location, and browser or device type. This privacy-oriented analytics service does not use cookies for Web Analytics. The current application does not use advertising trackers.

ViralBatch retains information for as long as reasonably necessary to provide the service, maintain account and media access, preserve billing and credit integrity, administer referrals, support users, resolve disputes, prevent fraud, secure the service, and comply with applicable legal obligations. Retention varies by data type and operational need; there is no fixed universal retention period.

Products and media can be archived or deleted through available product controls, but generated-media history, billing records, append-only credit ledgers, subscription entitlements, referral records, provider-attempt evidence, audit records, and security logs may need to remain longer for integrity, accounting, legal, fraud- prevention, or dispute purposes. Deletion may not immediately remove information from backups.

ViralBatch does not currently provide a self-service account- deletion control. You may contact support to request access, correction, or deletion. We may need to verify your identity and may retain or de-identify information where permitted or required for billing, ledger integrity, referrals, fraud prevention, security, disputes, or legal obligations.

Depending on where you live, applicable law may give you rights to request access, correction, deletion, portability, objection, or restriction concerning personal information. Rights and exceptions differ by location; this Policy does not claim that every right or privacy law applies identically everywhere.

ViralBatch uses safeguards appropriate to the service, including authenticated sessions, owner-scoped authorization, separated staging and production environments, private media storage, time-limited signed media access, server-side secrets, restricted administrative access, and administrator multi-factor authentication. No system or transmission method is completely secure, so absolute security cannot be guaranteed.

ViralBatch is intended for users who are legally able to agree to the Terms. If you believe a child has provided personal information without appropriate authorization, contact us so the circumstances can be reviewed.

ViralBatch and its providers may process information in countries other than the country where you live. Those locations may have different data-protection laws. ViralBatch does not state in this Policy that all information is stored or processed in one particular country.

We may update this Policy as ViralBatch or legal requirements change. The effective date at the top identifies the current version. We will provide additional notice of material changes when required; this does not promise individual email for every update.

Privacy questions and requests can be sent to support@viralbatch.io. For general product help, visit the Support page.