Home › Contact

Contact byedpi.io

Questions or corrections about this website? Email us — that is what the address below is for. Software broken instead? That still belongs with the developers, and this page explains how to tell the difference and where each kind of message actually lands.

Illustration for the contact page: a large envelope with an at-sign badge, for emailing this website

Email this site

For anything about byedpi.io itself — a wrong command in a guide, a claim that no longer matches the official documentation, a correction to the review, a guide that failed you — write to [email protected]. That is this site's own domain email address, and it is the lead contact method for the website. Our website is https://byedpi.io/ — anything purporting to come from a different domain, or a lookalike address, is not us.

Corrections sent to that address are checked against the primary sources described on the about page; if a report is right, the page is fixed. If your message is really about the software rather than this site's content, it will travel faster through the projects below — the site team cannot fix ByeDPI itself, and we will not pretend otherwise by taking the bug report ourselves.

Software questions go to the projects

Before posting, run through the troubleshooting guide and check the FAQ. It is not gatekeeping; the answers there are simply faster than any reply we or the developers can type, and a report that mentions what you already tried gets dramatically better responses.

What not to send

Please never send passwords, account details, payment information, or personal traffic data to us or to public GitHub threads. Nobody legitimate in this ecosystem needs them to help you. Describe symptoms, settings and providers — never credentials.

Business and republication

Quoting this site with a link is welcome. Republishing whole guides is not; see the terms of use. The ByeDPI software itself belongs to its developers under the MIT and GPL-3.0 licenses — we cannot grant anyone rights to it, and our independence from them is explained in the disclaimer.