Contact
Whatever you send, the same person reads it. This page just gets it there faster.
What do you need?
| Your message | Where to send it |
|---|---|
| A bug on a page where Emojery runs | Open the Report tab in the popup on the page that broke — it attaches the URL for you. Popup not opening? File a bug report. |
| A site Emojery should support | Check the roadmap first, then file a site request with 2 public example URLs. |
| A feature idea | File a feature request. |
| A question about how it works | Try the FAQ. If the answer is not there, ask a question. |
| A security vulnerability | Open a private security advisory, never a public issue. Scope and safe harbour: Security. |
| Privacy, data rights, or a legal notice | File a privacy or legal request, or email [email protected]. What we store: Privacy. |
| Press, interviews, review copies | Email [email protected]. Boilerplate and facts: press kit. Logos and screenshots: media kit. |
| Deleting your account or reversing your reactions | Nothing to send: reverse a reaction on the page itself, and delete the account from the popup's Account tab. What deletion removes: Privacy. |
| Funding the project | Sponsor links are on Donate. |
Two details save a round trip: report a bug from the page it happens on, so the popup sends that page's URL with your note, and add a screenshot of where the picker should sit when you ask for a new site.
Who reads it
Emojery is built by one independent developer, khasky (GitHub, LinkedIn). No support desk, no ticket robot, no second line to escalate to: whichever channel you pick, the same person reads it.
[email protected] — press, privacy and legal mail, read by the maintainer. Bugs and site requests belong in the templates above, where they can be tracked and closed.
Not sure where it belongs?
Send it to whichever row looks closest. Nothing is bounced for landing in the wrong place.