Privacy Policy

Version: 2026-10-28-r6 · Last updated: October 28, 2026

Top Apps LLC operates Vidifier's website, iPhone, iPad, and Mac applications and related AI services. This policy describes information we process, why we process it, the providers involved, and your choices. Contact support@vidifier.com with privacy questions or requests.

1. Photos, prompts, video, and generated media

When you request a generation or image edit, the selected image and your prompt, style, and generation settings are transmitted from the app to our backend hosted on Render. Our backend sends selected content and instructions to third-party AI model hosting providers for AI inference and content moderation. These providers host AI models or route requests to services involved in generating and checking your results.

For audio generation, we send the relevant video or its provider-hosted URL, prompt, and generation settings to our third-party AI model hosting providers' audio-generation services. Outputs are returned through provider-hosted URLs and downloaded by the app. Selected photos, prompts, and relevant video leave your device. Processing is not entirely on-device. In updated app versions, the creation action links to the Terms of Service and this Privacy Policy before you submit content. Earlier versions may show different notices or controls. The transmissions described here occur when you request generation. Do not upload material that you lack permission to disclose, particularly sensitive information about other people.

We do not use your Inputs or Outputs to train our own AI models. Third-party processing and any provider retention are governed by the applicable service arrangements and provider policies. We do not promise that a provider deletes all copies immediately when generation finishes. We do not publish your private creations to a public Vidifier feed.

2. Other information we process

• Generation and reliability records: prompts, operation and model settings, job and provider identifiers, provider media URLs, status, timing, errors, credit charges or compensation, and related diagnostic events. A provider URL may permit access to its associated media; treat shared URLs as sensitive.
• Installation and purchase identity: app-generated installation/customer identifiers, authentication credentials or their secure verification values, app/OS version, purchase and entitlement status, credit balances, and transaction identifiers. Apple-signed purchase evidence may be processed to verify ownership and associate purchases across devices.
• Agreement records: accepted Terms and Privacy Policy versions and document hashes, confirmation wording, server receipt time, installation identifier, app version, acceptance method, and any recorded withdrawal requests. Eligibility conditions are part of the linked Terms; the current notice does not request a separate age or guardian declaration or a date of birth.
• Support and safety information: information you choose to send us, complaint details, and records reasonably necessary to investigate misuse, protect the Service, resolve disputes, or comply with legal obligations.
• Technical request information: our hosting and service providers may process IP addresses, network/request metadata, and security logs in operating the Service. We do not claim that no information is collected simply because you do not create a named account.

3. Purchases and service providers

Apple distributes the app and handles App Store payments. We do not receive your full payment-card details. RevenueCat processes pseudonymous customer identifiers, purchase receipts and transaction information, subscriptions, entitlements, and credits to provide and verify paid access. Render hosts the backend and database. Third-party AI model hosting providers process selected content for AI inference, media delivery, and moderation as described above. We disclose information needed for these services and for lawful support, safety, and security activities.

Information about our other service providers: Apple, RevenueCat, Render, and PostHog. Their policies describe their own practices; this policy explains Vidifier's use of those services.

4. Basic usage analytics and optional diagnostics

Basic onboarding analytics: In app versions introducing this policy, basic usage analytics is enabled by default from the first onboarding screen unless an existing saved preference disables it. PostHog receives pseudonymous installation/session identifiers, app and OS information, onboarding screen names and order, Continue and Back actions, demo and review-carousel interactions, step timing, background/resume events, onboarding completion, and the initial paywall view. These events help us understand where onboarding is confusing and improve the app. They do not include your photos, videos, prompts, payment credentials, or screen recordings. Our service providers may process technical request information, including IP addresses, to receive these events; we disable PostHog location enrichment for these events.

You can turn off Basic usage analytics through Privacy choices during onboarding or in Settings → Privacy & Legal → Privacy Choices. Turning it off also stops optional diagnostics and session replay. Paid access and generation features do not depend on either setting. We preserve existing saved off preferences, including migrated earlier analytics preferences. Disabling analytics stops future collection; events already received are not automatically deleted. Earlier app versions may have used different controls.

Optional diagnostics and session replay: These stay off until you enable them separately. If enabled, PostHog also receives named app screens, generation-reliability events, and masked session recordings to diagnose problems and improve usability. Replay masks images and text inputs and excludes diagnostic logs and network payloads. Masking reduces exposure but does not guarantee that every incidental detail is removed. You can disable this option while keeping basic onboarding analytics enabled.

Essential purchase verification, legal-acceptance records, security, and backend job/reliability processing operate independently of these settings. This policy does not replace any consent or other requirements that apply to a particular use of information.

Website analytics are separate. Some pages on vidifier.com load PostHog web analytics, which can collect page visits, clicks, browser/device information, IP-related information, and cookie or browser-storage identifiers. Session recording may also operate if enabled in the website configuration. The app's analytics setting does not control website analytics. Browser privacy and storage controls may limit this collection; contact us about your information or available choices. The standalone legal-document pages do not load analytics scripts.

5. Why we use information and when we disclose it

We use information to fulfill generation requests, deliver and recover jobs, maintain local history, verify purchases, manage credits, record agreements, provide support, investigate abuse, secure and operate the Service, improve it where permitted, and satisfy legal duties. Where data-protection law requires a legal basis, we rely as applicable on performing our agreement with you, your consent for the specific processing described in the permission flow, legitimate interests in operating and securing the Service where lawful, and legal obligations. We do not treat acceptance of the Terms as blanket consent to every use of personal information.

We may disclose information to necessary service providers, in response to valid legal process or mandatory reporting duties, to protect rights and safety where law permits, in a business transfer subject to applicable protections, or as you direct. We do not sell personal information or share it for cross-context behavioral advertising. Exporting or sharing a creation sends it to the destination you choose, whose practices may differ.

6. Storage and retention

History, original input copies needed for saved jobs, thumbnails, drafts, pending submissions, and downloaded Outputs are stored locally on your device. Deleting a local item removes it from the app's local history; it does not automatically delete backend records, provider-hosted files, copies you exported, or copies held by recipients. Device backups and operating-system services may have their own retention behavior.

Our database retains operational metadata, including prompts and provider URLs, after a generation completes. Providers may retain uploaded media or Outputs under their own service arrangements. We retain information for as long as reasonably needed for the purposes described here, considering recovery, purchases, fraud prevention, complaints, disputes, legal requirements, and backup cycles. We do not promise immediate deletion after generation or a fixed provider-media lifetime. Contact us to request deletion or details about retention for your information. Some records may need to be retained to comply with law or document purchases and agreements.

7. Your choices and rights

You can choose which media to import, delete local history, and control Photos permissions through your device. In updated app versions, Settings → Privacy & Legal → Privacy Choices lets you turn off basic analytics and decline optional diagnostics and session replay. These versions do not have a separate AI-processing permission switch. You control future AI submissions by choosing whether to request another generation or edit. Stopping new requests does not undo completed processing, stop jobs already submitted, delete existing records, or cancel an App Store subscription. Existing media remains available locally. Use Contact Us in Settings or the email below for privacy requests, including requests about existing server or provider records.

Depending on where you live and applicable legal conditions, you may have rights to access, correct, delete, obtain a copy of, restrict, or object to processing of your personal information, withdraw consent, and complain to your data-protection authority. Send requests to support@vidifier.com. We may ask for proportionate verification, such as your installation or job identifier, to protect information from unauthorized disclosure. We will respond as required by applicable law and explain any lawful reason we cannot fully fulfill a request. We do not require you to send sensitive photos to verify identity.

8. Children and families

Vidifier's minimum age is 4. Users aged 4–17 may use the Service only with a parent or legal guardian's agreement and supervision, and additional local age and consent requirements apply where relevant. The App Store age rating describes content suitability; it does not establish parental consent to personal-information processing. Where applicable law requires parental notice or verifiable consent before collecting, using, or disclosing a child's personal information, those requirements apply separately from accepting the Terms. The app does not currently collect a date of birth or provide a dedicated verifiable parental-consent flow. If you believe a child's information has been processed without legally required authorization, contact support@vidifier.com so we can investigate and take appropriate action, including deletion where required.

9. Security and international processing

We use encrypted network connections and access controls intended to protect information. No service can guarantee absolute security. Avoid sharing credentials or private provider URLs. Our providers may process data in the United States and other countries with different data-protection laws. Applicable transfer requirements and safeguards must be observed; contact us with questions about processing locations or available safeguards.

10. Changes and contact

We will date revised policies and provide notice of material changes through the app or other appropriate means. When required, we will request new permission before new processing. Changes do not retroactively expand consent already given.

Top Apps LLC · Vidifier
support@vidifier.com
vidifier.com/support.html