Company
Talk to us.
No ticket maze, no chatbots, no phone tree. Four addresses, each read by a real person on the team that builds the platform. Pick the right one and your message lands in front of someone who can actually fix things.
Four addresses, read by people.
Every message goes to a shared inbox the team reads directly. Pick the one that matches your topic and skip the routing.
General
Questions, ideas, partnerships, or just to say the platform did something nice. This is the front door, and if you are not sure which address fits, this one always works.
hello@vronify.chatSupport
Account problems, bugs, and anything broken. Answered by a person within one business day. The more specifics you include, the faster the first reply becomes the last one you need.
support@vronify.chatSecurity
For vulnerability reports only, following our disclosure process. Please do not send account issues here; they reach the right people faster through support.
security@vronify.chatPress
Writing about Vronify.chat? We are happy to answer questions, fact-check claims before you publish, and the brand assets page has everything visual.
press@vronify.chatTwo of these addresses have a page of their own worth reading first. Security reports are handled under the vulnerability disclosure process, which explains what to include, what is in scope, and what we promise in return. And if you are writing a story, the brand assets page has the wordmark, the colors, and the usage rules, so you do not have to email us just for a logo.
Before you write.
A few shortcuts that might be faster than waiting for a reply.
Common questions are answered in the FAQ, platform health lives on the status page, and the support process is described on the support page. Everything else: email away. Nobody on the team will ever be annoyed that you wrote, but for the questions below, the answer is already published and available right now.
Common questions
Pricing, privacy, accounts, what happens when you get banned, how private DMs work. If lots of people ask it, the answer is in the FAQ.
Read the FAQIs it just you?
Before reporting an outage, check the status page. If something platform-wide is down, it is already listed there, and we are already on it.
Check system statusThe support process
Self-serve fixes for the most frequent problems, plus an honest description of what support can and cannot do for you.
Visit the support pageDid it change on purpose?
If something behaves differently than yesterday, it probably shipped. Every release is documented in the changelog, in plain language.
Read the changelogRunning a server
Setup, structure, growth, and the decisions that make a community work. The owner handbook covers the questions server owners email us most.
Open the handbookKeeping it civil
Slow mode, filters, the audit log, and how to handle a bad day in your community. The moderation guide walks through all of it.
Read the moderation guideWhat happens after you hit send.
The honest version of how your email is handled, because you deserve to know where it goes.
Every address on this page lands in an inbox the team reads directly. There is no ticketing vendor in the middle, no auto-triage bot scoring your message, and no first-line script to get past. Vronify.chat is built in the Netherlands by a small team, and the same people who wrote the code read the mail. That has a practical consequence: when you describe a bug to support, there is a good chance the person answering is the person who built the feature you are describing. Answers tend to be short, specific, and final for the same reason.
Response times, honestly
Support gets a first reply from a person within one business day. We work on Netherlands time, so a message sent late on a Friday is usually answered at the start of the next week. The general and press addresses are read just as carefully but are not held to the same clock; if your question is time-sensitive, say so in the subject line. Security reports are prioritized and handled under the disclosure process, which describes what to expect step by step.
Wrong address? Not a dead end
If you send a support question to hello@ or a press question to support@, we forward it internally rather than bounce it. You will still get an answer. Picking the right address just makes it faster, because it skips the hop. The one exception worth repeating: account issues sent to security@ slow everything down, both for you and for the researchers whose reports share that inbox. Account problems belong at support.
What we will never ask you for
We will never ask for your password or a verification code, not by email, not in chat, not anywhere. If a message claiming to be Vronify asks for either, it is not us, no matter how convincing it looks. Genuine mail from us comes from vronify.chat addresses and never pressures you to act within minutes. When in doubt, do not click anything; write to support@vronify.chat yourself and ask whether the message was real.
Evidence beats description
A link to the exact message, channel, or server is worth three paragraphs of description. Screenshots help too, especially for anything visual. One honest limitation: direct messages are private, and we don't read them, not even to investigate a report. If your message is about something you received in a DM, screenshots from your side are the only evidence that exists, so include them.
Write a message we can act on.
Four habits that turn a week of back-and-forth into a single reply.
One address, one topic
Route your message with the table further down this page, and keep each email to a single subject. A bug report and a feature idea in the same message will each wait for the other; sent separately, each gets answered on its own merits.
Put the point in the subject line
"Cannot upload an avatar in Firefox" beats "help" every time. A specific subject means your message reaches the right person on the first pass instead of the second, and it makes the thread easy to find again when you follow up.
Include the specifics
What you expected, what actually happened, which browser and device you were on, when it happened, and where: the server, the channel, or a link to the message itself. Never include your password. We do not need it, and we will never ask for it.
Write from the email on your account
For anything account-related, sending from the address tied to your account lets us verify it is you without a round of identity questions. Locked out of that inbox too? Say so up front, and we will verify you another way. It just takes an extra step.
Contact, without the usual friction.
Most platforms make reaching a human the hardest feature to find. We made it the easiest.
Which address, at a glance.
Match your situation, send it to the right inbox, and include what actually helps.
Sent it to the wrong address? Do not resend, we forward internally. The right address is just the faster path, never the only one.
Writing about Vronify.chat.
What press@ can do for your story, and the lines we will not cross for anyone's.
We answer questions on the record, provide background on how and why the platform was built, and fact-check claims about Vronify.chat before you publish. The brand assets page has the wordmark, the color palette, and the usage rules, and the about page covers the story so far. For anything beyond that, email press@vronify.chat with your outlet and deadline, and put the deadline in the subject line so it gets picked up in time.
Facts you can print
- Vronify.chat is built in the Netherlands by a small team at Vronify
- Hand-written from 0 to over 125.000 lines of code, with no template or white-label product underneath
- Runs on hardware we own and tune ourselves
- Under 40ms median message delivery in Europe, and 99.9% uptime across the last 12 months
- 50k+ members supported in a single server
- 0 trackers, 0 ads, 0 data brokers
- Direct messages are private; we don't read them
What we will not do
- Hand over user data. We never sell it, and we do not share it for a story either
- Comment on individual accounts, communities, or moderation decisions
- Read direct messages for anyone. They are private, and we don't
- Confirm a claim we have not verified. If we do not know, we say we do not know
Questions about contacting us.
How quickly will I get a reply?
Support gets a first reply from a person within one business day, on Netherlands time. Security reports are prioritized and handled under the disclosure process. The general and press addresses are read just as carefully but are not held to a fixed clock; if your message is time-sensitive, say so in the subject line and it will be treated that way.
Do you have a phone number or live chat?
No, and that is deliberate. We are a small team, and email gives both of us a written record: you can attach screenshots and links, and we can give you a considered answer instead of whatever fits in a live-chat window. The four addresses on this page are the only official ways to reach us. Anyone offering Vronify support by phone is not us.
How do I report another user or a community?
For a problem inside one community, start with that server's moderators; they have the context and the tools, and they are usually the fastest route. If the behavior breaks the community guidelines or the moderators are the problem, email support@vronify.chat with links to the messages and the server name. For DMs, include screenshots from your side: direct messages are private, so we don't read them ourselves, even to investigate.
I found a security problem. What do I do?
Read the vulnerability disclosure page first; it covers scope, what to include, and what we commit to in return. Then send your report to security@vronify.chat with steps to reproduce and the impact you see. Do not test against accounts or communities that are not yours. And if the problem is with your own account, someone got in, something looks off, that is a support matter: support@vronify.chat handles it faster.
Can I request a feature?
Please do: hello@vronify.chat. Describe the problem you are trying to solve rather than only the feature you imagine, because the problem is what actually shapes what we build. We are a small team and cannot build everything, but requests genuinely steer the roadmap; the upcoming bot engine exists because communities kept asking for automation without third-party bots. Watch the changelog to see what ships.
Can I write in a language other than English?
Write in whatever language you are comfortable in; we would rather have a clear message in your language than a confusing one in ours. English gets the fastest answer, and since the team is based in the Netherlands, Dutch works well too. For anything else we may take a little longer to make sure we understood you correctly.
Where is Vronify located? Can I visit?
Vronify.chat is built in the Netherlands, and the platform runs on hardware we own and tune ourselves. We do not publish an office address, and there is no walk-in desk; everything reaches us fastest by email. Press who need something in person can arrange it through press@vronify.chat. More about who we are is on the about page.
I emailed and heard nothing back. Now what?
First, check your spam folder; our replies come from vronify.chat addresses, and some inboxes are suspicious of domains they have not seen before. If a support message has gone unanswered past one business day, something went wrong on the way, so resend it with the same subject line rather than a new one, which keeps the thread together. And if you bundled several topics into one email, consider splitting them: single-topic messages are answered faster because they do not wait on each other.
Your community. Your rules. Your data.
Create a server, invite your people, and see what chat feels like when your account actually belongs to you.
Free to start. Live in under a minute. No install required.