Get in touch
Bug reports, feature suggestions, privacy questions, or anything else — here's how to reach us, and what helps us reply faster.
Primary email
Editorial & support
Send all correspondence to [email protected]. We aim to respond within 2–3 business days. There is no contact form on the site — email is faster and lets you attach screenshots or files.
What to send where
Bug reports
Tell us the tool name (URL), what you expected, what actually happened, and the browser + version you are using (Chrome 128, Firefox 130, Safari 18, etc). Screenshots or short screen recordings help a lot. Note that we cannot fix issues we cannot reproduce, so detail matters.
Feature suggestions
Have a tool you'd like to see? Tell us what it would do, who it is for, and what existing services fall short. We review every suggestion and frequently build from them. We will not build tools that require server-side processing (this would break the no-upload privacy stance).
Privacy concerns
If you believe a tool is sending data off your device, that is a serious bug. Tell us the tool URL, the input you used, and any network traces you captured (DevTools → Network tab). We will investigate within 24 hours.
Press & partnerships
Press releases, study citations, or partnership inquiries: please use the same address and include "PRESS" in the subject line. We do not run sponsored content or paid placements.
How long replies take
We are a small team. Most messages get a first reply within 2–3 business days, longer if you write on a weekend. Bug reports affecting core functionality get priority; feature suggestions and partnership pitches lower. If you don't hear back within a week, feel free to write a polite follow-up — sometimes mail gets lost in spam filters.
What to include in a bug report
- Tool URL — paste the page where the bug occurred.
- Expected vs. actual — one paragraph each is enough.
- Browser + OS — for example "Chrome 131 on Windows 11" or "Safari 18 on iOS 18".
- Sample input — if the input is sensitive, paraphrase instead of pasting it. We never need real secrets to debug.
- Screenshot or short video — when the bug is visual.
Mailing address
Luminesca is a digital-first publisher. We do not maintain a physical office for editorial correspondence. For legal notices, email us first and we will reply with a postal address if a formal mailing is required.
Tip: if your message concerns Luminesca's other properties — games, news or travel — please indicate so in the subject line so we can route it to the right team.
← Back to all tools