Last updated: 18.09.2026
I built Cycasc because I believe something that should be obvious but clearly isn't in 2026: your data belongs to you. Not to a corporation in Silicon Valley. Not to some ecosystem that locks you in. Not to an ad network that profiles you while you sleep.
So I host my own services. I run my own servers. I keep my data where I can see it, touch it, and - if things go wrong - fix it myself. And I let my friends and acquaintances do the same. No strings attached. No "freemium" upsell. No "your data fuels our AI model". Just me, some hardware, and a lot of caffeine. ☕
This page is me telling you, in plain language, what happens to your data when you use my services. No legalese. No "we may, in certain circumstances, potentially ...". Just the truth.
My name is Victor. I run Cycasc as a private, non-commercial project. I don't sell anything. I don't run ads. I don't have a "Data Science Team". There's no board of directors. There's me, two servers in two different buildings, and a lot of open-source software.
If you have questions, complaints, or just want to argue about the best file system (XFS, obviously), you can reach me at the end of this page.
Let's get the important stuff out of the way first:
The one exception: my TeamSpeak server runs on a virtual host provided by Linode (Akamai) in Frankfurt. That means Linode handles the network-level hosting for that specific service. I don't share any of your data with them beyond what's necessary to run the server. They are a processor, not a partner.
I'll be honest: it depends on which service you use. Here's the breakdown:
When you use Nextcloud, I store whatever you put there: files, photos, contacts, calendars, notes - you decide. I also store your account details: username, email address, and a password hash (I never see or store your actual password). If you enable two-factor authentication, I store the relevant keys.
Your in-game username, your IP address (in server logs), and chat history if you talk. Also I can see your in-game actions (like destroying blocks or opening chests). I'm not recording your every step in the overworld.
If you contribute to any pages, I store your username and the pages you write/edit. Public pages are, well... public.
Your nickname, IP address (in logs), and voice data (which is transmitted but not recorded).
Standard server logs: your IP address, browser type, timestamp, and which page you visited. That's it. No cookies, no fingerprinting, no "personalized experience".
These are primarily for my own use. If I let someone in, the same principles apply: I store what the service needs, I don't share it, and I delete it when asked.
I know, I know. You came here for the fun parts. But the GDPR is the GDPR, and I'd rather be upfront than get a letter from a supervisory authority.
Legal basis: When you create an account or use one of my services, you're doing so voluntarily. The legal basis for processing your data is your consent. You can withdraw that consent at any time by asking me to delete your account and data. No hard feelings.
For server logs (IPs, timestamps, etc.), the legal basis is my legitimate interest in keeping my servers secure, troubleshooting issues, and detecting abuse. I don't use logs for anything else.
Purpose limitation: I use your data only to provide the specific service you're using. Your Nextcloud files don't end up in my Minecraft logs. Your Matrix messages don't get cross-referenced with your Jellyfin watch history. (Even though, technically, I could. I won't.)
I'm not a corporation with a $50M security budget. But I take this seriously, and here's what's actually in place:
What I'm NOT doing (transparency time): I do not use full-disk encryption (LUKS/dm-crypt) on my storage. The data is protected by physical access control, network segmentation, and the fact that these servers are in a locked building in Germany - but if someone got physical access to the drives, the data would be readable.
Short answer: as long as you want me to, and a little longer for backups.
I do not have an automatic inactivity purge. If your account sits idle for three years, it's still there when you come back (unless you ask me to delete it, of course).
I hope it never happens. But if it does - if there's a breach, a leak, a "oops, I left a port open" situation - I will:
I'd rather have your trust and an honest "hey, this happened, here's what I'm doing" than a polished corporate statement that says "we take privacy seriously".
My services are not designed for children under 16 (the GDPR age of digital consent in Germany). I don't knowingly collect data from kids. If you're a parent and your kid signed up for my Minecraft server without telling you - well, that's a conversation for you two. But if you want their data removed, email me and I'll handle it.
I might update this page if I add new services, change my setup, or if the law changes. If I do, I'll update the "Last updated" date at the top. I won't email you a 4-page legal document. I'll just... update the page. You came here, you can come back.
Look, I can lock down my servers all I want, but the weakest link in the chain is usually the password you set to "password123". So:
You can reach me through any of these:
I'm one person, so I might not reply in 5 minutes like a corporate chatbot. But I will reply. Promise. 🤞
This is not a law firm's document. This is me, Victor, telling you how I handle your data. If you want the full legal citation for every sentence, talk to a lawyer. But I hope you didn't need to.
Now go use my services. And please, for the love of all that is holy, use a password longer and more complex than "bigdick2026". 🙃