Technical issue
Include the exact page, browser, device type, action, and visible error. For a file tool, include the source format and approximate size without sending confidential material.
Contact and support
Tell us what you need help with
Use the support form for a product question, reproducible technical issue, account or billing problem, licensing question, privacy request, or intellectual-property concern. Clear details help us route and investigate the request.
- Do not send passwords or full card details
- Include the page and exact step for bugs
- Use the account email for billing questions
Before you send
Give us enough context to reproduce the issue
For a technical problem, include the page, browser, device type, exact action, and what appeared instead. For billing, use the account email and a non-sensitive order reference.
Direct support inbox
Messages sent through this form arrive in the Nexlogo Studio support inbox, and replies go to the email address you enter below.
Best support message
Include the brand name used, the selected step, what you expected, and what happened instead.
Billing or credits
Include the account email, plan name, date, and a non-sensitive order or invoice reference. Never send a full card number, security code, password, or one-time login code.
Licensing question
Tell us whether the logo is for your own business or a client and which export or typeface is involved. Commercial-use rights do not replace trademark or third-party license checks.
Privacy or IP
Link to the specific public page or material involved and explain the concern clearly. Remove unrelated personal information from screenshots and attachments before sending.
Before you send a support request
Check the Help Center and FAQ first when the question is about a known workflow, export, or browser-tool limit. For payment rules, use the Pricing and Refund Policy pages. For commercial-use, trademark, or third-party asset questions, start with Licensing and Copyright and IP. Those pages provide the current published rule and often resolve a question immediately.
How support uses your message
The information in the form is used to understand and respond to the request, investigate a product problem, and keep a reasonable support record. Do not include passwords, authentication codes, private keys, recovery phrases, complete payment-card details, or confidential client files. The Privacy Policy explains how contact information and other service data are handled.
For bug reports, describe the smallest reproducible problem
A strong bug report names the page, the exact control used, what happened immediately before the issue, what you expected, and what appeared instead. If the problem involves an image or SVG, a simple non-confidential sample with the same format and dimensions is more useful than an unrelated large production file. This helps separate a format limitation, browser-memory issue, account-state problem, and genuine application bug.