privacy
The short version
ModRent processes information needed to provide accounts, packs, hosted Minecraft worlds, payments, referrals, and launcher access. We do not sell personal data or use advertising analytics. Hosting adds player identities, membership, gameplay timing, server files and logs, and account balances to the data we handle. Our sign-in, payment, hosting, and delivery providers also process information as described below.
Accounts, packs, and memberships
We store your WorkOS user ID, ModRent handle, account creation details, and records of acceptance of the terms and privacy notice. WorkOS handles sign-in and holds your email address and authentication information. ModRent accesses email addresses when needed for invitations, recipient verification, and support; the membership and invitation integration does not maintain a separate local email directory.
We store your in-progress pack, saved packs, names and descriptions, favourites, and publication or sharing settings. Public packs and shared recipes expose the information you choose to publish. A private pack used for a hosted world becomes available as that world's pinned client pack to authorised members.
For worlds, we process the owner, name, slug, connection address, pack configuration, memberships, roles, invitations, and invitation status. WorkOS stores the authoritative memberships and invitations. Other members can see member handles and roles; owners and operators can see pending invitation information and manage access within their permissions. Invitations can be sent to people without a ModRent account. If you receive an unwanted invitation, contact us to report it.
We process this information to provide the account and collaboration features you request under Article 6(1)(b) GDPR. For invitations involving people who have not registered, and to prevent abuse, we rely on our legitimate interests under Article 6(1)(f), subject to recipients' rights.
Minecraft identity and launcher access
You sign in with Microsoft through WorkOS. On your first Microsoft connection, our server uses the returned Microsoft authorisation with Xbox Live and Minecraft's services to obtain your Minecraft UUID and username. We associate that UUID with your ModRent account and assign a handle from the name if you do not have one. Later sign-ins reuse the saved identity. Authenticated gameplay can update our record of your Minecraft name.
We retain the Microsoft refresh token returned by WorkOS in server-side account storage for future Minecraft authorisation renewal. It is separate from browser-session tokens and is not sent to the browser or downloaded launcher. Intermediate Microsoft, Xbox and Minecraft access tokens are used during the identity exchange and are not retained. Direct Minecraft launching and use of the retained token to renew Minecraft access are not currently implemented. We never receive your Microsoft password.
The launcher reads the selected Minecraft UUID and username from local official-launcher account files and sends those profile details to ModRent for device authorisation. It does not send us your Microsoft email address, password, Minecraft access token, or unrelated Microsoft account details. Authentication for starting the game remains with the official Minecraft Launcher and Minecraft's services.
The launcher stores a ModRent device credential locally, scoped to the ModRent API. We store a hash of that credential with its account and Minecraft profile association. It allows the launcher to check membership, start authorised worlds, and prepare a connection. Short-lived browser challenges record your approval; the server matches your authenticated Minecraft UUID to the approved account and world when you join. These operations provide and secure the service you request under Articles 6(1)(b) and 6(1)(f) GDPR.
The launcher checks whether it can reach the world over IPv6. This is a connection test, not a scan of your network. If it fails, the launcher opens our network-help page. World hostnames include the owner's public handle and world slug; DNS providers and resolvers can see lookup requests, including world hostnames. A hostname alone does not grant gameplay access.
Hosted gameplay, files, and logs
Hosted worlds store saves, player data, configurations, installed mods, uploads, server logs, and recovery snapshots. Depending on Minecraft and the installed mods, these can include usernames, UUIDs, connection information, chat, commands, inventories, positions, and other gameplay records. World owners and operators can access world files and logs. Other players can see information Minecraft or the world's mods expose during play. Do not treat an in-world chat or world save as a private message to ModRent.
Our injected server agent reports authenticated player identities, connection sessions, join/leave and played-time information, ModRent command arguments and outcomes, and operational errors. It also reports world performance and resource measurements, including CPU, memory, tick timing, and JVM health. We use these to enforce membership, meter each player's usage, operate worlds, calculate shared resource rewards, and investigate failures. We do not rely on a player's locally reported UUID as proof of ownership.
The basis for providing hosted play and accounting is Article 6(1)(b) GDPR. Security, service reliability, and abuse investigation rely on our legitimate interests under Article 6(1)(f). World managers may make copies or configure mods that process additional data; they are responsible for their own use of it. Contact us if you need help with information held in a hosted world.
Payments, hosting time, gifts, and referrals
Stripe Managed Payments handles checkout as merchant of record and receives the payment, billing, and tax information needed for the purchase. ModRent does not receive full card numbers or card security codes. We keep an order tied to your account, the purchased bundle, payment and checkout references, confirmation status, amounts, currency and tax information returned by Stripe, and hosting time fulfilment records.
We maintain promotional and purchased hosting time balances, partially used hours, granted reward time, spending preferences, and usage records. Gifts record the sender, recipient, world context where applicable, amount and whether the hours were promotional or purchased. Referrals record a referral identifier, the referring and referred accounts, activation, and reward fulfilment. Signup and referral records prevent duplicate awards. An invitation or referral link does not give the sender access to your payment details.
These records support requested transactions and service delivery under Article 6(1)(b), applicable accounting and tax obligations under Article 6(1)(c), and fraud prevention and dispute handling under Article 6(1)(f). Stripe's own privacy notice explains its processing of payment information.
Cookies and storage on your device
modrent_sessionis a random sign-in session identifier. The related server record contains your user ID, handle, and WorkOS tokens. Session records have a 30-day lifetime that can be renewed during session refresh; signing out deletes the current session.modrent_auth_stateprotects browser sign-in against forgery and expires within 10 minutes.modrent_referralis set when you follow a valid referral link. It keeps the first referral identifier for up to 30 days so a later signup can be attributed and qualifying rewards can be granted. It is separate from sign-in and is not used for advertising.- Bunny's security service may set cookies to detect abuse and complete browser security challenges. WorkOS and Stripe may also use cookies on their own sign-in and checkout pages.
- Browser localStorage keeps your pack drawer, synchronisation state, and whether you have completed the introductory walkthrough. Signed-in pack data also synchronises with your account.
- The downloaded launcher stores installed pack files, launcher profiles, server-list entries, and its ModRent device credential on your computer. Signing out of the website does not revoke that separate device credential or remove downloaded files.
You can remove local data using your browser or operating system. Removing sign-in or device data may require you to sign in again. Contact us to revoke device access or request deletion of server-held information. We use referral attribution to administer the reward programme, not to track browsing across unrelated sites.
Providers and international transfers
Hetzner supplies our server infrastructure. BunnyWay d.o.o. (bunny.net) provides content delivery, DNS, and security services. They process network and service data needed to operate those services; CDN and DNS requests may be handled through their global networks.
WorkOS, Inc. provides sign-in, organisation memberships, invitations, and feature-flag checks. Microsoft provides Microsoft account sign-in, Xbox Live and Minecraft identity services; our server exchanges authorisation tokens with those services to obtain your Minecraft profile. Stripe provides Managed Payments, checkout, payment confirmation, and related payment services. Their infrastructure and subprocessors may process information outside the EEA.
Your browser loads fonts from Google Fonts and interface libraries from jsDelivr. Pack installers and the official launcher also make direct requests to Minecraft/Mojang, Modrinth, and mod or loader distribution services. Those services receive your IP address and request details and process them under their own privacy notices.
Where we transfer personal data outside the EEA, applicable data-protection safeguards are required, such as an applicable adequacy decision or Standard Contractual Clauses. You can contact us for information about the safeguards relevant to your data. We do not sell your data to these providers.
Retention and deletion
The server-side Microsoft refresh token remains with your account until removed or replaced; it has no automatic storage expiry, although Microsoft can expire or revoke it. Signing out deletes your browser session, not this account credential. Contact us to remove the retained credential or delete your account.
Browser linking requests expire after 15 minutes. An approved association can remain available for confirmation while its device authorisation is valid. Device authorisations expire after 90 days unless revoked earlier. Local files can remain on your computer after server-side authorisation expires.
Account content, confirmed identity links, world saves, and accounting records do not all have automatic expiry. They are kept to provide the ongoing service, maintain balances and transaction integrity, and meet applicable legal obligations. Snapshots retain a configured number of world versions rather than a fixed number of days. Removing live data does not necessarily remove it immediately from existing snapshots or copies downloaded by world managers.
Web, CDN, security, and Minecraft server logs have different rotation and retention arrangements. There is not a single 30-day deletion rule covering all of these records. We use operational logs for security, abuse prevention, troubleshooting, and service reliability under Article 6(1)(f), and retain relevant records where needed for an incident, dispute, or legal obligation.
To request account deletion, email hello@modrent.app from your sign-in address. We may ask for information needed to verify the request. We will address account and WorkOS data, identity links and device access, and the effect on owned or shared worlds. Payment, tax, fraud-prevention, or legal-claims records may need to remain after account closure; we will explain applicable exceptions. Deleting your account does not automatically remove other players' shared world content or downloaded copies.
Automated service controls
Software checks membership, credentials, available hosting time, and service limits, and can refuse a launch, deny admission, or disconnect a player. It also calculates balances, resource rewards, and referral eligibility. We do not use this data for advertising profiles. If you believe a restriction, charge, or reward calculation is wrong, contact us for review.
Your rights
Under the GDPR, you may request access, correction, deletion, restriction, and portability where applicable, and object to processing based on legitimate interests. Where processing relies on consent, you may withdraw it without affecting the lawfulness of earlier processing. Some rights are subject to legal conditions and exceptions. Contact hello@modrent.app; include a pack or world link if it helps identify the information concerned.
You may complain to the Dutch supervisory authority, the Autoriteit Persoonsgegevens, or another competent data-protection authority.
Changes to this notice
We will update this notice as the service changes and give appropriate notice of material changes. Acknowledging this notice is not blanket consent to unrelated uses of your data.