MagicOptix

Transparency

Desktop Metering and Diagnostics

A clear view of what MagicOptix collects automatically, what is sent only after confirmation, and why those data flows exist.

Last updated: June 2, 2026

Short version

If usage metering is enabled, MagicOptix records lightweight execution metadata to enforce plan limits and support billing/access decisions. Detailed diagnostics are sent to support only when a user explicitly confirms the action.

Automatically Collected for Access and Metering

This data helps MagicOptix keep the desktop app licensed, enforce plan limits, and show operational usage in the portal.

  • Account and session state required to authenticate the desktop app and portal.
  • License, plan, feature access, device binding, and monthly usage window.
  • Execution metadata: execution id, workflow, source, status, counts, duration, app, design type, template count, template labels, timestamps, and billing state.
  • App version and device reference used to understand compatibility and active-device limits.

Sent Only After “Send Diagnostics”

When you click Send Diagnostics and confirm, MagicOptix sends a support report for the selected or latest diagnostic execution.

  • Runtime log preview for the selected execution.
  • Execution request snapshot and result summary.
  • Error messages, result references, output folders, local paths, and workflow context.
  • Template labels, design type, app, source, status, and row/result counts.

Not Automatically Uploaded During Normal Metering

  • Full PSD or AI documents are not automatically uploaded for normal metering.
  • Full CSV, image folders, font files, and generated output folders are not automatically uploaded for normal metering.
  • Detailed diagnostics are not sent silently. They require a user action and confirmation.

Why This Matters

MagicOptix runs local Adobe workflows where failures can depend on files, templates, layers, paths, app versions, and operating system context. Lightweight metering keeps plan usage clear. User-confirmed diagnostics help support investigate real failures without asking users to manually assemble logs and screenshots.