Privacy

Privacy Policy

This policy explains how QRealm Studios handles personal data in connection with the public website, beta applications, purchases, license activation, and related support for Intervals and Intervals Pro.

Effective date: April 22, 2026 Services: Website, checkout, licensing, beta applications Core providers: Lemon Squeezy and Supabase

1. Controller and scope

This Privacy Policy applies to the website at qrealmstudios.com, the Intervals product pages, beta application forms, purchase and licensing workflows, and related customer support interactions.

The service is operated under the commercial name QRealm Studios. For privacy requests, contact qrealmstudios@qrealmstudios.com.

2. Data we collect

We collect only the categories of information reasonably needed to operate the service, process purchases, issue licenses, prevent abuse, and support customers.

  • Website interaction data, such as standard technical request information and limited browser storage preferences used for language selection and site experience.
  • Beta application data, including name, email address, operating system, role, musical experience, DAW information, application reason, and consent confirmation.
  • Purchase and licensing data, including customer email, customer name, country, product and variant purchased, order and customer identifiers, purchase date, refund status, and related license status information.
  • License activation data, including device identifier, device name or instance name, platform, app version, activation events, entitlement tokens, and license validation records.
  • Support and operational records, including webhook logs, anti-fraud records, and service event history needed for diagnostics and auditability.

3. Data stored locally in the desktop app

To keep your license active between sessions, the desktop app may store a local license session on your device. This can include the license key you entered, a short-lived entitlement token, plan tier, feature flags, and token expiry information.

On our backend, we generally store a hashed representation of the license key plus limited reference data, not the plaintext key as part of normal server-side license records.

4. How we use the data

Orders and delivery

To process purchases, deliver licenses, and provide access to the correct edition.

Licensing and security

To activate licenses, enforce activation limits, detect abuse, and keep license status synchronized.

Support and operations

To answer customer requests, review beta applications, and troubleshoot technical or billing issues.

  • Operate the public website and customer flows.
  • Review and respond to beta applications.
  • Process purchases and refunds.
  • Issue, refresh, deactivate, and validate licenses.
  • Prevent fraud, abuse, duplicate activations, and unauthorized access.
  • Maintain accounting, tax, legal, and security records where required.

5. Legal bases

Depending on where you are located, we generally rely on one or more of the following bases:

  • Performance of a contract, where data is needed to process your purchase, provide the software, activate your license, or respond to product support tied to the purchase.
  • Legitimate interests, where data is needed for service reliability, abuse prevention, diagnostics, operational security, and product administration.
  • Consent, where you voluntarily submit a beta application or otherwise provide information for a clearly optional purpose.
  • Legal obligations, where we must retain or disclose information for accounting, tax, fraud, or regulatory reasons.

6. Sharing with third parties

We do not sell your personal data. We may share limited data with service providers only where reasonably needed to operate the product or comply with law.

  • Lemon Squeezy, for checkout, payment processing, tax handling, merchant-of-record operations, and certain refund or anti-fraud actions.
  • Supabase, which we use for license activation, entitlement management, webhook handling, beta form submissions, and related backend storage.
  • Email delivery providers, such as transactional mail providers used to send beta communications or operational messages.
  • Infrastructure and hosting providers that support the website, application delivery, and technical operations.
  • Authorities, advisers, or counterparties where required by law, regulation, formal request, or to protect rights, safety, or security.

7. International transfers

Some of our providers may process data outside your country or outside the EEA/UK. Where such transfers occur, we rely on the provider's contractual, technical, and organizational safeguards as appropriate for the service used and the applicable legal framework.

8. Cookies, browser storage, and analytics

The public site currently uses limited browser storage primarily for language preference and certain presentation settings. As of the effective date of this policy, we do not intentionally run third-party advertising cookies or public-site behavioral analytics scripts.

If we materially change that approach in the future, we will update this policy and any related consent or disclosure flows as needed.

9. Data retention

We keep personal data only for as long as reasonably necessary for the purposes described above. In practice, retention depends on the type of record and the legal or operational need tied to it.

  • Purchase, tax, and accounting records may be retained for the period required by law.
  • Licensing, activation, and anti-abuse records may be retained while a license remains active and for a reasonable period afterward for support, fraud prevention, and audit needs.
  • Beta application records may be kept while the beta or related communications remain active and for a limited period afterward where follow-up or support is still relevant.
  • We may delete, anonymize, or minimize records when they are no longer needed.

10. Your rights

Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or port certain personal data. You may also have the right to withdraw consent where processing is based on consent.

To make a privacy request, email qrealmstudios@qrealmstudios.com and include enough detail for us to identify the relevant record. We may request additional information reasonably necessary to verify the request and avoid unauthorized disclosure or deletion.

11. Security

We use reasonable administrative, technical, and organizational measures appropriate to the size of the service and the type of data processed. No system can guarantee absolute security, but we aim to minimize data collection, limit access, and reduce unnecessary exposure wherever practical.

12. Changes to this policy

We may update this Privacy Policy from time to time to reflect changes in the product, law, operations, or provider stack. The latest version will be published on this page with an updated effective date.

13. Contact details