---
title: "Contact"
url: "https://cookiezest.com/contact/"
description: "How to reach the Zest team — topic requests, bug reports, questions, and security reports."
---

# Contact

How to reach the Zest team — topic requests, bug reports, questions, and security reports.

A few ways to reach us, depending on what you need.

## Topic requests

Building something and wish we’d covered it? Drop the topic in the FreshJuice contact form and we’ll see it. If enough people ask, we’ll write it up for [Learn](/learn/).

[Request a topic →](https://freshjuice.dev/contact/?utm_source=zest&utm_medium=referral&utm_campaign=topic_request)

## Bugs and feature requests

Found a bug, or want something Zest doesn’t do yet? The issue tracker is the right place. Include the version you’re on and a way to reproduce it.

[Open an issue →](https://github.com/freshjuice-dev/zest/issues)

## Questions and discussion

For “how do I…” questions that aren’t bugs, GitHub Discussions fits better than issues. Skim the existing threads first; your answer may already be there.

[Start a discussion →](https://github.com/freshjuice-dev/zest/discussions)

## Email

For anything you’d rather not post in public (partnerships, press, a security report), email [contact@freshjuice.dev](mailto:contact@freshjuice.dev).

## Security reports

Found a vulnerability? Please don’t open a public issue. Email [contact@freshjuice.dev](mailto:contact@freshjuice.dev) with the details instead. See our [security.txt](/.well-known/security.txt) for what to expect.