Terms and Legal
Privacy Policy.
What we collect, why we collect it, where it lives, and what we never do with it. Written to be read, not skimmed past. Effective 1 July 2026.
The short version.
The numbered policy below is what governs, but it will not surprise you. These four points are the whole shape of it.
We collect the minimum
An email address, the content you choose to post, the profile you choose to build, and the short-lived technical records any service needs to stay online and secure. Nothing else.
We never monetize it
No selling, no ads, no data brokers, no profiling. There are zero trackers on this site and in the app, so there is nothing to hand to an advertiser even if we wanted to.
It lives on our hardware
Your data sits on machines we own and operate in the Netherlands, under European data protection law. It is not parked on a third-party cloud where someone else sets the rules.
You stay in control
Export everything whenever you like. Delete a message, or delete your account, which anonymizes it. These are buttons in the app, not requests you file.
The policy in full: what we collect and why.
Plain English, numbered so you can cite it. This half covers who we are, what we take in, and where it lives.
1. Who we are
Vronify.chat is built and operated by Vronify, a small team in the Netherlands. We wrote the platform ourselves, from the first line to well past the hundred-thousandth, and we run it on hardware we own and tune ourselves. That matters for privacy in a direct way: there is no template vendor, no white-label supplier, and no cloud landlord with independent access to what you store here. When this policy says "we", it means the people who wrote the code and administer the machines, and nobody else.
2. What this policy covers
This policy covers the Vronify.chat app and this marketing site. It works together with our Terms of Service, which govern your use of the service, and the community guidelines, which govern behavior in public spaces. Where those documents describe what you may do, this one describes what happens to your data while you do it.
3. What we collect
Account data. An email address and a password when you create an account directly. If you sign in with Google or Discord instead, your provider shares the basics we need to open the account: a name, an avatar, and your email address. We do not receive your contacts, your files, or any ability to act as you on that provider.
Content. The messages and media you post, including edits, replies, reactions, polls, pinned messages, and anything you attach. Content exists because you created it, and it stays yours: section 10 explains how to remove any or all of it.
Profile data. Whatever you choose to add: display name, avatar, banner, bio, per-server nicknames, theme and appearance settings. All of it is optional and all of it is editable or removable at any time.
Functional signals. Small pieces of state that features need to work, such as which messages you have read, so read receipts and unread counts behave correctly, and which servers you belong to, so we know where to deliver your messages.
Technical records. The short-lived operational records any service needs to stay online and fight abuse: connection metadata, security events such as failed sign-in attempts, and error logs. These exist to run and secure the service. They are kept only for as long as they are useful for that purpose, and they are never used to build a profile of you.
4. What we deliberately do not collect
We do not ask for or upload your contact list. We do not track your location. We do not fingerprint your device or browser. We do not follow you around the web, and we do not embed analytics scripts, advertising pixels, or third-party trackers anywhere, including on the marketing page you are reading right now. If a piece of data is not needed to deliver a feature you actually use, our answer is to not collect it in the first place, because data we never hold is data that can never leak, be subpoenaed, or be misused.
5. What we use it for
Four things. To deliver your messages and run the features you use. To keep your account secure, which is what the technical records in section 3 are for. To enforce the community guidelines in public spaces, so shared channels stay usable. And to send you the transactional email the service needs, such as verification codes. That is the whole list. There is no fifth purpose hiding in a definitions section, and we will not add one quietly: section 16 explains how changes to this policy are announced.
6. What we never do
We do not sell your data, to anyone, for any price. We do not show ads and we do not share anything with advertisers or data brokers, so there is no advertising machinery on the other side of the service pulling at your information. We do not profile you, score you, or infer things about you for any commercial purpose. And we do not read your direct messages, which are private to the people in the conversation: staff do not read private conversations.
7. Direct messages, channels, and voice
Different spaces have different visibility, and we would rather spell that out than let you assume. Direct messages are private. In the app, only the people in the conversation see them, and as a matter of policy staff do not read private conversations. Community channels are visible to their community and its moderators, and that is a deliberate trade-off: moderators and our moderation tools need to see public spaces to keep them safe, enforce the guidelines, and act on reports. Treat a public channel like a public square. Voice channels carry conversation in real time; we do not record what is said in them. If a space is readable by moderators, this policy tells you so, and if it is private to the people in it, this policy tells you that too.
8. Where your data lives
On hardware we own and operate in the Netherlands. Your content is not parked on a third-party cloud, which means no cloud provider's staff, subprocessor chain, or foreign legal exposure sits between you and your data. Running our own machines is more work for us and it is the reason the service stays fast, but the privacy consequence is the one that belongs in this document: the list of parties with physical access to your data is us, and it ends there.
Retention, rights, and the edge cases.
The second half: how long things are kept, what you can demand, and what happens when something unusual occurs.
9. Cookies and local storage
The app sets what it needs to keep you signed in, and that is the extent of it. Your theme, appearance, and accessibility preferences live in your own browser's storage, where they belong. There are no third-party cookies, no cross-site identifiers, and no advertising or analytics cookies, which is also why you will not find a consent banner here: there is nothing running that would require one.
10. Retention and deletion
Your content stays until you remove it. When you delete a message, it is removed from the channel and from the recipient's side if it was a direct message, along with any media attached to it. When you delete your account, it is anonymized: your name and profile are removed, while the messages you already sent stay in their conversations attributed to a deleted, anonymous user, so other people's conversations stay intact. Channels keep only a bounded window of recent messages, so older content ages out over time. The technical records from section 3 rotate out on their own once they are no longer needed to run and secure the service.
11. Your rights
You can access, export, correct, and erase your data from within the app, whenever you can sign in. Because we are based in the Netherlands, European data protection law applies to everything we do with your data, and the rights it grants, such as access, rectification, erasure, and portability, are the same ones already wired into the app as buttons. Exercising them does not require a request letter or a proof-of-identity ritual, because you exercise them from inside your own authenticated account. If you prefer to invoke a right formally, email us and we will handle it that way, and you always keep the right to raise a complaint with your data protection authority. If you believe we hold something about you that the in-app tools do not reach, email us and we will resolve it.
12. Bans and your data
A server ban is a moderation outcome, not a data grab. It only stops participation in that community: you keep your account, every message you sent, and the direct messages you received, unless the sender removed them. While you can sign in, you can still export your data and delete your account, exactly as before. We think holding someone's history hostage as punishment is wrong, and our account ownership page explains that position in full. Nothing about a server ban changes what this policy promises you.
13. Legal requests
We respond to legal orders that are valid under the law that applies to us in the Netherlands, and we review what we receive rather than rubber-stamping it. Two structural facts shape what any such order can yield. First, we can only produce data we actually hold, and sections 3 and 4 keep that set small. Second, your data sits on machines we own and operate in the Netherlands, so there is no third-party cloud provider or subprocessor a request could route around us to reach. We do not build backdoors, weakened modes, or special access mechanisms for anyone.
14. If something goes wrong
No honest privacy policy pretends incidents are impossible. If a security incident affects your data, we investigate it, fix it, and tell the people affected what happened and what it means for them, rather than burying it in vague language. Our security page describes how the platform is defended day to day, and researchers who find a weakness can report it through our vulnerability disclosure process, which we treat as a service to users, not a threat.
15. Children
Vronify.chat is not directed at children. Do not create an account unless you are old enough to consent to the processing of your data under the law where you live. If we learn that an account belongs to a child who does not meet that bar, we delete the account and its personal data.
16. Changes to this policy
When this policy changes, the effective date at the top changes with it, and material changes are announced in the changelog rather than slipped in silently. We will not weaken a promise in this document and hope nobody notices; if a change would matter to you, the point of announcing it is that you get to notice. The current version is always at this address.
17. Contact
Privacy questions reach us at hello@vronify.chat. Security reports have their own process. For general help with the product, support is the faster route. We are a small team and the person answering privacy mail is one of the people who built the system, which tends to make the answers specific.
Numbers we intend to keep exactly where they are.
Most privacy pages hide behind adjectives. These are the figures behind ours.
Exercise your rights in minutes.
Every right in this policy is a control in the app, not a form and a waiting period. Here is the practical order to reach for them in.
Export a copy
Take an export of your data from your account settings, any time you can sign in. Do this first if you want a record of what exists before you start removing things.
Correct or trim
Edit your profile details, or delete individual messages. A deleted message disappears for everyone, media included: from the channel, and from the recipient's side if it was a DM.
Delete your account
Deleting your account anonymizes it: your name and profile are removed, while the messages you already sent stay in their conversations attributed to a deleted user. Deletion cannot be undone.
Ask us for the rest
If you believe we hold something the in-app tools do not reach, email hello@vronify.chat and we will resolve it. Formal requests under data protection law are welcome too.
Questions about this policy.
Do you sell my data or share it with advertisers?
No, and the business is built so the answer stays no. There are no ads on the platform, no advertisers to serve, and no data brokers in the picture, so your data has no buyer on the other side of us. Core features are free and stay free; if we ever charge for optional extras for power users, that is a price for features, never a price paid with your data.
Can Vronify staff read my direct messages?
As a matter of policy, no. Direct messages are private, and Vronify staff do not read private conversations. There is no admin view of your DMs built into the product, and reading private conversations is not part of how the service works.
If DMs are private, why are server channels visible to moderators?
Because public spaces need moderation to stay safe. If community channels were hidden from moderators, they could not review reported messages, automated filters could not run, and the community guidelines would be unenforceable. We chose to be honest about that trade-off instead of pretending you can have both: private conversations stay between the people in them, shared spaces get real moderation.
What happens to my data if I am banned?
A server ban only stops participation in that community. You keep your account, every message you sent, and the DMs you received, unless the sender removed them. While you can sign in, export and account deletion keep working exactly as before. The full reasoning is on the account ownership page.
How fast does deletion actually happen?
Immediately. Deleting your account is one action, with no thirty-day cooling-off. It anonymizes your account: your name and profile are removed, while the messages you already sent stay in their conversations attributed to a deleted user. That cuts both ways, and we say so plainly: deletion cannot be undone, so export a copy first if you might want your history later.
Do you use cookies or analytics?
Only what keeps you signed in, plus preferences like your theme stored in your own browser. There are zero trackers, zero analytics scripts, and zero third-party or advertising cookies anywhere, including on this marketing site. That is why there is no cookie banner: nothing here does what banners exist to warn about.
Will the upcoming bot engine change what is collected?
No. The bot engine, which is coming soon, runs on our own infrastructure and only acts inside servers where the owner switched it on. It sends nothing outside the platform, runs no third-party code, and has no access to direct messages, which stay private to the people in them. If a future feature ever changed what this policy covers, section 16 applies: the change would be announced, not slipped in.
Where do I send a formal privacy request?
Email hello@vronify.chat. Most requests are unnecessary in practice, because access, export, correction, and erasure are self-service in the app, but formal requests under European data protection law are handled through that address, and you always retain the right to contact your data protection authority.
Private by design, not by promise.
Everything this policy describes is already running. See what a chat platform feels like when nobody is watching over your shoulder.
Free to start. No trackers. Nothing to install.