Privacy Policy

1. Who we are

OmniClient ("OmniClient", "we", "us") makes the OmniClient mod and the OmniClient Launcher for Minecraft: Java Edition, and runs this website. This policy explains what information each of them handles, where it is kept and who it is shared with.

OmniClient is in early access. This policy describes how the Software is built today. If that changes before or after release, we'll update this policy first (see Changes).

2. This website

This section covers this website, omni-client.com. It used to be at omni.mine-dream.org, which now forwards here; older versions of the mod and launcher still check that address for updates. The OmniClient Store has its own section below.

• One cookie, shared with the store; no analytics or trackers. This website sets no cookies of its own, doesn't use analytics, and doesn't load advertising or tracking scripts. When you sign in to the OmniClient Store (with Microsoft, or from the game), its sign-in cookie, omni_sid, is for omni-client.com as well, so you're signed in on both. Our server passes it on to the store, on the same computer, to show your Minecraft name and face, and while OmniClient is in early access to check that your account may download it. Fonts, images and scripts are served from this site, and your face from the store.
• Discord. The home page shows the OmniClient Discord server's name, who's online (their Discord names and avatars) and an invite. Your browser loads these from Discord's public server widget (discord.com, and avatars from cdn.discordapp.com), without sending cookies, so like any website Discord sees your IP address and browser details; that's handled under Discord's privacy policy. Nothing else on this website comes from another company.
• Downloads. The launcher and the mod are downloaded from this website (/downloads), and they check it for updates (below). While OmniClient is in early access, and for the Early update channel's files (/downloads/early/) always, our server asks the store about each download, with your sign-in cookie or the launcher's and the mod's download key, and serves it only to players with early access. Neither keeps a record of who downloads or checks.
• Hosting logs. The company that hosts this website may automatically record standard request details, such as your IP address, browser type, the page requested and the time, to deliver the site and protect it from abuse. Those logs are kept under the host's own policies. We don't use them to identify or profile visitors.

3. The OmniClient mod

The mod has no analytics or telemetry. Its only network connections of its own are for updates (to this website), early access and bans, cosmetics, emotes, the Servers page's list, the main menu's tourney and World Sharing (to the OmniClient Store, to Mojang's session server to sign you in to the store, and to your router while you share a world), all described below. It sends nothing else to us or anyone else.

It stores its files on your computer, in a folder shared by every Minecraft version and instance:

If your launcher is sandboxed and can't reach your home folder (for example a Flatpak launcher), the mod keeps the same files in a .omni folder inside the game instance instead.

Updates

When the game starts, and then every minute while it runs, the mod reads a short file on this website, omni-client.com/downloads/versions.txt, which lists the newest version on each update channel; the mod follows the one picked in the launcher. If there's a newer one, it downloads it from the same place, checks it against the checksum in that file, uses it from the next start, and tells you in the game. If your account has early access, the requests carry your download key (~/.omni/download.key, see Cosmetics below), so this website can check with the store that your account may have early builds (while OmniClient is in early access, and on the Early update channel); otherwise the request only identifies itself as OmniClient and nothing about you or your account is sent. To turn updates off, add noupdate to the agent: -javaagent:/path/to/omniagent.jar=noupdate.

Early access and bans

When the game starts, the mod signs in to the OmniClient Store the way it does for cosmetics (below), then asks the store every 10 seconds while you play whether your account can use OmniClient: whether OmniClient is in early access (only open to some players) and your account has it, and whether your account is banned from OmniClient. If it can't, every OmniClient feature stays switched off and the mod's menu says why. These checks send only your sign-in token; the store doesn't log them. The answer is remembered in ~/.omni/clientconfig.json. The checks happen even with the Cosmetics module off. If signing in fails, the mod only asks whether OmniClient is in early access, which carries nothing about you, and tries signing in again a few minutes later.

Cosmetics

Cosmetics and badges come from the OmniClient Store. The mod talks to it like this:

• Signing in. When the game starts (and when you open the Cosmetics page, if you're signed out), the mod gets a one-time code from the store and asks Mojang's session server to confirm your account, using the game's own login. It's the same request Minecraft makes when you join a server. The store then asks Mojang whether that happened. The store learns your Minecraft name and UUID; your login token only ever goes to Mojang. If your account has early access, the store also gives the mod a download key for its update checks, kept in ~/.omni/download.key for up to 30 days; it's deleted if your account no longer needs one.
• What you wear. Once you're signed in, the mod tells the store which cosmetics and badge you picked, so other OmniClient players see them. It also gets back what you own and what the rest costs, and while you stay signed in it asks again every few minutes, so anything you no longer own comes off. A copy of what you own is kept in ~/.omni/clientconfig.json, so your cosmetics show before you sign in again.
• Other players. To show the cosmetics and badges other OmniClient players wear, and the Omni logo beside the nametags and player-list names of players who use OmniClient, the mod sends the store the Minecraft UUIDs of the players loaded around you and in the server's player list (Tab). The store answers which of them it knows as OmniClient players (anyone who has signed in to it from the mod), and what they wear. A UUID is the public ID of a Minecraft account, which servers already share with everyone in the game. The mod doesn't send the server you're playing on or your chat. It asks about each player at most every 10 minutes, and other players' OmniClient does the same for you. We use these UUIDs only to answer, and don't log or keep them, or record who asked about whom.
• Opening the store. The store buttons on the Cosmetics page open a one-time sign-in link in your browser.

Like any web request, these requests reveal your IP address, and they name the mod's and Minecraft's versions.

Turn off Show Other Players' Cosmetics (Client → Cosmetics in the mod's menu) to stop the lookups of other players. Switch off the whole Cosmetics module and the mod makes no cosmetics connections; it still checks for updates, early access and bans.

Emotes

Emotes are animations your player plays (the emote wheel, B by default). They work through the OmniClient Store too:

• Playing one. When you play an emote, the mod signs you in (as for cosmetics) and tells the store which emote you started, and tells it again when you stop. The store keeps this in memory only, never on disk, and forgets it when you stop or after 2 minutes at most.
• Other players' emotes. While OmniClient players are on your screen, the mod asks the store about every 1.5 seconds which of them are playing an emote, by their Minecraft UUIDs. It asks only about players the store said use OmniClient, and nothing while there are none. As with cosmetics, we use these UUIDs only to answer, and don't log or keep them, or record who asked about whom.

Turn off Show My Emotes To Others (Client → Emotes in the mod's menu) and your emotes play only on your screen, without telling the store. Turn off Show Other Players' Emotes to stop asking about other players, or switch off the Emotes module for neither.

Servers page

The Servers page in the mod's menu lists servers we pick (Server Discovery) and our partnered servers. When you open it, the mod downloads that list from the OmniClient Store (store.omni-client.com/api/v1/servers), at most every few minutes, and the servers' pictures from the same place. A server without a picture of its own shows the icon it shows in Minecraft's server list; the OmniClient Store asks the server for it, so your game doesn't. These requests don't sign you in and carry nothing about you or your account beyond the IP address any web request reveals; the store doesn't log them. OmniClient staff (SuperAdmins whose Discord account is linked to their Minecraft account) can also change the list from this page; for them, the store's answer to their sign-in says so, and their changes are sent signed in, with any picture they pick. The mod doesn't contact the listed servers itself: only joining one, or adding it to your server list (where Minecraft shows its status as for any server), does that. Partnered servers are servers we have an arrangement with; they're marked as partners.

Tourneys

While Minecraft's main menu shows, the mod asks the OmniClient Store (store.omni-client.com/api/v1/tourney) whether a tourney is coming up, at most once a minute, and shows a banner from a day before it starts until it ends. The answer is the tourney's server address and when it starts and ends. These requests don't sign you in and carry nothing about you or your account beyond the IP address any web request reveals; the store doesn't log them. The mod doesn't contact the tourney's server unless you press Join. OmniClient staff (SuperAdmins whose Discord account is linked to their Minecraft account) set tourneys up from the mod's Tourney page; their changes are sent signed in, and the store keeps the server address, the times and which staff account set it up.

Hosting a tourney (OmniClient staff). OmniClient SuperAdmins can host a minigame tourney on their own computer, from the OmniClient Launcher's Tourneys page or from the mod's Tourney page; the mod asks the launcher that started the game over a connection inside your computer, which nothing leaves. The launcher first asks the OmniClient Store, signed in, whether your account may host. It runs Minecraft's server from Mojang (after you agree to the Minecraft EULA) and, if you leave it on, asks your router to open the server's port with UPnP while you host, and for your public IP address; the port is closed again when you stop. The launcher then lists the tourney with the OmniClient Store, signed in: the game mode, the player limit, the reward you typed, when it starts and how long it lasts, the port, and your public IP address (from your router, or as the store sees your request). The store keeps these with your Minecraft name while the tourney runs, shows the tourney on everyone's main menu with your name, the game and your reward, and gives the address only to signed-in players who join it from the main menu or with its invite code; OmniClient never shows them the address, though anyone who joins a server can find its address with network tools. While you host, the launcher checks in with the store every minute and tells it the winner of each game, by their Minecraft name and account ID; the winner gets the Champion cape and badge. Players in your tourney see and talk to each other as on any Minecraft server, and you can read the server's console.

World Sharing

World Sharing lets friends join the singleplayer world you're in. When you start it, the mod opens the world to LAN (as Minecraft's Open to LAN does), asks your router to forward that port with UPnP and for your public IP address, and lists the share with the OmniClient Store, signed in: the port, the world's name and your public IP address (from your router, or as the store sees the request). The store gives it an invite code and keeps these with your Minecraft name while you share; it gives the address only to signed-in players who type the code, and OmniClient never shows it to them, though anyone who joins a server can find its address with network tools. While you share, the mod checks in with the store every minute; stopping, or leaving the world, ends the share and closes the port on your router. If you lead a party, it follows you in: the launcher sends the invite code (not the address) to your party through the OmniClient Store, as it does a server for a party trip. Players who join can do what Open to LAN lets them do in your world.

Minecraft itself, Microsoft's and Mojang's services, and any multiplayer server you join handle your information under their own terms and privacy policies, not this one.

4. The OmniClient Store

The OmniClient Store, at store.omni-client.com, sells cosmetics and the Omni+, Omni Pro and Omni Elite plans, and answers the mod's cosmetics requests. It's the only part of OmniClient that keeps information about you. It keeps:

Friends, chat and parties

The OmniClient Launcher's Social page, and the Social page in the game's OmniClient menu (when the launcher started the game), let you add friends by their Minecraft name, chat with them, and play together in parties. The launcher signs in to the store the same way the mod does: your password and sign-in token go only to Mojang. If you've added several Microsoft accounts to the launcher, it signs each of them in, so you can read and answer every account's messages; each account has its own friends, chats and party. The launcher doesn't tell the store that the accounts are yours together, though they sign in from the same internet address; the store doesn't link them.

• Who can reach you. Only friends can message you and invite you to parties, unless you change that to everyone in Social's settings. Anyone who has signed in from OmniClient can send you a friend request by your Minecraft name. Block a player to stop requests, messages and invites from them both ways.
• Messages go to the friend you wrote to, or to everyone in your party. The store keeps them for 30 days, then deletes them. Your launcher keeps every message it receives or sends on your computer, in ~/.omni/launcher/social/, until you delete it. Your friends' launchers do the same with your messages to them.
• End-to-end encryption. Each computer your launcher runs on makes its own encryption key for each of your accounts; the private part stays in ~/.omni/launcher/social/ on that computer, and only the public part goes to the store, so others can encrypt to it. When everyone in a chat has an up-to-date launcher, your launcher encrypts each message (GIFs included) for the people in the chat and your own computers before sending it, and the store keeps and delivers text it can't read: not even OmniClient staff can. A chat shows a lock when it's encrypted; if someone's launcher can't open encrypted messages yet, the chat says so and its messages go unencrypted, as before. The store still sees who wrote to whom, and when.
• GIFs come from GIPHY. When you search for one, your launcher sends the search to the store, which asks GIPHY, and the GIFs are loaded from the store too, which fetches each from GIPHY once and keeps a copy. So GIPHY sees the store's searches, not your address or who searched. The store keeps recent searches in memory for 10 minutes to answer repeats, and copies of GIFs (not who sent them) until it needs the space.
• Chat filter. Hiding swearing and slurs in messages you receive happens in your launcher, on your computer; nothing about it is sent anywhere.
• Online and activity. Your friends and party see whether you're online, and what you're doing: "In the launcher", or the version or modpack you're playing (not which server). While the launcher is open, each of your accounts shows as online to its own friends: the one you play with shows what you're playing, the others "In the launcher". The store keeps this in memory only, while you're online.
• Parties. When the party's leader joins a server, the store tells the other members' launchers the server's address, the game's version and, if the leader shares it, their modpack, so the members' games can follow. Each member's game counts down first, and they can stay instead. A modpack from Modrinth or CurseForge is shared as its name and version. A modpack the leader made is shared as its list of mods hosted on Modrinth and its configs, which the store keeps for 24 hours. Mod files that are only on the leader's computer aren't shared.
• Reports. Reporting a player sends their name, your reason and a copy of the message you reported (if any) to OmniClient staff, who see them in the OmniClient Discord admin menu. The store can't read an encrypted message, so reporting one sends its text from your launcher, marked as coming from you.

Signing in

Sign in on the store or this website with Microsoft, or from the game (section 3). With Microsoft, you sign in on Microsoft's own page, so your password never reaches us. Microsoft then gives the store a one-time sign-in for Xbox Live, which the store uses straight away, with Xbox Live and Minecraft's services, to learn which Minecraft account you have: its UUID and name. The store doesn't keep these tokens, and doesn't learn your email address or anything else about your Microsoft account.

What others can see

Every OmniClient player can see the cosmetics you wear and your badge. That's what they're for. A plan's badge shows that you have that plan; pick None on the Badges tab to hide your badge. Once you've signed in from the mod, other OmniClient players' games can tell that you use OmniClient, so they know to ask about your emotes, and they see the emotes you play unless you turn off Show My Emotes To Others. If you buy someone a gift, they see your Minecraft name with it. Your purchases, payments and Discord account aren't otherwise shown to anyone.

Payments

Purchases are sold through Onelink, Stripe's merchant of record service, on Stripe's own checkout page, so your card details never reach us. To work out tax and send receipts, Onelink asks for your name, email address and billing address, and keeps them and your payment details under its own privacy policy; it also handles managing and cancelling plans at link.com. We can see some of these details in Stripe's dashboard, for example to help with a refund. We don't copy them into the store.

Discord

Linking Discord is optional. When you link, Discord tells us your Discord user ID and name (nothing else: no email, no servers list). Our Discord bot then checks whether you're in the OmniClient server and boosting it, and gives you the roles that go with your perks and plan. It checks again every few hours while you're linked. Unlink on the store's Discord page at any time; the roles the store gave you are removed.

Your face

While you're signed in, the store shows your skin's face next to your name. The store fetches your public profile and skin from Mojang's session server itself, using your UUID, and keeps the face for up to 6 hours. Your browser loads it from the store, not from Mojang or anyone else.

Cookies

The store sets one cookie, omni_sid, which keeps you signed in for up to 30 days, on the store and on omni-client.com (section 2). While you sign in with Microsoft, a second one, omni_ms, ties Microsoft's answer to your browser for up to 10 minutes. They're needed for signing in to work. There are no other cookies, analytics or trackers, and store pages load nothing from other websites; Stripe's checkout and Discord's sign-in are pages on their own websites.

How long we keep it

• Sign-in tokens expire within 24 hours, download keys within 30 days, one-time sign-in links within 5 minutes, unfinished Microsoft sign-ins within 10 minutes, and website sessions after 30 days or when you sign out.
• Which emote you're playing is kept in memory only, until you stop or for 2 minutes at most.
• Direct and party messages are deleted after 30 days, invites to parties after 10 minutes, and modpacks shared for a party after 24 hours. Reports are kept until staff have handled them, then for 90 days.
• Your skin's face is kept for up to 6 hours, then fetched again from Mojang the next time it's shown.
• Purchase records are kept as long as tax and accounting law requires, even if you ask us to delete your other data.
• Everything else is kept while you use the store, and deleted on request (see Your choices and rights).
• The store doesn't keep access logs. Errors are logged without the contents of requests.

5. The OmniClient Launcher

Signing in with Microsoft

The launcher uses Microsoft's device-code sign-in. You enter a short code at microsoft.com/link in your own browser, so your password is only ever entered on Microsoft's website. The launcher never sees it. After you approve, the launcher talks directly to Microsoft, Xbox Live and Minecraft services to confirm that the account owns Minecraft: Java Edition. We don't run any server in between.

For each account, the launcher stores the following on your computer only, in ~/.omni/launcher/accounts.json:

• your Minecraft username and UUID, and your Xbox user ID;
• the access token and refresh token the game needs to launch and to keep you signed in.

On Linux and macOS this file is created so that only your user account can read it. On Windows it sits inside your user profile. Offline accounts store only the name you choose and an offline UUID made from it. Removing an account in the launcher deletes it from the file.

Player heads

To show your account's avatar, and your friends' faces on the launcher's and the game's Social pages, the launcher fetches the public profile and skin of each from Mojang's session server and caches the faces in ~/.omni/launcher/cache/faces/. The game gets the faces from the launcher, over the connection that stays inside your computer.

Discord status

If the Discord app is running on your computer, the launcher tells it what you're doing so Discord can show it on your profile, the way it shows other games you play: "In the launcher", or the Minecraft version and mode (for example "OmniClient · Sodium") or the modpack's name, and how long you've been playing. Discord shows the OmniClient logo with it, which Discord loads from this website, or for a modpack from Modrinth or CurseForge, the modpack's icon, which Discord loads from that service. Your Minecraft name, account and the servers you join aren't included.

The launcher passes this only to the Discord app on the same computer; the launcher itself sends nothing over the internet for it. Discord then shares your status with the people who can see your activity, under Discord's own privacy policy. The status ends when you close the launcher. To stop it, turn off Settings → Discord in the launcher, or hide your activity in Discord's settings.

Split screen

The mod's Split Screen module opens a second copy of your game for a second player, signed in with another account you've added to the launcher. So that each player controls only their own game, the launcher reads your keyboards and mice while split screen is being set up and while it runs. First it learns which keyboard and mouse belong to each player, when each player presses a key and clicks. Then it passes each player's key presses, mouse movement, clicks and scrolling to that player's game. While split screen runs, those keyboards and mice are reserved for the two games, so the rest of your computer doesn't receive their input.

This input goes only to the two games, over a connection that stays inside your computer. The launcher doesn't store it, log it or send it anywhere else, and the games use it the way they use any key press or click. The launcher stops reading your keyboards and mice as soon as split screen ends: when you press Ctrl+Alt+End, stop it in the game, or close either game or the launcher. When player 1 presses End to use their desktop for a while, the launcher stops reading player 1's keyboard and mouse until End is pressed in player 1's game again. On Linux, reading keyboards and mice needs your user account to be in the input group, which you add yourself. Membership lets the programs you run read those devices, so you can leave the group when you're not using split screen.

Updates

When it opens, and every minute while it runs (in the background too), the launcher reads omni-client.com/downloads/versions.txt on this website. If there's a newer launcher, it downloads it to ~/.omni/launcher/updates/ and uses it the next time it opens; if there's a newer OmniClient, it replaces ~/.omni/omniagent.jar. It also downloads OmniClient from there the first time you play it, if it isn't on your computer yet. Settings → Updates picks the update channel: Release, Beta, Alpha, or Early for players with early access, which the launcher learns from the store when it signs in (/cosmetics/me). If one of your accounts has early access, these requests carry the download key the store gave it (~/.omni/download.key), which the launcher gets when it signs in to the store; otherwise they send nothing about you or your accounts. Turn updates off in Settings → Updates.

Downloads

To sign you in and set up a game, the launcher connects to these services:

Some of these services deliver files from their own download hosts. For example, Adoptium's Java downloads are served from GitHub, and loader libraries can come from Maven repositories such as Maven Central.

Like any web request, these connections let each service see your IP address and basic technical details, such as the name and version of the launcher making the request. Each service handles that information under its own privacy policy. Apart from this website, which keeps no record of these requests, we don't operate any of these services and receive none of this information.

Files on your computer

Everything else the launcher keeps, including game instances, downloaded game files, Java runtimes, its cache and settings.json, lives in ~/.omni/launcher/ and is never uploaded anywhere.

6. If you contact us

If you email us, we receive your email address and whatever you choose to include. We use it only to reply to you, and keep it only for as long as the conversation needs.

7. What we don't do

We don't sell or rent personal information, share it with advertisers, show ads, or build profiles of players. Apart from what the OmniClient Store keeps (section 4) and emails you send us, we don't hold personal information about you. The services we use to run OmniClient handle some of it for us: Stripe (payments), Discord (if you link it), Mojang (confirming accounts and fetching skins), GIPHY (GIF searches, which the store makes, never with your address) and the companies that host and protect our websites.

8. Children

The OmniClient Store is for people who can make purchases where they live. If you're younger, ask a parent or guardian before buying anything. The store keeps only the Minecraft details described in section 4, which are the same for every player. Sign-in for children's Minecraft accounts happens through Microsoft and is covered by Microsoft's family settings and policies. If you believe a child has given us personal information, contact us and we'll delete it.

9. Your choices and rights

Because the Software keeps your information on your own computer, you're in control of it:

• Remove an account in the launcher to delete its tokens.
• Turn off Show Other Players' Cosmetics in the mod's menu (Client → Cosmetics) to stop the mod asking the store about the players around you and in the player list, or switch off the Cosmetics module to stop its cosmetics connections. Show Omni Logo there hides the logo beside names.
• Turn off automatic updates in the launcher's Settings → Updates, and for the mod with the agent option noupdate.
• Pick None on the Badges tab of the Cosmetics page to hide your badge.
• Turn off Show My Emotes To Others or Show Other Players' Emotes (Client → Emotes), or the whole Emotes module.
• Unlink your Discord account on the store's Discord page.
• Turn off Settings → Discord in the launcher to stop showing what you're playing on Discord.
• End split screen (Ctrl+Alt+End, or stop it in the game) to stop the launcher reading your keyboards and mice.
• Choose who may message you and invite you to parties (friends or everyone) in the launcher's Social page; block players; leave a party; delete ~/.omni/launcher/social/ to remove your chat history from your computer.
• Delete ~/.omni/launcher/ to remove all launcher data, including accounts, instances and downloads.
• Delete ~/.omni/ to remove everything OmniClient has stored.

Depending on where you live, for example in the EU, the UK or California, you may have the right to access, correct or delete personal information an organisation holds about you, and to complain to your local data protection authority. The personal information we hold is what the OmniClient Store keeps (section 4) and emails you've sent us. To ask for a copy or for it to be deleted, contact us and tell us your Minecraft name. Purchase records we must keep by law are kept until we no longer have to.

10. Security

The store keeps sign-in tokens and sessions only as one-way hashes, and never sees your Minecraft login or card details. Your launcher sign-in tokens are stored on your computer, so anyone with access to your user account on that computer could use them. Keep your device and user account secure, and remove accounts from the launcher on computers you share. Downloaded Java runtimes are checked against the checksum Adoptium publishes before they are used.

11. Changes to this policy

If we change how OmniClient handles information, for example by adding an online feature, we'll update this page and the effective date at the top before the change ships. Significant changes will also be announced on this website.

12. Contact

Questions about privacy, or a request about your information? Email us at [email protected].