Questions, answered.

Yes. Direct messages are private: in the app, only the people in the conversation see them, and as a matter of policy our staff do not read private conversations. Connections are encrypted in transit with TLS, so nobody in between is reading along. Private DMs goes deeper into what that means in practice.

Because moderators need to be able to keep public spaces safe. In a channel with hundreds or thousands of members, moderation tools, automated filters, and the audit log have to be able to see content to act on it: you cannot remove spam you cannot read. This is an honest trade-off, and we would rather state it plainly than imply privacy that is not there. The line is simple: one-to-one conversations are private, shared spaces are governed. Privacy at Vronify lays out the reasoning in full.

On hardware we own and operate in the Netherlands. Nothing is parked on a third party cloud, and nothing leaves our machines for analytics or advertising. Owning the hardware matters for more than privacy: it is why we can tune the whole stack ourselves and hold delivery times most rented infrastructure cannot. The privacy policy spells out exactly what we store and for how long.

No, no, and no. There are zero trackers, zero ads, and zero data brokers involved anywhere in the product or on this site. We never sell data and we never read private conversations. This is not restraint, it is structure: our income will come from optional extras that people choose to pay for, so there is no business reason for your attention or your data to be the product.

Through the vulnerability disclosure process, please, rather than the general support queue. It exists so that reports about the platform's safety reach the people who can fix them fast and quietly, before details become public. If you are unsure whether what you found counts as a security issue, err on the side of the disclosure process; the security page describes how we defend the platform day to day.

Real-time messaging with edits, replies, reactions, and read receipts. Threads for side conversations, polls for decisions, pinned messages for the things everyone keeps asking, and bookmarks for the things you want to find again. Voice channels for talking. For structure: roles and permissions, channel categories, per-server nicknames, custom emoji, and server tags. For safety: an audit log, slow mode, and automated filters. For discovery: an Explore page where public communities can be found. The features page covers each one, and chat and messaging goes deep on the core experience.

The browser version is available now, and it is a first-class experience on both desktop and mobile browsers, not a placeholder. A mobile app for iOS and Android and a desktop app for Windows, macOS, and Linux are coming soon. Until then, nothing is gated: everything the platform does, it does in the browser you already have. Watch the changelog for app announcements.

Automation is coming through the built-in bot engine, which is in active development and not live yet. When it ships, you will flip one switch in your server settings to get welcome cards, auto-reactions, a message log, custom commands, reaction roles, leveling and XP, and tickets, with nothing to host and no token to babysit. We deliberately do not run third-party bot code inside servers: that is how we can promise no external party can read your channels or take your automation offline.

Yes. Voice channels are live today: persistent rooms members drop into and out of, straight from the browser, with no install. They sit in your channel list alongside text channels and respect the same roles and permissions. Voice channels has the details.

Yes, at both the personal and the community level. You get themes, appearance settings, and accessibility options for how the app looks to you, plus a custom profile for how you look to others. Communities get custom emoji, server tags, and per-server nicknames, so the same person can be "Sam" in one server and "DM Sam" in their tabletop group. The customization page shows the full range.

Two ways: your invite link, which you can post anywhere, and the Explore page, where public servers can be discovered by people browsing for a home. Making a server public is optional; private communities stay invisible. If you are building something worth showing off, featured communities is where we highlight the best of the platform, and discovery explains how the Explore page works.

Head to the support page. It lists the fastest way to reach us for questions, bug reports, and account issues, and a real person answers within one business day. Security issues have their own disclosure process. When reporting a bug, include what you did, what you expected, and what happened instead; those three sentences usually cut the back-and-forth in half.

A small team in the Netherlands, writing every line ourselves: the platform was hand-written from zero to over 125.000 lines of code, with no template or white-label product underneath, running on hardware we own and tune. Small and independent is a feature here, not a limitation; it is why the promises on this page are decisions we can actually make. More on the about page, and you can always reach us via contact.

Ask us directly through support or contact, whichever fits. Genuinely useful questions tend to end up on this page, so asking helps the next person too. If your question is about rules of behavior on the platform, the community guidelines and the terms of service are the authoritative sources.