Contact ImagesQueen
Which inbox to use for billing, privacy and abuse reports, what to include, and how long a reply takes.
Last updated: 2026-11-21
Which inbox
One team runs the service, but three addresses reach different people. Picking the right one up front saves a round trip.
| What you need | Send to | Typical reply |
|---|---|---|
| Credits, plans, payments, invoices, watermarks, failed generations | [email protected] | 2 business days |
| Account or data deletion, data export, privacy questions, data subject requests | [email protected] | within 30 calendar days |
| Reporting abusive content, trademark or copyright complaints, abuse of the service | [email protected] with ABUSE in the subject | 3 business days |
A ticket beats an email
If you can sign in, open a ticket at /settings/tickets. A ticket carries your order reference and credit ledger automatically, which removes the usual "which account is this?" round trip. If you email instead, use the address on the account β otherwise we have to verify identity first.
What to include
- Account email, not the display name.
- Rough timestamp, for example
2026-11-20 14:00 UTC. Logs are searched in UTC; local time is fine if you name the zone. - Order or transaction reference. Stripe, PayPal and Creem each use a different format β paste it verbatim rather than retyping it.
- For generation issues: the tool page slug (e.g.
/features/ai-image-generator) and the task ID. Task IDs can be copied from My Generations. - A screenshot, with everything except the last four digits of a card redacted.
What not to send
- Full card numbers, CVVs, or payment passwords. Nobody here needs them, at any point.
- Your account password. If identity needs confirming, we will ask you to do it in the dashboard yourself, not to hand the password over.
- Other people's personal data. For a report about third-party content, give the minimum needed to locate it.
Channels that do not work
- The generator input box. That is the model's prompt, not a message to us. Nobody reads it.
- Social media DMs. The accounts on X and GitHub are entry points only; everything is handled through the addresses and tickets above.
How refunds, deletion and complaints are handled
- Refunds. Start with the terms on /pricing. If your case fits, open a ticket with the order reference and the reason. If it does not, the reply will name the specific clause that applies.
- Account and data deletion. Email the privacy address from the registered address, asking to delete the account and its data. It is completed within 30 days and confirmed by reply. Statutory retention of transaction records is not shortened by a deletion request; section 7 of the Privacy Policy states which records and for how long.
- Content complaints. Rights holders should include a link to the original work, evidence of the right held, and the exact URL complained of. A report missing any of the three is returned for completion rather than actioned.
What we will never do
We will not call or message you out of the blue to "verify your account" or "settle an outstanding charge", and we will never ask you to forward a verification code β not to support, not to anyone. Any message that does is impersonation.
Elsewhere
- Terms of service: /terms-of-service
- Acceptable use policy: /acceptable-use-policy
- Privacy policy: /privacy-policy
- What this service is and is not: /about
