PRIVACY POLICY

BF6 Loadouts is run by Basile Vernouillet, an independent developer based in France. This page describes what the site actually does with data — not a template. If something here is unclear or looks wrong, write to contact@bf6loadouts.com.

Browsing without an account

You can read every build, weapon page and tier list without signing in, and I do not ask you for anything to do it. Two things still happen in the background:

• The site is served through Cloudflare, which handles DNS and caching. Like any web server, it processes your IP address, browser user agent and the URL you requested in order to deliver the page and to block attacks.
• Page views are counted per build, loadout and tier list. That is a single counter on the item — no visitor identifier is attached to it.

The site also loads a lightweight page-analytics script from onedollarstats.com, which reports aggregate traffic (page views, referrers, which links are clicked). I use it to see which pages are worth improving. It is not used to build a profile of you.

Voting without an account

Votes are open to visitors who are not signed in. To stop the same person voting on a build repeatedly, a random token is stored in a cookie named bf6_anonymous_vote_token on your device for up to a year, and the vote is saved against that token. The token is a random string: it holds no name, no email and no IP address, and it is not used for advertising or analytics. Clearing your cookies deletes it, and you will be able to vote again.

If you create an account

Accounts are handled by Clerk, an authentication provider. Clerk stores your login credentials, sessions and any social login you choose to use; I never see your password. What is copied into this site's own database is:

• your email address;
• your username, first and last name and profile picture URL, as provided to Clerk;
• your Clerk user ID and the time you last signed in;
• optionally, the creator links you add yourself: Twitch, YouTube and X/Twitter handles.

Everything you then create is stored under that account: builds, loadouts, tier lists, votes, ratings, comments and forum posts.

What is public

This is a public database, so assume anything you publish is visible to everyone, including search engines and AI crawlers. That covers your builds, loadouts, tier lists, comments and forum posts, along with your username and profile picture next to them, and the creator links you added. Votes are public in aggregate: the totals appear on each build, but who voted is not shown.

Your email address is never displayed on the site.

Comment moderation

Comments are checked automatically before they appear. The text of the comment is sent to a language model through OpenRouter, which returns a judgement on toxicity and spam. Only the comment text goes out — not your email or your account details — and the result (approved, flagged, rejected, plus a score) is stored with the comment so I can review moderation decisions.

Advertising

The site is paid for by ads served through Google AdSense. Google sets its own cookies and similar identifiers in your browser to serve and measure ads, and depending on your settings and region those ads may be personalised using data Google holds about you. That data goes to Google, not to me; I only see aggregate earnings and impression counts in my AdSense dashboard.

To be straightforward about it: this site does not currently show a cookie consent banner, so advertising cookies may be set before you have been asked. I consider that a gap and intend to fix it. In the meantime you can control personalised advertising directly at Google My Ad Center, block third-party cookies in your browser, or use an ad blocker — the site works fine with one.

Who else touches the data, and where

• Clerk — accounts, sign-in and sessions.
• Convex — the database and file storage holding everything described above, including images you upload with a build.
• Cloudflare — DNS, caching and protection in front of the site.
• Google AdSense — ads.
• OpenRouter — automated comment moderation.
• One Dollar Stats — aggregate page analytics.

These are US-based providers, so data reaches servers outside the EU. I do not sell data, and I do not share your account details with anyone beyond the providers needed to run the site.

Weapon stats on the site come from datamined game files, not from users — see about.

How long things are kept

Account data and published content stay until you ask for them to be removed or delete them yourself. The anonymous vote cookie expires a year after it is set. Ask me to delete your account and I will remove it along with your comments; for builds and loadouts, tell me whether you want them deleted too or kept and detached from your name — a build other people have voted on can be either, your call.

Your rights

I operate from France, so the GDPR applies to this site, and I apply the same rights to everyone regardless of where they live. You can ask for a copy of your data, ask for a correction, ask for deletion, ask me to restrict or stop processing, or object to it. Legally, the basis is: your consent when you create an account and publish, my legitimate interest in keeping the site running and moderated, and — for advertising cookies — consent, which is the gap described above.

Email contact@bf6loadouts.com and I will handle it. One person reads that inbox, so expect days rather than minutes, and within a month at the outside. If you are in the EU and think I have handled your data badly, you can complain to your national data protection authority; in France that is the CNIL.

Children

The site is not aimed at children, and accounts are not intended for anyone under 16. If you believe a child has created an account here, write to me and I will delete it.

Changes

When this policy changes, the date at the top changes with it. There is no mailing list, so significant changes will be visible on this page rather than pushed to you.