Contact and support
Reach the personwho builds Azemax.
Azemax Studio is an independent developer project. Email is the only support channel currently offered; there is no ticket portal, live chat, or phone line.
Support is handled on a best-effort basis. Including enough detail in your first message makes a useful reply much more likely.
Support email
azemaxhq@gmail.comEmail is also the address used for privacy requests and legal notices. See the Privacy Policy for how requests are handled.
What to include
A clear first message usually means fewer round trips. Depending on the request, include:
- The email address on your Azemax account, if the request is account-specific.
- The browser and operating system you used.
- The page, panel, or action involved, and the steps that led to it.
- The exact error message or a screenshot of the problem.
- Whether you were using Azemax Default or Bring Your Own Key, if AI is involved.
Never send credentials
Request types
Product support and bug reports
Describe the browser, the page or action involved, what you expected, and what happened. Screenshots and exact error text help. Do not include API keys, passwords, or private source code.
Email with this subjectAccount and data deletion
Send the request from the email address associated with the account and state that you want the account and associated server-side data deleted. Self-service account deletion is not implemented yet, so this is handled manually.
Email with this subjectSecurity reports
Report suspected vulnerabilities privately by email. Include reproduction steps and the impact you believe is possible. Do not test against other users’ accounts or run disruptive load against production.
Email with this subjectBefore you write
Many setup and execution questions are already answered. The documentation covers account verification, provider configuration, key storage, run limits, and common failures. The FAQ covers account deletion, offline use, supported languages, and pricing.
For a product issue, check whether it reproduces after a reload and in a different browser profile with extensions disabled. That distinguishes an application problem from a local extension or network issue.
Security and abuse
Report vulnerabilities privately rather than opening a public issue. Do not access another user’s data, disrupt the service, or use the execution sandbox to attack third parties. The Terms of Service describe prohibited use, and the security section of the Privacy Policy describes how data is handled.