quietpix

Contact

QuietPix is a small project, not a company with a support department. Mail goes to one inbox and a person reads it.

Email

infoquietpix@gmail.com

There is no contact form here on purpose. A form would mean a server collecting what you type, and the whole point of this site is that it does not run one. Your mail client talks to your mail provider; nothing passes through QuietPix.

Reporting a bug

This is the most useful mail you can send, and the one most likely to change something the same week. Four things make a report actionable:

Crashes are also reported automatically, without file contents, which is how most fixes start. A message from a real person still helps: it tells us which failures actually got in someone's way.

Requesting a tool or a format

Tell us the job rather than the feature. "I need to get a 40 MB video under Discord's limit" leads somewhere better than "add a video compressor", because the job often has a simpler answer than the feature would. Requests that keep arriving get built first.

Privacy, data and legal questions

The short answer is in the privacy policy: files are processed on your device and never uploaded, so there is no stored file to request, export or delete. If you need that in writing for an employer, a client or a compliance review, ask and you will get a plain answer rather than a form letter. Licensing and attribution questions are covered on the licenses page.

Advertising and business

QuietPix is funded by ads placed outside the tools themselves. For anything commercial — sponsorship, partnership, or a question about how ads are served — use the same address and say so in the subject line.

What to expect

Replies usually take a few days. Bug reports get priority, because they affect people beyond the person writing. Mail is read in the order it arrives and nothing is deleted unread, but a vague message ("it doesn't work") may get a question back rather than a fix.

Who is behind this

QuietPix is built and maintained by one developer. The reasoning behind the architecture, and why the tools run on your device instead of a server, is written up on the about page.