The fastest way to reach PrivateConvert is by email. There’s no contact form because forms phone home to third-party services, set cookies, and capture data we don’t want to capture. A plain mailto link is the most private channel we can offer:
$ mailto: contact@privateconvert.net
One human handles the inbox — Keishin. No ticketing system, no auto-responders, no “we’ll get back to you in 5 business days.” Response times vary: typically within a few days for non-urgent items, faster for security issues or anything that affects a working tool.
What to include in a bug report
If a converter is misbehaving, the following details help reproduce and fix the issue fast:
- Which converter you were using (URL of the page — e.g.
/heic-to-jpg-offline/) - Your browser and version (e.g. “Firefox 132 on Windows 11” or “Safari 17 on iPhone”)
- The general type of file you were converting (e.g. “HEIC from iPhone 15” or “100-page scanned PDF”) — do not send the actual file. We don’t need it and we don’t want it. The whole point of this site is that files stay on your device.
- What you expected to happen vs. what actually happened
- Any error messages shown in the page or in the browser console (open DevTools with
F12→Consoletab, screenshot or paste anything red)
Feature requests & tool suggestions
If there’s a file format you wish we supported — AVIF, AAC to MP3, video formats, audio extraction, anything — let us know. Requests get prioritized based on a mix of demand and feasibility: some conversions are easy to do client-side via WebAssembly, others are prohibitively heavy or technically impossible without a server (which would break the no-upload promise).
The current development roadmap is shaped by two factors: real user demand (what people email us about) and DataForSEO research (what people actually search for). Both inputs matter. A tool nobody emails about but 50,000 people search for monthly is still worth building. A tool nobody searches for but five users desperately need is also worth building.
Security disclosures
If you’ve found a security issue — XSS, malicious file parsing, anything that could compromise visitor privacy or device safety — please email contact@privateconvert.net with “SECURITY” in the subject line. We’ll respond as quickly as possible.
There’s no formal bug bounty program yet, but we genuinely appreciate responsible disclosure and will publicly credit researchers who want recognition. If you’d rather stay anonymous, that’s also fine — what matters is the fix shipping.
Privacy questions
Anything about what we collect, how, or why — ask away. The short version lives in the privacy policy; if anything is unclear or seems too good to be true, email us and we’ll improve the wording. The site’s entire value proposition rests on the “no upload, no tracking” claim being accurate — if you spot a gap between what we say and what the code does, we want to know immediately.
Partnership inquiries
We’re open to partnerships with privacy-respecting tools and services we’d recommend anyway. We’re not interested in: ad networks, data brokers, anything requiring tracking pixels or analytics beyond Plausible, or anything that compromises the no-upload promise. If your offering genuinely fits the privacy-first audience — a no-logs VPN, an end-to-end encrypted email host, a zero-knowledge cloud storage provider — send a pitch.
Press & media
For interviews, articles, or coverage about PrivateConvert’s architecturally-enforced privacy approach — including the technical side of how WebAssembly enables client-side file conversion without a server — email with “PRESS” in the subject. Sample brief on request.
What we’ll never do
- Send marketing email after you contact us (you’re not on a list, because there is no list)
- Share your email with third parties (we don’t have any third parties)
- Use a CRM that “enriches” your email with social-graph data
- Add tracking pixels to replies
- Ask you to upload a file as part of troubleshooting
Email us the way you’d email a friend. We’ll reply the same way.