LLucky Loadout

Lucky Loadout / Privacy

Privacy policy

Short version: no accounts, no ads, and only analytics cookies. Here is everything the site stores and counts.

Updated 2026-10-19

What stays on your device

A few settings are saved in your browser so the machines remember them. The site does not upload them, and you can clear them any time by clearing this site's data in your browser settings. One usage event, described below, does say whether you turned sound on or off, which is the same choice the sound setting remembers.

KeyWhereWhat it's forHow long
ll-hd2-own-v1Local storageWhich Helldivers 2 equipment you marked as available, so rolls use your selected unlocks.Until you clear it
ll-dbd-own-v1Local storageWhich Dead by Daylight characters and perks you marked as owned, so rolls only use what you have.Until you clear it
ll-val-filter-v1Local storageWhich Valorant roles and agents you chose to roll from.Until you clear it
ll-mutedLocal storageWhether you turned the sound off.Until you clear it
ll-spunSession storageWhether the opening tease spin already played in this tab, so it only plays once.Until you close the tab

Share links

A shared build is written after the # in its link. Browsers don't send that part to web servers. Our analytics script does read the full page address, so the site's analytics is set up to remove the part after the # and any query string before a page view or a usage event is sent. That way a shared build code is not part of what is counted: the page address that the analytics script reports has the part after the # and any query string removed. A build code is a short list of ids for what was rolled (characters, perks, or a realm and map); it holds nothing about you.

Helldivers 2 roll links and share codes work the same way: the build code after the # is a short list of ids for what was rolled (weapons, a throwable, an armor passive, a booster and stratagems); it holds nothing about you.

Opening a page is still a request to Vercel's servers, like any request to a website, and what Vercel collects for that is covered under Hosting below. A query string added to a link is part of that request. The analytics request is a request like any other, so it also tells Vercel which page it came from, and a query string in a link can still reach Vercel that way. The part after the # never does.

What we count

The site uses Vercel Web Analytics to count page views, so we know which machines people use. Vercel's documentation says each page view may store the time, the page address, the page that linked you here, your approximate location (country, and possibly state and city), your operating system and browser with their versions, and your device type.

Vercel Web Analytics sets no cookies. Vercel says it tells visitors apart with a hash created from the request, and that the visitor session is discarded after 24 hours. It also says this data is recorded anonymously, not tied to an individual or to an IP address.

Usage events

Besides page views, the site sends a few usage events to Vercel Web Analytics while you use a tool. An event is a name plus at most two short labels. The labels never hold what you rolled, a character or perk name, or anything about you. Vercel may store the same details with an event as with a page view, including the page address the analytics script reports, without any # part or query string (see Share links above), and describes this data as recorded anonymously. Here is every event:

  • A roll: which side it was (killer, survivor or map) and how many rolls it was since the page loaded (1, 2 to 3, or 4 or more). That count starts again each time a page loads and is not saved on your device.
  • A slam, which is stopping the reels early: no labels.
  • Printing the ticket: no labels.
  • Copying a share link: whether your browser copied it or the link was shown for you to copy by hand.
  • Opening a guide’s suggested build in a randomizer: the guide identifier and game, without the shared build code.
  • Opening a share link: whether the code worked, did not match this machine, or used something that has left the game.
  • Changing which characters or perks you own: which of the two lists changed, and only when it really changed.
  • Turning sound on or off: whether sound is now on.
  • A data error: what failed, either the game data would not load or the machine could not start.

Holding a reel is not counted. Switching sides is not counted as its own event, but the roll it starts is counted like any other roll.

Google Analytics

On luckyloadout.com the site also uses Google Analytics 4 to count page views. It sets Google's first-party analytics cookies (named _ga and _ga_ followed by an id), which tell repeat visits apart and last up to two years. It runs with advertising storage, ad user data and ad personalization denied, and with Google signals and ad personalization off; the site shows no ads. As with Vercel, the page address it reports has the part after the # and any query string removed, so a shared build code is not sent. It sends no usage events, only page views.

Google's own collection is covered by how Google uses information from sites that use its services. You can block it with a content blocker or the Google Analytics opt-out add-on.

Hosting

Vercel hosts the site. Vercel's privacy policy says it collects IP addresses, a location derived from them, and system configuration information for traffic to the sites it hosts.

Ads

There are no ads today. If ads are ever added, this page will be updated to describe them.

Other sites

The link to The Finals Loadout (opens in a new tab) goes to a different site, which this page does not cover.

Kids

The site isn't aimed at children under 13.

Changes

If this page changes, the date at the top changes with it.

Contact

Privacy questions: info@thefinalsloadout.com.