Contact Zyff

One address covers everything: bugs, bad output, tool requests, questions about how a tool works, privacy questions, and copyright or takedown notices. Put the topic in the subject line so it is obvious at a glance, and include the URL of the page you were on.

The chat bubble is the same conversation by a faster route, and it is the better choice for a quick question about how a tool behaves. It is operated for us by Brevo, so what you type there is stored by them as well as read by us — the privacy page explains exactly what that means. Email is the right channel for anything you would rather not hand to a third-party inbox, and for a takedown or a formal privacy request, which needs a written record.

Plain text is fine and preferred. If you need to attach a file so we can reproduce a problem, remember that an email attachment lands in an ordinary inbox and stays there, unlike a tool upload, which is processed in memory and never stored. Do not send anything you would not normally send by email. A screenshot of the result is often enough.

This is the most valuable mail we get, and the difference between a report we can fix and one we cannot is usually four or five specifics. A result that came out wrong is a bug even when nothing threw an error, so send those too: a mask that cut through someone's shoulder, a compressed file that got larger, a converted image with shifted colors.

If the tool showed you an error message, quote it exactly. Those strings map to specific checks in the code, which usually points straight at the cause.

Tell us the job rather than the tool name, and include the phrase you searched for before you landed here. Search wording tells us more about what people need than a feature title does, and requests that name a concrete format, dimension, or limit are the easiest to act on.

If the tool you want is already listed with a coming-soon label, say so anyway. Those messages are a direct signal about build order, and they carry more weight than page views do.

If you have never signed in, there is no profile to export or close — tools need no account. If you do have one, you can delete it yourself from your account page, which removes your identity and your saved widgets. Uploads are processed in memory and never stored, so there is normally no copy of your file for us to delete by the time you write. If you have a question about the aggregate page-view and performance analytics the site collects, ask and we will answer it directly.

For copyright or DMCA notices, include the URL on zyff.app, a description of the work, and how to reach you. One thing worth knowing first: the Google Reviews widget shows review data that originates with Google's Places API and with the people who wrote it. Zyff holds a cache of what Google returned, described in the privacy policy, and refreshes it from Google — it is not an independent copy we edit or curate. So a request to change or remove an individual review has to go to Google or to the business that owns the listing. Once it is gone there, tell us as well: our copy is kept indefinitely and refreshed only on demand, so unlike a timed cache it will not clear itself. Email ashokguptaa66@gmail.com naming the business and we will delete our stored copy for it.

We read everything, and we reply when we can. We are not going to invent a response-time promise we cannot keep, so treat it as: a real person will see your message, and a clear bug report is far more likely to get an answer and a fix than a vague one.

You will not get a ticket number or an automated acknowledgment — email reaches a person, not a helpdesk. We do not accept guest posts, link exchanges, paid placements, or sponsored tool listings, so those messages will not get a reply.