Privacy overview

1. Scope

This page explains how MiracodeX is intended to handle account, support, and related service data at the current launch stage. It does not change the core product direction: MiracodeX is local-first by design.

2. Local-first product model

• Project files, code, and delivery artifacts are intended to stay local by default.
• Cloud services should be limited to account, licence, support, and related service workflows unless the user explicitly enables more.

3. Data categories

• Account information such as email address, login credentials, and basic profile details used for access and support.
• Subscription, licence, and transaction records used to manage trials, access rights, and service operations.
• Support information such as support emails, voluntarily submitted logs, screenshots, or diagnostic files when you choose to provide them.

4. How data may be used

• To authenticate users, manage trials or subscriptions, and verify licence status.
• To provide onboarding, product support, account notices, and service communications.
• To maintain service reliability, prevent abuse, and improve operational quality.

5. Third-party services

MiracodeX does not aim to transfer project code or local delivery artifacts by default. Limited third-party services may be used for account management, billing, email delivery, analytics, or infrastructure support where necessary to operate the product.

6. Retention and deletion

Account, billing, and support records may be retained for legal, financial, security, and operational purposes. If you need account deletion or related assistance, contact the support channel listed on the site.

7. Security

Reasonable technical and organizational measures should be used to protect account and service data. No internet-connected service can guarantee absolute security.

8. Contact

For privacy questions or account-related requests, contact the support email published on the MiracodeX website.