Privacy
Policy

What data LS:MP collects, why, how long we keep it, who else sees it and the rights you have over it, plus every cookie and browser key the site uses.

Version 1.0 Effective 3 November 2026 Last updated 17 November 2026

The short version

  • No analytics. No advertising. No tracking of any kind. There is not one measurement script anywhere on this website, and on the website there is nothing to opt out of.
  • Our web pages load nothing from third parties: not the fonts, not the icons, not the anti-robot check. Your browser talks to us and to nobody else.
  • We use seven cookies for sign-in, security and the language you choose in the game interface.
  • We collect what an account needs: your email, your username, a hash of your password, and the technical records that make sign-in safe, including your IP address and a fingerprint of your machine.
  • If the LS:MP client crashes, it sends us a crash report. Both settings behind this are on by default in the installer: a small text report of the failure, and, only when our servers ask for one, a memory dump of the game. You can switch either off in the installer, or at any time under Settings › Privacy in the client (details).
  • You can delete your account yourself, from your settings, at any time.

The full text below is the one that counts, and it is specific: every cookie, every stored key, every recipient.

Who is responsible

This policy covers the personal data processed by the Los Santos Modding Platform (“LS:MP”, “we”): the website at lsmp.gg and its subdomains, the LS:MP client and its updater, the forum, the server list, the documentation, the in-game interface, and our OAuth 2.0 provider.

It does not cover the gameservers you join. Those belong to other people, who answer for their own data handling. See what a gameserver learns.

LS:MP is operated as an independent project. The controller can be reached at support@lsmp.gg, and will supply full identifying and contact details on request. We have not appointed a data protection officer; that address reaches the person who makes these decisions.

How we approach this

Three choices shape everything below, and they were made in the code before they were written down here.

  • Nothing that isn't needed. We ask for an email, a username and a password. We do not ask for your real name, your date of birth, your address, your phone number or your country.
  • Nothing from third parties on our pages. The typeface, the icons, the anti-robot check and every script are served from our own domain. Loading them from someone else's CDN would hand that company the IP address of every visitor, for nothing. What a forum member chooses to post is the one exception, and it is kept on a short leash.
  • Nothing that measures you. No analytics, no fingerprinting for statistics, no A/B testing, no advertising network, no “essential partners”. We know how many accounts and servers exist because we count rows; we do not know how you moved around this page, and we have no way of finding out.

What we collect, and why

“Legal basis” below refers to Article 6 of the GDPR, which applies to everyone using the platform whether or not you live in the European Union: we do not run two standards.

Your account

DataWhyLegal basis
Email addressIdentifies the account, confirms it at sign-up, resets a lost password, and warns you about changes to its security.Performance of our contract with you
UsernameYour public name on the platform: forum, profile, in game.Contract
PasswordNever stored. We keep an Argon2id hash, from which the password cannot be recovered.Contract
Account dates and flagsWhen it was created, when the email was verified, supporter tier, whether a deletion is pending.Contract
AvatarShown on your profile, on the forum and in game. A default one is generated for you; you may replace it.Contract
Two-factor secret and recovery codesOnly if you turn two-factor authentication on.Contract

Signing in, and keeping the platform safe

Some of this is unavoidable: an online service that cannot tell a returning player from an attacker cannot protect either of them.

DataWhyLegal basis
Session recordsOne per device you are signed in on: your user ID, email, username, the IP address it was opened from, a short description of the browser or client, and, for game sessions, the machine fingerprint. Listed in your settings so you can end any of them.Contract; legitimate interest in account security
IP addressRecorded against your account when you sign in, so an unfamiliar address can be flagged. Also used, without being stored against you, to rate-limit sign-in, registration and password-reset attempts.Legitimate interest in preventing abuse and account takeover
Machine fingerprint (“HWID”)One-way digests of hardware identifiers read by the game client: the identifier and serial numbers of your computer's firmware, the serial number of the disk Windows runs from, and the factory addresses of its built-in network cards, plus a random value the client stores for itself when installed. The identifiers themselves never leave your computer, only digests from which they cannot be recovered. It is what makes a ban cost more than the price of a new email address. It is not derived from your files and does not identify you outside LS:MP.Legitimate interest in enforcing bans and preventing cheating
Sign-up address in your activation emailThe activation email tells you which IP address created the account, so you can see immediately if it wasn't you.Legitimate interest in account security
Moderation recordsBans against an account, an address or a machine, with the reason and the expiry; reports you send; actions our staff take.Legitimate interest in protecting the platform and its users
The anti-robot check collects nothing

Sign-up and password reset are protected by a proof-of-work puzzle your own browser solves. There is no third-party captcha, no cookie, no image grid, and nothing about you is sent anywhere: your computer simply does a little arithmetic before the form is accepted.

What you publish

Forum topics, replies and attachments; likes, subscriptions and read markers; your public profile; the servers you list, with their name, description, icon, banner and network address; the boosts you place on servers. This is processed to run the service you asked for, and some of it is public by design: your username, public ID, avatar and posts can be read by anyone, signed in or not.

Topic views and file downloads are counted in aggregate only: a number per day, with no row tying it to you.

Crash reports

If the LS:MP client crashes, it can send us a report so the fault can be found. Two settings decide what leaves your computer. The installer shows both, and both are on unless you untick them; you can change either at any time in the client, under Settings › Privacy. A memory dump is only ever sent in answer to a crash report, so the two are linked: crash dumps can only be turned on while crash reports are on, and turning off crash reports also turns off crash dumps. If, under the previous version of these settings, you had kept the diagnostic summary on and the full report off, crash reports are now off until you turn them on yourself: that setting sends more than the summary did.

SettingWhat is sent
Send crash reportsA crash report: a small archive of text files, sent every time the client crashes. It holds a summary of the failure: the error, its code and the memory address it involved; the call stack; the list of modules that were loaded; the crash signature; the LS:MP version, your operating system, CPU, graphics card, memory size and how much of it was in use; the time of the crash; an identifier generated anew each time the client is launched; and the address of the LS:MP server you were connected to, if any. It also holds the complete text report that summary is taken from, which adds the IDs of the program's threads, the processor register values, and a few hundred bytes read from the program's memory around the failing instruction and at the top of its stack; and the last part of the client's log file, which can mention names and server addresses. In both, your Windows user folder, and so your Windows user name, is replaced by a placeholder. It contains no memory dump.
Send crash dumpsA memory dump of the LS:MP process at the moment it crashed, and nothing else. It is not sent every time: after receiving the crash report, our server says whether it wants the dump, and it asks only until it holds two for that kind of crash. A memory dump is a snapshot of what the program held in memory, so it may contain any data that was in the game's memory at that moment: text you had typed, names shown on screen, messages you were reading. We use it only to find the fault. This setting has no effect while crash reports are off.

So that a recurring crash can be matched to the person it keeps happening to, whatever is sent also carries your account's public ID if you were signed in, a 64-bit digest of your machine fingerprint (from which the fingerprint cannot be recovered), and the IP address our server sees the report coming from. With crash reports off, nothing is sent: the report stays on your computer, where the client only ever keeps the most recent one. Whenever something was not sent automatically, the crash window offers a button to send it for that one crash, only if you click it. Crash summaries are deleted automatically after 365 days, and the report archives and memory dumps after 90 days at most (see how long we keep data). Legal basis: legitimate interest in diagnosing and fixing defects; the two settings are how you object to it, at any time.

Email we send you

Account email is transactional: activation, welcome, password reset, password changed, security alerts, sign-in codes. You cannot opt out of these without closing the account, because they are the account.

We may occasionally send registered users an announcement about the platform itself. Every one carries a one-click unsubscribe, and unsubscribing takes effect immediately and permanently.

Purchases and supporter status

When you buy a mod or become a supporter, the money moves at the payment provider: we never see or store card details. What we keep is the entitlement: which licences your account holds, when they expire, and which supporter tier is active. Where the provider is Patreon, and only if you connect that account yourself, we also hold your Patreon user ID, the email on that account (for support, never for decisions) and your membership status.

Cookies and browser storage

Here is every cookie we set. The sign-in and security cookies support account access and protect account connections. The language cookie stores your choice from the in-game settings.

CookieWhat it doesLifetime
lsmp_sessionKeeps you signed in. An opaque identifier: it contains nothing about you, and is only a key to a record on our side. HttpOnly, Secure, SameSite=Lax.31 days
lsmp_sdA technical marker holding the single character 1, so that we do not re-send the session cookie on every response. No identifier, no secret.31 days
lsmp_oauth_stateProtects the Google sign-in round trip against cross-site request forgery.10 minutes
lsmp_patreon_stateThe same protection, for connecting a Patreon account.10 minutes
lsmp_link_discord_stateThe same protection, for connecting a Discord account.10 minutes
lsmp_link_steam_stateThe same protection, for connecting a Steam account.10 minutes
lsmp_langRemembers the interface language you select in the in-game settings. It stores only the language code.365 days

Local storage

Cookies are not the only thing a site can leave on your device, and a policy that listed only cookies would be hiding half the answer. These values live in your browser's local storage (the last two in session storage, which is emptied when you close the tab). They stay on your machine; none of them is sent to us as a tracking identifier, and none is readable by anyone else.

KeyWhat it holds
token, guestTokenYour session, mirrored where a cookie cannot follow: the in-game interface runs from a local address, so the cookie is never sent to it.
lsmp_theme, lsmp_lang, lsmp_reduce_motionChoices you made: light or dark, interface language, and whether to cut down on animation.
lsmp_history, lsmp_favoritesServers you visited recently, and servers you starred, in the server browser.
lsmp_cartWhat is in your basket in the in-game mod store.
fx-draft-new, fx-draft-t…A forum post you were writing and have not sent, so a closed tab does not cost you the text.
lsmp-sdk-theme, lsmp-sdk-langOn the documentation: your theme, and whether you want code samples in JavaScript or Lua.
lsmp.signinCodeA sign-in code you asked for and have not typed yet, so that coming back from your mail app does not lose the request. Useless without the code itself.
lsmp_try_openedWhen an in-game mod trial started, so the trial page can still show the time spent after a reload.

You can clear all of it at any time from your browser's site-data settings. Clearing it signs you out and forgets your preferences; nothing else is lost.

What our pages load from elsewhere

Nothing, of our own doing. Every font, icon, image, stylesheet and script that makes up our web pages is served from our own domain. There is no CDN-hosted library, no web font service, no social widget and no third-party captcha, so no other company is told that you visited us.

The forum is the one place where a page can show something hosted elsewhere, because a member chose to post it:

  • Pictures from a short list of image hosts: Imgur, Tenor, Giphy and GitHub. Your browser fetches them directly, so that host sees your IP address, but it is not told which page you were reading. We only accept hosts that serve a picture without setting a cookie; a picture from anywhere else is shown as a plain link.
  • Videos from YouTube, Vimeo or Streamable. Nothing is loaded until you click the player, which says beforehand who it plays from. Once it plays, it is that company's player under its own privacy policy, and it may store data on your device. YouTube videos play from its privacy-enhanced domain, and Vimeo videos with its do-not-track setting.

Two more, both outside the web pages themselves. Our origin sits behind a reverse proxy, which necessarily sees the traffic that reaches us; see who else sees your data. And inside the in-game mod store, artwork for a mod is loaded from the storefront that publishes it, which means that storefront sees your IP address when the store is open.

That proxy may set a short-lived security cookie of its own (__cf_bm or cf_clearance) on the rare occasions it has to check that traffic is not an automated attack. It identifies no one, serves no other purpose, and is strictly necessary in the same sense as ours. The traffic statistics it keeps are counted on its side from the requests it carries: no script runs in your browser for them.

If that ever changes (if we ever add anything that measures or follows you), we will ask for your consent before it loads, and this page will say so first.

What we never do

  • We do not sell, rent or trade your personal data. Not to anyone, not ever.
  • We do not profile you, score you, or make automated decisions with a legal or similarly significant effect on you.
  • We do not run advertising, and we host no advertising technology.
  • We do not use analytics: no page-view tracking, no session recording, no heatmaps, no funnels.
  • We do not ask for, and have no use for, your real name, date of birth, address or telephone number.
  • We do not store payment card details, because payments never happen here.
  • We do not read the content of your private messages for any purpose other than acting on a report about them.

Accounts you link to ours

Linking is always your choice, always reversible from your account settings, and deliberately narrow: we ask each provider for the least they will give us.

ServiceWhat we receive and keep
GoogleYour verified email address and a stable account identifier, used so you can sign in without a password. Nothing else.
DiscordYour Discord ID, and only that. We request the minimum scope, which means we are not even shown your email address or your servers, and we keep no Discord access token: we ask Discord to discard it as soon as the link is made.
SteamYour SteamID64, and only that. Steam's sign-in requires no secret and grants us no access to your library, your friends or your profile beyond that number.
PatreonYour Patreon user ID, the email address on that account (kept for support, and no decision depends on it), and your membership status and tier, which is what your supporter benefits are granted from.

Unlinking removes the connection on our side. What the provider keeps is governed by the provider's own policy, not by this one.

What a gameserver learns

Gameservers are other people's computers

When you join a server, you connect to a machine we do not own or control. Its operator decides independently what to record about your play, and is legally responsible for that, as a controller in their own right. This policy cannot and does not cover it.

As with any online game, a server you connect to necessarily sees your network address. It is also told your public identity: your public ID, your username, the address of your avatar, and whether you are a registered account or a guest. Before you are admitted, we confirm to the server that the identity your client presents is really yours: that check is what stops someone playing under your name.

So that it can enforce its own bans, a server is also given a machine identifier of its own: derived from your machine fingerprint, it is different on every server, and it can be neither traced back to the fingerprint nor matched with what another server receives.

Scripts running on a server can record what you do there, keep statistics against your account, and refuse you entry. If you want to know what a particular server keeps, ask its operator.

Who else sees your data

A very short list, and nobody on it receives anything for their own purposes.

RecipientWhat for
Our hosting providerRuns the machines the service and its databases live on, including the one where crash reports and memory dumps are stored.
Our network and storage providerSits in front of the site as a reverse proxy, filtering attacks and carrying traffic, which means it processes the IP address of every request, and crash reports pass through it on their way to us. The same provider stores published mod packages and serves them for download; it does not store crash reports.
Our email deliverySends the transactional messages described above.
Google, Discord, Steam, PatreonOnly if you choose to link that account, and only what that section describes.
Mod storefrontsWhere a mod is sold through a storefront, we exchange with it the identifiers needed to grant your account what you bought.
Gameserver operatorsAs described above. They are independent controllers, not our processors.

We may also disclose data where the law requires it, or where it is necessary to establish, exercise or defend a legal claim. If we are ever compelled to hand over data about you, we will tell you unless we are forbidden to.

Where your data goes

Our servers are in Europe. Some of the providers above are established outside the European Economic Area, or operate networks that route traffic through it. Where personal data is transferred outside the EEA or the United Kingdom, that transfer relies on an adequacy decision of the European Commission where one exists, and otherwise on the European Commission's Standard Contractual Clauses.

You can ask us at any time which providers are involved and on what basis.

How long we keep it

DataKept
Your account and its contentFor as long as the account exists.
Sessions31 days, or until you sign out or end the session yourself.
Rate-limit countersMinutes to hours. Never tied to your account.
Guest identities15 days after they were last used.
Inactive accountsDeleted after 22 months without any activity, following a reminder by email after 21 months and at least 30 days' notice. Details below.
Sign-in address historyDeleted when the account is deleted.
Supporter transition log180 days.
Crash reportsCrash summaries, with the account ID, machine fingerprint and IP address they carry: 365 days, then deleted automatically. Report archives (complete text report and log excerpt) and memory dumps: 90 days at most, then deleted automatically. What remains afterwards describes only the defect (its signature, the module it occurred in, and how many times it happened to how many accounts) and identifies no one.
Anticheat eventsAnticheat events recorded against an account are kept for 365 days, then deleted automatically.
BackupsRotated on a short cycle; deleted data disappears from them as they age out.

Deleting your account

You can start deletion yourself from your account settings. It completes after a 15-day grace period (signing in during that window cancels it) and then removes your account row, your sessions, your avatar, your servers and their artwork, your boosts, your two-factor secret, your forum data, your OAuth grants, your linked accounts and your address history. The crash summaries your client sent are kept for the defect they describe, but detached from you: your account ID, IP address and machine identifiers are erased from them. The report archives your client sent are deleted with your account, or within 90 days at the latest. Memory dumps carry no account identifier; the IP address and machine identifier stored alongside them are erased, and the dumps themselves are deleted within 90 days in any case.

Inactive accounts

We do not keep accounts nobody uses. After 21 months without any activity we email the address on the account, with the date from which it will be deleted. After 22 months without activity, and never less than 30 days after that reminder, the account is deleted, with the same scope as when you delete it yourself, minus the 15-day grace period, which the reminder already was.

Activity means signing in: on the website, from the game, with a sign-in code or Google, or through an application you authorised with your LS:MP account. Signing in at any time before the deletion cancels it and restarts the count; nothing else is needed.

Some accounts are not deleted for inactivity, for as long as the reason lasts: accounts holding a licence that has not expired (perpetual ones included) or an active supporter tier (a purchase or a membership is still running), accounts under an active ban, which would otherwise be a way to undo it, and our own staff accounts. When the reason ends, the account falls under the rule like any other. If the reminder cannot be delivered because the address is no longer valid, the deletion still happens: the reminder was sent to the address you gave us, and we do not keep accounts we cannot reach forever. An address that was never confirmed gets no reminder at all (it may not be yours), and its account follows the same dates.

What deliberately survives, and why

Being straight about this matters more than the paragraph looks.

  • Machine bans. A ban imposed on a computer stays on that computer. If deleting an account lifted it, deleting an account would be the way to undo one.
  • The administrative log. A record of what our staff did, and when. A log that could be erased by the person it concerns would not be a log.
  • Your supporter membership record. It describes a membership held at Patreon rather than with us, and keeping it is what lets a returning supporter recover their tier instead of paying twice.
  • Anonymous and aggregate figures. Daily counters that never identified anyone are not affected by deletion.

If you object to one of these, write to us and say so. We will weigh it case by case, as Article 21 of the GDPR requires.

Your rights

Wherever you live, we will honour the following. If you are in the European Union, the United Kingdom or another place with comparable law, these are rights you hold; elsewhere, treat them as a promise.

  • Access: a copy of the personal data we hold about you, and an explanation of what we do with it.
  • Rectification: correction of anything inaccurate. Your username, email and avatar you can change yourself.
  • Erasure: deletion of your data, subject to what deliberately survives.
  • Restriction: a pause on processing while a dispute about accuracy or legitimate interest is resolved.
  • Objection: to any processing we base on a legitimate interest, on grounds relating to your situation. Tell us the grounds and we will weigh them.
  • Portability: the data you gave us, in a structured, machine-readable format.
  • Withdrawal of consent: where we relied on consent, you may withdraw it at any time, without affecting what was lawful before.
  • Complaint: to your national data protection authority, whatever we say or do.

To exercise any of them, write to support@lsmp.gg from the address on your account, or from another address if you can show the account is yours. We answer within one month, and tell you if a complex request needs longer. There is no charge, unless a request is manifestly unfounded or excessive.

Access and portability are handled by hand today. We may ask you to confirm your identity first, not to obstruct you, but because handing an account's data to the wrong person is the worst outcome available.

How we protect it

  • Passwords are hashed with Argon2id, at parameters that follow the OWASP recommendation. We cannot read your password, and neither can anyone who steals the database.
  • Two-factor authentication is available on every account, with recovery codes. Turn it on.
  • Everything travels over HTTPS, and session cookies are marked Secure and HttpOnly, which puts them out of reach of page scripts.
  • Sessions are capped and listed. A limited number per account, each shown in your settings with the address and device it was opened from, each revocable on its own.
  • Sign-in, registration and password reset are rate-limited per address and per account, and protected by the proof-of-work check described above.
  • The game client's identity is sealed before it reaches a server, so nobody can play as you by claiming to.

No system is perfect. If a breach affecting your personal data occurs, we will notify the competent supervisory authority within 72 hours where the law requires it, and tell you directly when the risk to you is high.

Children

LS:MP is not intended for children. You must be at least 13 to hold an account, and older where your local law requires it; the detail is in the Terms of Service. We do not knowingly collect data from anyone below that age; if we learn that we have, we delete the account and its data.

If you are a parent or guardian and believe your child has created an account, write to support@lsmp.gg and we will act on it.

Changes to this policy

We update this page when what we do changes. The version and dates at the top always reflect the current text.

If a change materially affects how we handle your data, we will tell you before it takes effect, by email or by a notice on the site, and say what changed. Where a change requires your consent, we will ask for it rather than assume it.

Contact

Anything at all about your data, including the requests described in your rights: support@lsmp.gg.

You also have the right to lodge a complaint with your national data protection authority. We would rather you gave us the chance to fix it first, but that right is yours regardless.

Privacy Policy, version 1.0, effective 3 November 2026. See also the Terms of Service.