Privacy

You can use Gear Lab without an account, and most people do. Nothing you configure is sent to us: your class, affixes and builds are worked out in your own browser. Traffic is measured with a self-hosted, cookie-free analytics service that records page views and a few anonymous interactions — never an identifier that could single you out.

Who is responsible

Gear Lab is operated by VUH Labs LLC, which is the data controller for the personal data described on this page. For anything about your data — a question, a copy, a correction, a deletion, or a complaint — write to [email protected]. We answer from the same address.

Signing in with Discord

Signing in is optional. If you do, we ask Discord only for its identify scope and store three things: your Discord user ID, your display name, and your avatar image address. We do not ask for, receive, or store your email address, your password, your servers, or your messages.

Your display name and avatar are refreshed each time you sign in, so they follow whatever you have set on Discord. What Discord itself does with your data is covered by Discord's privacy policy.

While you are signed in we set one cookie holding a signed session token. It is strictly necessary — it is what keeps you signed in — it expires after 30 days, and it is never used for tracking or advertising. Signing out deletes it.

Why we are allowed to hold it

  • Your account and saved builds — because you asked for them. Signing in and saving are both deliberate acts, and holding the data is what performing that request means.
  • Analytics — our legitimate interest in knowing which pages and campaigns actually help people build something. It sets no cookies, records no identifier, and cannot be traced to a person, which is what keeps that interest from overriding your privacy.
  • Personalised advertising — your consent, asked for by Google's consent message where the law requires it, and withdrawable from the same prompt.
  • Keeping the site up — our legitimate interest in serving and protecting it, which is what the hosting provider's technical logs are for.

How long we keep it

Your account and saved builds stay until you delete them — there is no expiry and no archive. Deleting a build removes it; deleting your account removes the account and every build with it, immediately and permanently. Our analytics holds no personal data to retain, and the hosting provider's technical logs age out on its own schedule.

Your rights, and how to use them

If you are in the UK, the EU, Brazil or another place with similar law, you have the right to a copy of your data, to correct it, to delete it, to object to or restrict what we do with it, and to take it elsewhere. Two of those are buttons rather than requests:

  • Download my data, on your account page, gives you everything we hold under your account as a JSON file — machine-readable, so you can take it with you.
  • Delete account, on the same page, removes it all. It cannot be undone, and it does not ask Discord to delete anything — Discord is a separate service with its own account.

Your display name and avatar are refreshed from Discord at each sign-in, so correcting them there corrects them here. For anything else, write to [email protected]. If you think we have got it wrong, you can complain to your local data protection authority.

Who else touches it

We use a small number of providers and share nothing beyond what each needs to do its job: Cloudflare hosts the site and the database, Discord is the sign-in provider, and Google serves the advertising. We do not sell your data, and we do not give it to data brokers or ad networks — no Discord ID, display name or avatar is ever passed to an advertising or analytics service.

VUH Labs LLC is based in the United States and the database is hosted there, so if you are in the UK, EU or Brazil your data is transferred outside your region. That transfer runs on the standard contractual clauses in our providers' data processing agreements.

Embedded videos

A shared build can include a video its author chose, shown as an embedded frame. The preview image is fetched from YouTube's image servers when the page renders it; the player itself — the part that can set cookies — loads from YouTube's cookie-less domain only when you press play, at which point YouTube's own terms apply.

Advertising

Advertising is what pays for hosting and keeps the calculator free. Gear Lab uses Google AdSense, and Google's advertising tag loads on every page. Google may set cookies or use similar device identifiers to serve and measure ads, under its own policies.

Where consent is required by law — the EEA, the UK and Switzerland — Google's consent message asks for your choice before personalised advertising is used, and you can change that choice later from the same prompt.

  • Without an account, everything you configure (class, affixes, builds) lives only in your browser, saved in its local storage. Share links encode the build in the URL itself, so sharing one sends nothing to us.
  • If you are signed in, comments and votes you post on shared builds are stored under your account and shown publicly with your display name, and reports you file about content are stored privately so we can act on them. You can delete any comment; deleting your account removes all of it.
  • If you are signed in and choose to save a build, that build is stored on our server under your account — its name, the encoded build itself, and when you saved it. Saving is always something you do deliberately; nothing is uploaded in the background. Saved builds are private unless you mark one public, you can delete any of them at any time, and deleting your account deletes all of them with it.
  • The site is served by our hosting provider, which may keep standard technical request logs (such as IP addresses) and set strictly necessary cookies to operate and protect the service.
  • Apart from the session cookie described above, which exists only while you are signed in, Gear Lab sets no cookies of its own — and never sells or shares anything about you.

Changes to this policy

If what we collect changes, this page changes with it and the date below moves. Since we hold no email address for you, notice of anything material appears on the site rather than in your inbox.

Questions? Get in touch.

Last updated: 13 August 2026.

← Volver al planificador