Project or export issue
Include the project URL, what you expected, what happened, browser details, and any visible error text. Never send API keys or private credentials.
Tell us what happened. We'll help route it.
Get help with a project, generation, export, credit charge, privacy request, security report, or product question.
Billing or credits
Include the account email, approximate time, plan or credit pack, and the relevant usage-ledger row or checkout receipt identifier.
Privacy or security
State whether the request involves access, deletion, a suspected vulnerability, or a legal notice. Sensitive security details should not be posted publicly.
Product feedback
Share the job you were trying to complete, where the workflow became confusing, and what outcome would have been more useful.
Before you email
Check the usage ledger for generation charges and try a clean local install for export issues. Those two artifacts usually make diagnosis much faster.
Keep secrets out of support messages
Do not send passwords, session cookies, payment card data, database credentials, provider keys, or private customer data. Redact screenshots and logs before attaching them.