Get in touch
Pick the channel that matches your question — that way the right person sees it first, and you'll hear back faster. None of the addresses below are monitored 24/7, but every legitimate message gets a human reply, usually within a few business days.
Choose where to reach us
Help & support
Trouble installing, running, or using Vitriol. SmartScreen warnings, conversion errors, the password lock disappearing, FFmpeg not detecting hardware encoders — anything you'd ask a human to walk you through.
General & business
Partnerships, press, licensing inquiries, integrations, anything that isn't a specific user-support question. If you're not sure which channel to use, this one routes correctly.
Bug reports
If something's clearly broken — a conversion fails with an error, the app crashes, or output is corrupted — open an issue on GitHub. Reproducible bugs get the fastest fix because the report becomes a permanent, searchable record.
Security disclosures
If you've found a security vulnerability — anything that could let an attacker recover encrypted Stone payloads, escalate privileges via the installer, tamper with auto-update downloads, etc. — please use GitHub's private security advisory flow rather than a public issue, so the fix can ship before the details are public.
Before emailing — quick links
Most common questions are already answered in one of these places. Worth a glance before opening a thread:
- Download page — installer vs. portable, system requirements, signed publisher
- Philosopher's Stone explainer — what cross-category vs. same-category conversions look like
- README on GitHub — feature list, format support, scope notes
- Existing issues — chances are someone has already asked your question
- Privacy policy — what data Vitriol does and doesn't collect
- License — what you can and can't do with Vitriol under the Elastic License v2
Response expectations
Vitriol is a single-developer project — no support team, no SLA, no premium tier. That means:
- Reasonable turnaround for legitimate questions: a few business days. Sometimes faster, occasionally slower if I'm deep in another release.
- GitHub Issues are public and stay public — that's part of why they're the fastest path for bugs and feature requests. Other users see your question, sometimes answer before I do, and the conversation becomes a search result for the next person with the same question.
- Email is private and slower. Reserve it for things that don't fit a public issue tracker (account setup, business inquiries, support requests with personal context you don't want indexed by search engines).
- Sales pitches and unsolicited "offers" go to spam. If you're a vendor selling a service Vitriol doesn't need, please don't.