Privacy Policy

Who we are

Lampas 2 is a Minecraft server community run by the Lampas team. In this policy, “we” means the Lampas team and “the services” means this portal, the Lampas Launcher and the Lampas game server. You can reach the team through a staff member on the Lampas Discord server.

What we collect

When you sign in with Discord. Your Discord user ID, username, display name and avatar, and the IDs of your roles in the Lampas Discord server. We use the roles to decide whether you can sign in and what you can access. Discord also gives us your email address; we store only a one-way hash of it, never the address itself.

When you link your Minecraft account. You sign in with Microsoft and we receive your Minecraft Java username and UUID, plus Microsoft and Minecraft access tokens. We keep those tokens in our database so the Lampas Launcher can start the game signed in as you. Unlinking your account deletes them.

When you use the portal. A session record with your IP address and browser user agent, kept until the session expires or you sign out. When you sign in to the launcher, a short-lived sign-in code and a launcher session that lasts up to 30 days. Any YouTube or Twitch links you add.

When you link your YouTube channel through Google. You sign in with Google and allow us to view your YouTube account. We receive your Google account ID and Google access and refresh tokens. We don't ask Google for your name or email address; if Google includes them anyway, we don't use them. We use the tokens only to ask YouTube which channel is yours, and store that channel's ID, handle (or its title, if it has no handle) and link. For each of your live streams we store its video ID, link, title, and start and end times, which we get from YouTube API Services when YouTube tells us your channel published or updated a video.

When you link your Twitch account. You sign in with Twitch and we receive your Twitch user ID, login and display name. We revoke and delete the Twitch sign-in tokens as soon as the account is recorded. We ask Twitch only to identify your account; if its sign-in token includes your email address, the address is deleted with that token. Twitch then tells us when you start and stop streaming, and for each of your live streams we store its stream ID, your channel link, its title when Twitch gives it to us, and its start and end times.

On the game server.

• Server logs, which record when you connect and disconnect (including your IP address), chat messages and commands.
• Your world data: your inventory, position, builds and other in-game state, saved in the world files and in our gameplay database, keyed by your Minecraft UUID.
• Voice chat is relayed through the server in real time. We don't record it.
• Who is online right now. The portal reads this from the server and doesn't store it.

When staff moderate the server. Records of whitelist, operator and ban changes, including ban reasons and banned IP addresses, and a log of the commands staff send to the server.

The Lampas Launcher

The launcher runs on your computer. You install it from the Microsoft Store or from GitHub. It stores its sign-in and your Minecraft token on your device using your operating system's secure storage. It keeps logs on your device with tokens and passwords removed, and it doesn't send usage data or crash reports to us. It turns off Fabric's telemetry when it starts the game.

To install and update the game it downloads from Mojang, Fabric and the Lampas portal, checks GitHub for launcher updates, and loads player head images from mc-heads.net.

How we use it

• To sign you in and decide what you can access.
• To prove you own the Minecraft account you link, add it to the server whitelist, and let the launcher start the game as you.
• To run the game and keep your progress.
• To keep the server safe: moderation, investigating cheating and abuse, and fixing problems.
• To show in game that you are live, with a link to your stream, while you stream on the YouTube channel or Twitch account you linked.
• To show you in the player directory to other signed-in members.

We don't sell your data or use it for advertising.

Who can see it

Other signed-in members can see your display name and avatar, your Discord username, your Minecraft username and UUID, whether you are staff, your channel links, and whether you are online. Staff can also see moderation records and your account details. People who aren't signed in can't see any of it.

Services we rely on

These services process data for us or receive it when you play:

• Discord, for sign-in and role checks.
• Twitch, to learn which Twitch account is yours and when you go live; the Twitch Privacy Notice applies to that.
• YouTube API Services, to look up your YouTube channel and check whether your streams are live. Google receives our requests about your channel and its videos; the Google Privacy Policy applies to that. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
• Microsoft, Xbox Live and Mojang, to verify your Minecraft account. The portal also looks up linked players' Minecraft UUIDs with Mojang to show their skins.
• Railway, which hosts the portal, its database and file storage.
• Bloom.host, which hosts the game server, its world files and its logs.
• PronounDB: the game server looks up your Minecraft UUID there to show the pronouns you set on PronounDB.
• mc-heads.net: the launcher loads player head images from there by Minecraft UUID.
• The Microsoft Store, which distributes the launcher. Microsoft handles Store downloads and updates under its own privacy statement.
• GitHub, which hosts launcher releases.

Some mods in the game connect to their own services from your computer (for example, Figura for player avatars). Their own privacy policies apply to that.

Sharing Google user data

Google user data means what we get when you link your YouTube channel through Google: your Google account ID, your Google tokens, your channel's ID, handle (or title) and link, and the video ID, link, title and times of each of your live streams.

We don't sell Google user data, use it for advertising, or use it to train AI or machine-learning models. We share or disclose it only in these ways:

• With other members. Signed-in members see your channel link and handle in the player directory. While you stream, players on the game server see that you are live and can open your stream's link.
• With our hosting providers, which store and process it only to run the services. Railway hosts the portal, the database that holds this data, and the portal's service logs. Bloom.host hosts the game server: while you are live and on the server, the portal sends it your stream's link. The game server keeps the link only in memory and drops it when we see the stream end, when you leave the server or after 12 hours.
• With Google. Google receives your tokens when we ask YouTube which channel is yours, your channel ID when we ask YouTube to tell us about its new videos, your video IDs when we check whether a stream is live, and a request to revoke our access when your channel is unlinked.
• When the law requires it. We disclose it if we must to comply with the law or a valid legal order.

We don't transfer it to anyone else.

How we protect Google user data

• Encryption in transit. The portal is served over HTTPS, and plain HTTP requests are redirected to HTTPS. The portal reaches Google's APIs over HTTPS. The database can't be reached from the internet; the portal connects to it over our host's private network, which encrypts the traffic. The portal sends your stream's link to the game server over an encrypted (TLS) connection that requires a secret key and accepts connections only from our host's outbound addresses for the portal.
• Encrypted tokens. Your Google access and refresh tokens are encrypted (XChaCha20-Poly1305) before they are stored. The key is kept in our host's environment settings, separate from the database. We don't keep the ID token Google sends with them, which only identifies your Google account; it is deleted within about a day.
• Tokens stay on the server. Only the portal's server uses your tokens, and only to ask YouTube which channel is yours and to revoke our access when your channel is unlinked. The portal never sends them to a browser or app, and staff can't see them in the portal.
• Minimal access. We ask Google only to identify your account and to view your YouTube account (read-only), not for your name or email address. Only you, signed in with Discord, can link your Google account to your Lampas account.
• Restricted access. Only the Lampas team members who run the portal can access our hosting account and the database. Database credentials and API keys are kept in the host's environment settings, not in our code.
• Limited retention. We check your channel with YouTube about every 25 days and delete live stream records within 30 days, as described under How long we keep it.
• Revocation and deletion. When you unlink your channel, the portal asks Google to revoke our access, then deletes your tokens, channel ID and live stream records straight away.

How long we keep it

Your account and its records stay while your account exists. Portal and launcher sessions stop working when they expire. World backups made during server updates replace older ones; we keep the latest two. We haven't set a fixed deletion schedule for server logs and moderation records yet; we will add one to this policy, and if you ask us to delete your data before then, we will.

Live stream records are deleted within 30 days after the stream ends, and our log of the in-game live status commands within 30 days after each command. We keep your Google tokens while your channel is linked, and use them about every 25 days to check with YouTube that the channel is still yours. If that check can't be done within 30 days, for example because you removed our access in your Google Account, we unlink the channel and delete the tokens. The portal's service logs, which our host keeps for a limited time, also record the YouTube video and channel IDs and Twitch user and stream IDs it handled. Your Twitch user ID, login and display name stay while your Twitch account is linked.

Your choices and rights

• Unlink your Minecraft account or remove your channel links at any time on your dashboard.
• Unlinking your YouTube channel on your dashboard revokes our Google access and deletes your Google tokens, YouTube channel ID and live stream records straight away. You can also remove our access in your Google Account settings; we then unlink the channel within 30 days.
• Unlinking Twitch on your dashboard deletes your Twitch user ID, login and Twitch live stream records straight away and stops the notifications from Twitch.
• Ask a staff member on the Lampas Discord server for a copy of your data, to correct it, or to delete your account. Deleting your account also removes you from the server whitelist. We delete data we got from Google and YouTube within 7 days of your request.

Lampas is run from the Philippines, and the Data Privacy Act of 2012 gives you the right to be informed, to access, correct and delete your data, to object to processing, and to complain to the National Privacy Commission. People elsewhere may have similar rights where they live.

Age

Lampas 2 is an 18+ event. We don't knowingly collect data from anyone under 18; if we learn that an account belongs to someone under 18, we remove it and delete its data.

Changes

When this policy changes we update the version and date at the top and announce it on the Lampas Discord server.