Skip to content

Licensing and Support

Cortiq uses a license activation flow designed for a Windows desktop product.

At a high level:

  • A Cortiq key is issued after purchase or direct distribution.
  • The key is activated inside the desktop app.
  • Activation is verified against the Cortiq licensing service.
  • License validity and expiration are tracked by the platform.

The app surfaces the relevant paths directly in the sidebar:

  • Settings -> License for activation, status checks, and license state
  • Community -> Report a Bug
  • Community -> Feedback
  • Community -> Discussion

Those community links are useful when a user is already inside Cortiq and wants to move directly into the public support channels.

  • Activation is tied to the machine where Cortiq is installed.
  • Live usage typically requires a valid license.
  • License questions should be handled through support rather than public issue threads if they involve personal or payment-sensitive details.

This page is for users who need to:

  • activate Cortiq on a machine
  • understand where to go for support
  • handle license-sensitive questions correctly
  • know which support routes are public and which are private

Use the Cortiq public repository for these support routes:

ChannelUse It For
GitHub IssuesReproducible bugs and feature requests
GitHub DiscussionsQuestions, workflow ideas, and community conversation
GitHub ReleasesCurrent public installer and release notes
Email supportActivation or account-specific help that should not be posted publicly

Do not post these in public issues:

  • License keys
  • Personal payment data
  • Security vulnerabilities
  • Sensitive account identifiers

Security concerns should be reported privately, and license-sensitive cases should go to direct support.

If your license is time-based, expect expiration tracking and renewal handling to matter operationally. Do not wait until a live-trading day to confirm license status.

Use this guidance when you need:

  • help with activation and license continuity
  • the right public route for bugs and feature requests
  • the right private route for sensitive account or payment issues