Privacy Policy
Our commitment to protecting your privacy and personal data
2026/10/28
Introduction
Welcome to our Privacy Policy. This document explains how we collect, use, and protect your personal information when you use our services.
Information We Collect
We may collect the following types of information:
- Personal Information: Name, email address, and contact details you provide when registering or contacting us.
- Usage Data: Information about how you interact with our website, including pages visited and time spent.
- Device Information: Details about the device you use to access our services, such as IP address, browser type, and operating system.
How We Use Your Information
We use your information for the following purposes:
- To provide and maintain our services
- To notify you about changes to our services
- To provide customer support
- To gather analysis or valuable information to improve our services
- To monitor the usage of our services
- To detect, prevent, and address technical issues
Data Security
Product measurements
We use account and service records to calculate aggregate registrations, successful video generation, paid account status, and authenticated daily activity. Daily activity is deduplicated by account and UTC date and retained for 120 days. The internal operations dashboard receives aggregate counts and dates, not email addresses, account identifiers, prompts, uploaded media, or individual activity records.
With analytics consent and without browser Do Not Track or Global Privacy Control, registration views, starts, and confirmed account creations may be sent to Google Analytics. Events contain only the registration method and a random, single-use event identifier, not form contents or account identifiers. A signed, HttpOnly registration receipt expires after 24 hours; server receipt records are removed after two days. Denying analytics does not prevent account use. First-party service measurements remain separate from optional third-party analytics.
When an authenticated user opens a hosted payment checkout, we keep a first-party checkout-attempt record for up to 180 days. It contains the account identifier, payment provider and session identifiers, selected plan or credit package, a price/currency/billing-interval snapshot, lifecycle status and timestamps, and a sanitized failure category. If the user returns after cancelling and chooses to answer the optional survey, we also save one fixed-choice reason. We do not store card details, checkout URLs, provider error messages, or free-form survey text in this record.
With analytics consent and without Do Not Track or Global Privacy Control, checkout stages and an optional fixed-choice cancellation reason may also be sent to Google Analytics and OpenPanel. These events use a random checkout-attempt identifier and catalog identifiers; they do not contain card details, checkout URLs, account identifiers, email addresses, names, or free-form text. The first-party checkout record and optional survey submission support payment operations and troubleshooting and do not depend on analytics consent.
We implement appropriate security measures to protect your personal information from unauthorized access, alteration, disclosure, or destruction.
Third-Party Services
We may employ third-party companies and individuals to facilitate our services, provide services on our behalf, or assist us in analyzing how our services are used.
Stripe processes card and other payment-method information on its hosted checkout pages. We receive payment and subscription status needed to provide the purchased service, but do not receive or store the full card number.
With your analytics consent, OpenPanel measures page views, including navigation within the app. It does not load when your browser signals Do Not Track or Global Privacy Control. Page URLs retain only the marketing parameters utm_source, utm_medium, utm_campaign, utm_term and utm_content. Values are limited to 120 characters and a restricted character set; email addresses, URLs and control characters are rejected. Other query parameters and URL fragments are removed. Referring URLs are reduced to their HTTP(S) origin, without paths, query parameters or fragments. We do not enable OpenPanel user identification, session replay, automatic element tracking or outgoing-link tracking, and do not send it account identifiers, form contents, prompts or uploaded media. See our Cookie Policy for how to manage analytics consent.
With your analytics consent and without browser Do Not Track or Global Privacy Control signals, Tawk.to processes visitor sessions, visited pages, referring URLs, device and browser details, and IP addresses for basic visitor statistics. We keep its chat widget hidden and do not enable account identification or custom business events. We do not explicitly send it account names, email addresses, account identifiers, prompts or uploaded media. We block or stop Tawk.to when a page or referring URL uses an authentication path or contains recognized sensitive parameters, such as token, code or email. Other query parameters may still be recorded. After it stops, tracking can resume only after a full reload on an eligible page.
Changes to This Privacy Policy
We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page.
Contact Us
If you have any questions about this Privacy Policy, please contact us.