Only what the product needs.

Information we process

The website and hosting layer may process standard request data such as IP address, browser, device, timestamps, requested pages, and security events. A purchase provides the name and email associated with the Stripe Checkout Session, product and price identifiers, payment status, transaction reference, and timestamps needed to fulfill and support the order. We do not receive full payment-card numbers or security codes.

How we use it

We use this information to operate and secure the site, verify paid orders, issue and recover the correct CS2 license, deliver the software, prevent duplicate fulfillment, respond to support, verify education eligibility, investigate defects or abuse, maintain transaction records, and meet legal obligations. We do not sell personal information or use first-party advertising trackers.

First-party site measurement

To understand whether the launch is reaching working technicians, the site records a limited set of first-party events: a random per-tab session identifier, an allowlisted page route and event name, video progress milestone or selected pricing tier when relevant, UTM source, medium, campaign, and content values, the referring site’s hostname, and a timestamp. This measurement is used for aggregate traffic, workflow-view, checkout-intent, and campaign reporting. The analytics table does not store full referring URLs, IP addresses, user-agent strings, names, email addresses, payment identifiers, or license values.

Public Beta forum

Forum display names, reports, replies, status activity, and optional screenshots are public. A follow-up email is optional, stays private, and is used only to clarify or resolve the submitted item. The browser may remember a display name and anonymous device token so the visitor does not need an account and cannot add duplicate affected signals from the same browser. We also process limited request and abuse-control data to rate-limit spam, investigate reports, and moderate unsafe or irrelevant content.

Payments and service providers

Stripe Managed Payments and Link process checkout, transaction support, fraud controls, payment details, receipts, and applicable indirect taxes under Stripe’s Privacy Policy. Hostinger provides the CueStacks website runtime and first-party storage for forum records, screenshots, release delivery, and fulfillment records. Hostinger also processes support and license-delivery email for support@cuestacks.com. Each provider processes information under its own terms and privacy commitments.

Offline licensing

CueStacks accepts legacy CS1 and new CS2 signed keys offline. The key and local license state remain valid on the Mac without a network connection. CueStacks 0.3.23 and later may send a first-party activation receipt to cuestacks.com when the app is opened online, and a Beta tester may also submit that receipt through the direct activation-sync page. The receipt may include a license identifier and fingerprint, licensee name and email, tier, machine identifier and name, CueStacks and macOS versions, and activation/last-seen timestamps. We use it for license support, observed-seat counts, Beta version adoption, and release troubleshooting. It does not remotely activate, validate, revoke, or change an offline license.

Software update checks

If update checks are enabled in CueStacks, the app contacts the first-party cuestacks.com update feed to determine whether a newer signed release is available. The request may include standard network metadata such as IP address, app version, operating system version, and request time. CueStacks does not send show files, media names, license keys, or a hardware profile with an update check. Automatic checks can be disabled in Settings. They are evaluated only when CueStacks opens and do not begin later during a running session. If show audio starts while a launch check is still finishing, its automatic prompt is suppressed for that session.

Storage and retention

Fulfillment records store the order reference, purchaser contact information, product mapping, issuance status, delivery attempts, and an encrypted copy of the issued key for recovery. We retain transaction and license records for as long as reasonably needed to honor perpetual ownership, provide support, prevent fraud, and meet accounting or legal requirements. Support correspondence is retained as needed to resolve the request and maintain an appropriate service history. Forum content may remain public to preserve issue and resolution history. Private follow-up details, abuse records, and removed content are retained only as reasonably needed for support, security, moderation, and legal obligations. Raw first-party measurement events are automatically deleted after 13 months. Short-lived duplicate-prevention and abuse-control records expire sooner. Internal campaign plans and manually entered business-channel snapshots remain private and are retained until they are replaced or no longer needed for operations.

Your choices

You may request access, correction, or deletion of personal information we control, subject to transaction, fraud-prevention, license-recovery, and legal retention requirements. Privacy and data questions, including questions about first-party measurement, may be sent to support@cuestacks.com.