Send us feedback or questions using the form below. This static form opens your email client.
If the form doesn’t open your email client, click here:
Email us.
Make it useful
How to use this page without overthinking it
This part of the site is meant to support your decision-making, not to overload you. Skim for what matters to you today, and feel free to leave the rest for another time.
Make your message count
How to send feedback that improves Calorie Explorer for everyone
Thoughtful messages help us refine the tool, expand food coverage, and clarify confusing parts of the experience.
Share where you got stuck. Tell us what page you were on and what you were trying to learn or compare.
Suggest missing perspectives. If you notice a cultural food, common meal style, or everyday scenario that isn't represented, let us know.
Note what worked well. Positive examples of clear explanations or useful comparisons help us repeat those patterns elsewhere.
You don't have to write a long report—even a short, specific comment can point us toward meaningful improvements.
Setting healthy boundaries
What we can't do through the contact form
We care about how people use Calorie Explorer, but there are important limits to the kinds of help we can offer directly.
No emergency support. The site and inbox aren't equipped to handle crises or urgent health situations.
No personal diagnoses. We can't interpret symptoms, lab results, or medical histories.
No individualized meal plans. Suggestions need to stay general so that you can adapt them with professionals who know your context.
Knowing these limits helps keep expectations realistic and encourages people to seek the right kind of support when they need it.
Help shape the roadmap
Types of suggestions that are especially helpful
Specific, story-backed ideas make it easier to see how potential features would play out for real people.
Scenario-based requests. Explain the situation you were in and what you wished the site could do in that moment.
Clarity improvements. Point out any labels, flows, or explanations that felt confusing and suggest wording that would have helped.
Coverage gaps. Note everyday foods, cuisines, or contexts that feel underrepresented in the current experience.
Even if every idea can't be implemented, understanding your real-world use cases helps keep improvements grounded and practical.
What to expect
Setting expectations for replies and changes
Feedback is appreciated, but not every message can receive a direct reply or immediate change.
Patterns matter most. Suggestions that show up in many messages are more likely to shape future updates.
Some issues take time. Accessibility improvements, structural redesigns, and new tools may require careful planning.
Silence isn't dismissal. Even when we can't respond individually, feedback can still influence the overall direction.
Sharing your experience is still valuable, even if the visible impact shows up gradually rather than right away.
Help keep things accurate
How to report bugs, data issues, or confusing results
Even with care, occasional errors or unclear moments can appear. Clear reports make it much easier to investigate and fix them.
Include the page or feature. Share the URL or describe whether you were in the calculator, foods browser, or another section.
Describe what you expected. Explain what you thought would happen before the bug or confusing result appeared.
Add examples if possible. Specific food names, values, or steps you took help recreate the issue.
You don't need to use technical language—just a clear story of what happened is already a big help.
Broader impact
Suggesting improvements for specific communities or cuisines
Food is deeply cultural. Suggestions that highlight missing perspectives can help make Calorie Explorer more inclusive over time.
Name the context. Share the region, culture, or community you're thinking about when you notice gaps.
Offer everyday examples. List common dishes, snacks, or ingredients that feel underrepresented.
Explain why it matters. A brief note about how inclusion would help you or others can guide prioritization.
While not every request can be added quickly, these insights help shape a more representative tool in the long run.
Human side
Sharing stories of how the tool has supported you
While feature requests and bug reports are important, it can also be helpful to hear how people have woven Calorie Explorer into their real lives.
Describe a specific moment. Share a time when a comparison, article, or planning session made something click.
Highlight what changed for you. Maybe your shopping felt calmer, or you felt less guilty about a particular choice.
Mention what felt respectful. Notes about tone, wording, or features that felt supportive can guide future decisions.
You never have to share more than you're comfortable with, but real-world stories can help keep future improvements grounded and humane.
Inclusive design
How to suggest accessibility improvements
Accessibility is an ongoing practice, not a one-time checkbox. Thoughtful suggestions can make the site easier to use for more people.
Describe the barrier. Share what made the site hard to use—such as contrast, keyboard navigation, or screen reader behavior.
Explain your setup. Mention the device, browser, or assistive technology you were using when you noticed the issue.
Offer examples if you can. If you've seen similar tools handle the same challenge well, that can help point to solutions.
Even when fixes take time, clear accessibility feedback is always valuable.