ChatMock is a small independent project, and this inbox goes straight to the people who build and maintain it. There is no ticket queue, no chatbot and no offshore support layer — just an email address that a human reads. Because the project is small, we answer the messages that help the tool and skip the ones that only ask us to do something a static website cannot do.
Email us
hello@chatmock.net
Putting a short subject prefix in the line makes routing immediate: Bug, UI correction, Copyright, Business, Abuse or Privacy. Anything sent without a prefix still gets read — it just takes a little longer to sort.
What we can actually help with
- Bug reports. The generator exports a broken image, a bubble is clipped, a control does nothing, a page fails to load. Tell us the platform page, the browser and the device, and — if you can — the exact steps that triggered it.
- UI accuracy corrections. This is the single most useful email we receive. If a colour, corner radius, tick state or timestamp position is wrong on a platform you use every day, send the correction. We verify against the real app and fix it; several of the details in our colour reference came from exactly this kind of note.
- Copyright and trademark complaints. If you believe a name, logo or screenshot recreation on this site infringes a right you hold, write to us with the specific page and the material concerned. We act on substantiated complaints, including removing material where that is the right outcome.
- Business and partnership enquiries. Licensing, embedding, bulk export or API access for a product or agency workflow. Tell us what you need and what scale you are working at.
- Press and content. If you are writing about mockup tools, screenshot authenticity or the ethics of fabricated conversations, we are happy to give a direct answer on the record.
- Reports of misuse. If someone has used ChatMock to produce an image that violates our Acceptable Use Policy, send the image and the context in which you found it. See the note below on what we can and cannot do about it.
- Privacy questions. Anything about data, analytics or local storage — see the Privacy Policy first, then ask.
Response times
We aim to reply within two to three business days. UI accuracy corrections and clear bug reports are usually answered faster, because they are the ones we can act on immediately. Business enquiries that need a proposal take longer. If a week passes with no reply, resend once — occasionally a message lands in spam.
What we cannot do
Being honest about this saves everyone time. ChatMock has no accounts and no server that stores mockups — every conversation you build is rendered and exported inside your own browser. That is the core of the privacy design, and it has a practical consequence: we cannot see, retrieve or delete anything you created. We cannot recover a mockup you lost, tell you what a conversation contained, or confirm whether someone used the tool to make a particular image. We also cannot take down an image posted on another platform — that request belongs with the platform hosting it, though we will always answer questions about the tool itself.
Why there is no contact form
A form on this site would have nothing behind it. The whole product is a static page that draws pixels in your browser; there is no application server to receive a submission, and a form that silently drops messages is worse than no form at all. A plain email address is the honest version of the same thing — and it means you have a record of what you sent us.
Before you write
A few pages already answer the most common questions: the About page explains how the project works and why it is free, the examples gallery shows complete scenes you can rebuild, and the blog collects the platform-specific guides. If your question is already covered there, the answer will arrive faster than any reply.