Privacy Statement
What happens to data when you visit Softlight or use the Windows launcher.
1. Operator and scope
MailoDataCenter, based in the Netherlands, operates Softlight and is responsible for personal data it processes through its website, launcher diagnostics, connection services, and contact channel. For privacy questions or requests, email [email protected].
This statement covers softlight.app and the Softlight Windows launcher. It covers our hosting, optional PostHog analytics and diagnostics, data kept on your device, and requests to independent services.
2. Website and hosting
MailoDataCenter operates the website's hosting and content delivery in the Netherlands. Delivering a page or download temporarily requires network information such as your IP address, requested URL, and request headers.
Our website hosting does not retain ordinary web-server access or error logs. Separately, enabled analytics retain usage and sanitized error records in PostHog as described below. We do not create advertising profiles or sell visitor data.
Softlight uses PostHog for usage analytics, sanitized error reports, error-triggered interface replay, operational logs, performance measurements, and optional rating surveys. PostHog hosts this project's collected data in the United States. Softlight has no advertising or cloud backups of game installations. The launcher does not automatically upload worlds, screenshots, saved skins, or game logs to MailoDataCenter.
Ordinary link-only server and world sharing do not create an account or require Microsoft sign-in. Friends-enabled rooms instead require verified Minecraft accounts. There is no separate password or email-verification step.
For ordinary link-only sharing, connect.softlight.app temporarily processes room membership, invitation secrets, connection candidates, optional server name/version hints, Minecraft display names, and abuse counters only in memory. Display names are shared with the other players in the room and are not verified by Softlight. No Minecraft UUID or account token is sent for this naming feature. The sharing protocol uses a temporary random connection identity without a sharing account token. When diagnostics are enabled, updated launchers can also send their separate random installation identifier and session context to owned Softlight services to link operational failures. Turning collection off stops this optional telemetry context. The STUN service helps peers discover network addresses. An OVH-hosted TURN service can forward end-to-end encrypted gameplay packets when a direct connection is unavailable. It temporarily processes peer IP addresses, connection timing, and packet sizes to carry traffic; it does not decrypt gameplay or host worlds. These services do not retain gameplay traffic or invitation secrets. Sanitized operational logs and aggregate service-health measurements are described below. Rooms and counters are temporary and are not stored in a database. Peers can learn each other's IP addresses. Account-free sharing does not hide your IP address or Minecraft display name.
Friends uses a verified Minecraft UUID and username. The launcher proves account ownership directly with Mojang; Microsoft and Minecraft tokens never go to Softlight Services. The dedicated Friends database stores profiles, friendships, requests, blocks, privacy preferences, and hashes of short-lived access and rotating refresh credentials. Access sessions last 15 minutes and refresh credentials have a 30-day absolute lifetime. Accepted friends can see online presence unless you appear offline. Friends invitations and shared-session listings are temporary.
Where chat is enabled, the new server history mode stores new message bodies in the dedicated Friends database for 30 days. These bodies are readable by the operator. HTTPS protects transport; this mode does not provide end-to-end encryption. The service also stores conversation metadata, membership, timestamps, read cursors, mute choices, and chat preferences. Message bodies are not written to service logs.
Each signed-in PC automatically downloads available server history and keeps encrypted local history with no automatic age expiry, subject to storage capacity. A new PC can recover only the available 30-day server history. Older messages remain only on PCs that downloaded them. Existing local history is not uploaded. Signing in does not require separate chat-device registration or manual key approval. Windows protects local keys, but an unlocked account or malware can still access local messages. Losing a PC and its protected key loses any history available only on that PC. Existing read-only conversations remain read-only.
During the transition, previously registered devices can collect encrypted deliveries for their original 72-hour lifetime. These older deliveries use keys trusted on first use, have no forward secrecy, and have not had an independent cryptographic review. New encrypted sends stop when server history mode activates; older launchers must update.
Blocking hides messages, previews, typing and receipts in both directions, including shared groups; group membership remains visible. Typing is temporary. Appear offline suppresses typing and read receipts, but does not prevent messages you choose to send. Chat settings control desktop alerts, preview text, typing and receipts. Windows can retain notification previews according to its settings. Drafts stay in memory; local history and failed send attempts are encrypted. Failed attempts expire within 72 hours and require explicit retry. Blocking hides messages in the official launcher but cannot erase screenshots or copies kept elsewhere.
4. Data on your computer
The Windows launcher saves installation manifests, installed-content records, library groups, local server manifests, server backups, settings, and saved skins on your computer. Each installation has its own game files, configuration, worlds, screenshots, and game logs. The default launcher data directory is %APPDATA%\Softlight.
Minecraft sign-in gives the launcher access to Microsoft authentication information and your Minecraft player name, UUID, ownership status, and profile. Saved Microsoft authentication credentials and personal CurseForge API keys are stored separately from installations using Windows-backed encryption. Minecraft credentials and provider keys are not uploaded to MailoDataCenter.
Sharing invitations and relay credentials are held in memory, not saved by the current launcher. Invite secrets stay in the fragment of HTTPS links, which browsers do not send in HTTP requests. The join page removes the fragment from browser history and uses no analytics or browser storage. Old encrypted sharing credentials are not read or automatically deleted.
Microsoft handles your password in the system browser; you do not enter it into Softlight. The launcher uses the resulting credentials with the relevant official services to authenticate and perform the actions you request.
Saving a skin locally does not change your Minecraft account. Applying a skin sends the selected texture and the necessary authentication information to Minecraft's service. Imported files and screenshots stay local unless you choose to share them or independent software sends them elsewhere.
5. Requests to other services
PostHog processes the analytics, diagnostics, recordings, and survey ratings described above on our behalf in its United States cloud region. Requests to PostHog require network connection information, including an IP address. Our project is configured to discard client IP addresses from stored events. See PostHog's Privacy Policy and data storage documentation for its processing and storage practices. Contact us about Softlight telemetry or requests to remove it.
The website's Discover content pages retrieve public project information, searches, and compatibility filters directly from Modrinth in your browser. Modrinth receives your IP address, browser request headers, search terms, project identifiers, and compatibility filters. These catalog requests omit cookies, authorization credentials, and the referring page URL. Softlight's server does not retrieve catalog data. Search and filter choices appear in the page URL and browser history. Catalog responses are cached briefly in browser memory, without adding cookies or persistent browser storage.
Hovering or focusing a public page link can preload that page's HTML and code. On Discover pages, hovering or focusing filters, sorting choices, pagination, or version controls can request the matching catalog information before you select it. These requests follow the same rules described above and use short-lived memory caches. Prefetching does not download installers or project files, execute analytics on unvisited pages, or run on private invitation pages. Data-saving connections skip this background work.
Project artwork and images in creator descriptions load directly from third-party HTTPS image hosts. File downloads go directly to the URLs supplied by Modrinth. Those hosts receive your IP address and request headers. Catalog images and download links omit the referring page URL. Opening creator links or the original Modrinth page uses the recipient's own website and privacy policy. Other Softlight pages do not request catalog data.
Functions such as sign-in, ownership checks, profile and skin changes, content browsing, and downloading game files require direct requests to third-party services. These can include Microsoft, Xbox, Minecraft, Modrinth, CurseForge, loader maintainers, and Java-runtime or file-distribution providers.
A recipient can receive your IP address, request headers, searches or project identifiers, game and loader filters, and any credentials required for its service. Credentials are used for their intended services, not sent to unrelated providers. Enabled launcher update checks and downloads also contact the configured Softlight release host.
Independent services may retain data or process it outside the Netherlands or the European Economic Area under their own policies. Their retention practices are separate from the collection described here. Minecraft, mods, and multiplayer servers can also make their own network requests.
- Microsoft Privacy Statement , including Minecraft and Xbox services.
- Modrinth Privacy Policy , covering catalog requests and requests made by the launcher.
- Overwolf Platform Privacy Policy for CurseForge, together with its Website Privacy Policy and notices shown by the relevant service.
6. Purposes and legal bases
We temporarily process website request information to deliver the website and requested downloads. We process contact inquiries to answer your questions and resolve requests. Our legitimate interests under GDPR Article 6(1)(f) are operating this free service and responding to people who contact us, while limiting the information used to what those tasks require.
Launcher processing necessary to provide functions you request, such as managing local installations or signing in, supports delivering the service under GDPR Article 6(1)(b). Independent providers are responsible for explaining the legal bases for their own processing.
Temporary signaling, room membership, and connection address exchange support the sharing service you request under GDPR Article 6(1)(b). Temporary throttling protects that service under our legitimate interest in preventing abuse.
Usage analytics help us understand which functions people use and where downloads, installation, or launches fail. Sanitized diagnostics and masked error replay help us investigate faults. Aggregate service measurements help us monitor availability and capacity. These uses are limited to operating and improving Softlight; the controls in Analytics, replay, and browser storage let you stop optional collection.
Where a legal obligation requires us to retain or disclose particular information, GDPR Article 6(1)(c) applies. We do not rely on accepting these terms as blanket consent to tracking or unrelated data use.
7. Retention and removal
Our website hosting does not retain ordinary web-server access or error logs. PostHog error recordings have a 30-day retention period. Usage events, error reports, survey ratings, and operational logs follow the retention periods for their products in our PostHog plan. Turning collection off does not erase previously uploaded records. Contact [email protected] for access or deletion requests and details of the applicable retention periods. Data that independent providers retain for their own services is governed by their policies.
Room data disappears when the host session ends; invitations expire and temporary abuse counters expire automatically. The ordinary link-only sharing does not save account records. Friends and chat use the separate retention rules below.
Server message bodies become unavailable after 30 days. Reads enforce this boundary; startup and hourly cleanup remove expired bodies. Downloaded local history has no automatic age expiry. Storage limits stop new downloads with an error instead of silently removing older messages. You can explicitly clear older local history in Chat settings. Previously queued encrypted deliveries expire within 72 hours. Deleting a message removes its local body and sends an erasure record to other devices. Deleting a group withdraws access. Delete friends profile removes authored messages, memberships, preferences, read state and devices. Other devices apply erasures when they reconnect; offline or modified clients cannot be forced to erase immediately. A surviving group transfers to its longest-standing remaining member. A minimal hashed UUID opt-out record prevents automatic re-enrollment. Minimal message authorship and durable deletion records contain no text and have no automatic age expiry, so deletions can reach PCs that have been offline for longer than 30 days. Encrypted database backups have a maximum retention of seven days; deleted data may remain in those backups until rotation. Backups can contain queued ciphertext and readable server messages, but not local histories or private device keys. Recovery must reconcile deletions, revoked devices and permissions, discard restored delivery queues, and expire old messages before reopening access.
If you created an account in an earlier sharing preview, removing that sign-in service does not itself erase its existing Microsoft identifier, profile information, or authentication state. These legacy records require separate deletion during retirement. For access or deletion requests, email [email protected]; no account login is needed. Remaining encrypted identity backups are subject to the existing maximum retention of seven days. Stopping the old backup service does not automatically erase them.
Local launcher settings, installations, saved skins, and downloaded files remain on your computer until you remove them. Signing out removes Softlight's saved Microsoft credentials. Removing a personal provider key in Settings deletes that locally saved credential. Microsoft or provider browser sessions can remain signed in separately.
You can delete saved skins and installations from the launcher. Deleting an installation also removes its local files, so back up worlds first. Uninstalling Softlight preserves player data. To remove remaining launcher data, close Softlight and remove its data directory after backing up anything you want to keep.
If you email us, we use your email address and the information you send to handle the inquiry. We delete correspondence after the inquiry is resolved unless a legal obligation requires retention. Do not send passwords, authentication tokens, or API keys. Share logs only when needed and check them for personal information first.
8. Your privacy rights
Where applicable under the GDPR, you can request access, correction, erasure, restriction of processing, or portability of your personal data, and object to processing based on legitimate interests. Contact [email protected] to make a request. We will respond within the period required by law and may need proportionate information to verify your identity.
Telemetry uses random browser and installation identifiers rather than account names. To locate telemetry for an access or deletion request, we may need the identifier stored on the relevant device. Contact us for help locating it; do not send passwords, account tokens, or private game files. You can disable future collection without making a request or signing in.
We cannot retrieve launcher files that are only on your computer or erase records controlled by independent providers. You can manage local files yourself and contact the relevant provider about its records.
You can raise a concern with us or complain to the Autoriteit Persoonsgegevens , the Dutch data protection authority, or another competent supervisory authority. You do not need to waive your rights to use Softlight.
9. Changes and contact
We will update this statement when Softlight's data practices change and show the revised date here. Material changes will be identified on the website or in release notes, with any notice required by law. We will not introduce a new consent-based use without obtaining the consent it requires.
Questions about this statement can be sent to [email protected]. The Terms of Service explain use of the website and launcher.