Who we are
MixUp.live builds creator media and live production tools, including A‑B Roll, Dekorum, and future MixUp.live products. In this policy, “MixUp.live,” “we,” “us,” and “our” refer to the MixUp.live product family and related websites.
What we collect
Depending on how you use the site or apps, we may collect:
- Website visit analytics, if enabled.
- Your email address when you choose to join a MixUp.live product or beta-interest list.
- Aggregate download counts for public app downloads.
- Optional campaign or UTM tags, such as links from Facebook, NDI user groups, email, or beta pages.
- Purchase and billing information handled through Stripe.
- License activation information needed to unlock paid features such as A‑B Roll Pro.
- Support emails, screenshots, attachments, logs, or crash details that you voluntarily send to us.
- Basic technical information needed to operate websites, downloads, app updates, and support workflows.
Downloads and telemetry
We may use privacy-conscious download telemetry to understand aggregate interest in public builds. This can help us answer basic product questions such as how many people clicked a download link, which campaign link was used, and whether a public release is reaching testers.
Download telemetry is intended for aggregate product and release measurement, not behavioural tracking inside the app. You can avoid campaign-tagged links by using a plain download URL when one is available.
Different MixUp products may use different operational or analytics systems. Product-specific disclosures are provided where relevant.
A‑B Roll anonymous usage metrics
A‑B Roll may send a small HTTPS request when the app launches if Share anonymous usage metrics is enabled and the build is eligible to report. This setting is on by default and can be disabled in A‑B Roll Settings. Disabling it stops future usage-metric reports and does not change A‑B Roll functionality.
The request contains only:
- A random installation identifier.
- The app marketing version and build number.
- The current Free or Professional tier.
We use these metrics for aggregate product analytics: estimating unique installations, measuring app opens and repeat opens, understanding the Free and Professional usage mix, and seeing which app versions and builds are active.
The random installation identifier is pseudonymous when sent. Our server one-way hashes it before storage, and the raw identifier is not stored in the telemetry database. This telemetry identity is separate from the licensing DeviceID and is not linked to a license, account, email address, hardware ID, Stripe record, or customer record.
A‑B Roll usage telemetry does not include:
- Media, audio, or frame contents.
- Filenames, file paths, playlists, NDI source names, or show names.
- Device names, hardware serial numbers, or MAC addresses.
- Account details, email addresses, license keys, activation tokens, Stripe IDs, or customer IDs.
- Playback events or keyboard events.
The request is encrypted in transit using HTTPS/TLS. Network and infrastructure providers may process connection metadata as needed to deliver it. A‑B Roll's application telemetry storage does not intentionally retain IP addresses for this usage metric. The metrics are not used for advertising or cross-app tracking.
Dekorum
Dekorum is currently a private beta. Render hosts the web application. Supabase provides invited-user magic-link authentication, the access list and account-owned saved Projects. These services may process ordinary account, request and connection information as needed to deliver and protect the service.
The Dekorum sign-in screen includes a beta-access request form. It requires an email address and can include an optional name and company, show or use-case context. Valid requests are stored in Supabase with a pending access status for manual review; submitting a request does not grant access. When server-side notifications are enabled, the same request details, submission time and service environment or origin may also be sent to MixUp.live through Resend so the request can be reviewed.
Anonymous Dekorum product telemetry is optional and off by default. Eligible users can choose whether to share it and can change that choice through Privacy settings in Dekorum. When enabled, Dekorum sends one limited reopen report containing a random installation identifier, app version, build and current tier. We use this to estimate anonymous installations and reopens and to understand which versions and builds remain active.
The random identifier is created and stored in the consenting browser. The Cloudflare telemetry Worker stores only a one-way SHA-256-derived installation hash in Cloudflare D1, together with first- and last-seen times, reopen count, and the latest version, build and tier. It keeps one mutable summary per installation rather than an event history. Inactive summaries are deleted after 24 months. Turning sharing off stops future reports and removes the browser's local telemetry identifier, but it does not retroactively delete an existing anonymous server summary.
Dekorum product telemetry does not include:
- Name, email, account or authentication identity, or invite and access status.
- Shows, graphics, saved Projects, sessions, or Sequence, Preview, Program and Output content or activity.
- Route history, referrer, user-agent string, device details or a device fingerprint.
- Raw installation UUIDs or IP addresses in the application telemetry payload or D1 telemetry record.
Access administration and anonymous telemetry are separate systems and do not share an identifier. Cloudflare may process a source IP transiently at its edge for telemetry rate limiting, and Cloudflare, Render, Supabase, Resend and other infrastructure providers may process ordinary request or security information while delivering their services. The exclusions above describe Dekorum's application telemetry payload and storage; they are not a claim that infrastructure providers receive no network information.
Purchases and license activation
Purchases are processed through Stripe. Stripe may collect payment, billing, fraud-prevention, and transaction information according to its own policies. MixUp.live receives the information needed to confirm purchases, operate checkout, provide support, and activate licensed features.
License activation data is used to verify that a license is valid and unlock the correct app features. We try to keep licensing data limited to what is needed for activation, support, and abuse prevention.
Support emails, logs, and crash reports
If you contact us for support, you may choose to send screenshots, logs, crash reports, system details, or other attachments. We use that information to understand the issue, improve the product, and respond to you.
Please do not send confidential production files, private client media, passwords, license tokens, or payment details in support emails.
Third-party services
We use third-party services to operate the site, downloads, payments, updates, and support. These may include:
- Cloudflare for DNS, hosting, Workers, R2 storage, caching, download infrastructure, and Turnstile bot verification. Turnstile processing is also covered by Cloudflare’s Turnstile Privacy Addendum.
- Brevo for storing beta-interest email addresses and sending product updates.
- Render for hosting the Dekorum private-beta application.
- Supabase for Dekorum authentication, private-beta access administration, and account-owned saved Projects.
- Resend for optional Dekorum access-request notifications.
- Stripe for checkout, payments, billing, and transaction processing.
- Sparkle-compatible update infrastructure for app update delivery.
- Email and support inbox providers for product communication and support.
- WordPress or other website hosting systems where beta or release-note pages are hosted.
How we use information
We use information to:
- Operate MixUp.live websites and app download flows.
- Measure aggregate public release and beta download activity.
- Process purchases and activate licenses.
- Provide support and respond to feedback.
- Improve app reliability, release quality, and documentation.
- Protect the site, downloads, licensing, and payment flows from abuse.
We do not sell personal data.
Your choices
- You can disable Share anonymous usage metrics in A‑B Roll Settings.
- You can leave Dekorum anonymous telemetry off or enable and disable it through Dekorum's Privacy settings.
- You can choose not to send crash reports, logs, screenshots, or support attachments.
- You can avoid campaign-tagged links by using plain site navigation or a plain download URL when available.
- You can contact us with privacy, support, or deletion questions.
Data retention
We keep information only as long as it is reasonably useful for operating the product, supporting users, meeting business or legal needs, improving reliability, and protecting the service. Support emails and beta feedback may be retained while they remain useful for product development and support history.
For A‑B Roll usage metrics, we retain a single pseudonymous installation record used for aggregate all-time installation and usage counts. We do not keep a separate event history for every launch. We may revisit this retention approach as the product and policy evolve.
Dekorum anonymous telemetry retains one mutable summary for each hashed installation identifier and deletes summaries that have been inactive for more than 24 months. Private-beta access requests and saved Projects follow the general retention approach above and may be kept while needed to administer access, provide the service and support users.
Changes to this policy
We may update this privacy policy as MixUp.live, A‑B Roll, Dekorum, and related tools evolve. When we make meaningful changes, we will update the effective date on this page.
Contact
For privacy questions, contact privacy@mixup.live. For A‑B Roll beta support and feedback, contact beta@mixup.live.