llamaperf

Privacy

Last updated 22 November 2026

This page says what llamaperf collects, why, who else handles it, and how long it is kept. We would rather list something plainly than leave it out.

When you browse

Every request to llamaperf passes through Cloudflare, which protects and speeds up the site and sees your address as part of doing so. Our own server then logs each request: your address, the page, your browser's name, the page you came from and your country. These logs are kept for 14 days and are used to keep the site running and to spot abusive traffic.

We use two analytics tools to understand how the site is used. Google Analytics sets cookies and is run by Google. StepMetrics is our own analytics service; it sets one cookie on llamaperf.com, stepmetrics_id, kept for 400 days, to recognise a returning browser, and otherwise tells visits apart using your address and browser.

You can save your GPU or Mac as your rig, so pages answer for your hardware first. It is kept in your browser's own storage on that device and is never attached to an account. To suggest a card, the page reads the name of the graphics chip your browser reports and matches it against our list inside your browser. That name is not sent to us for this. When you save or clear a rig, StepMetrics records which card it was, the same way it records other things you press on the site.

Ads

The ads on llamaperf are served by llamaperf itself, with no third-party ad scripts. So that we only count real readers, we record every ad view and every click on an ad, whether or not it is counted: the time, the ad, where it was shown, your address and country, whether you were signed in (and which account), and the request your browser sent: every header except the ones that carry passwords or keys, and every cookie, with the value of any cookie that signs you in or proves who you are removed so that we never hold anything that could be used as you. That includes the Google Analytics identifier, which lets us match these records with Google Analytics. For a view we also record what the page could see: whether your browser reports itself as automated, how long the ad was on screen, your window and screen size, pixel density, time zone, preferred languages, whether you use a touch screen and whether you prefer a light or dark theme. We keep these records indefinitely.

Advertisers only ever see totals: how many times their ad was seen and clicked each week.

Shop and cloud GPU links

Some pages link to shops that sell the card and to cloud GPU services you can rent by the hour. They pay us a commission if you buy or sign up through the link, and that never changes how we rank or grade hardware. When you click one, we record which link it was, the kind of page it was on, the card, the time and whether we counted the click. We don't record your address or your account with it. Once you reach the shop, its own cookies and privacy policy apply. We keep these records indefinitely.

Your account

To create an account we ask for your email address and a password. We store the password only as a hash, never as you typed it. Your username, and your bio if you add one, are public, shown with the reports, comments, discussions and votes you contribute. We record when you created the account, and whether you asked to receive email updates, and only send them if you did.

If you ask for new reports on a GPU or a model, we store which GPUs and models you follow and, once a week, email you the reports added for them and newly released models that fit your GPUs, using Amazon Web Services. We keep a record of each of those emails: when it went out, which reports it listed and whether it was delivered to the mail service. If you ticked the box asking for news when you signed up, we also send a weekly email about what was added to llamaperf. We keep a copy of every email we send you, with its time and delivery status, with no end date. A blind copy of each weekly email also goes to the site owner's inbox. Every email has a link that stops them, and you can change what you follow on your account page.

Each account also has a key for connecting a coding agent to our tools, which submit your benchmarks and manage your ads. It is stored encrypted and shown only to you.

You can also connect an app such as ChatGPT to those tools with OAuth. We then store which app you connected, what you allowed it to do, when, and when it was last used, and we keep its tokens only as hashes. The app that connects registers its own name and return address with us. You can disconnect it at any time on your account page, which stops it at once.

Reports and news you submit

When you submit a performance report or a news link we store what you sent, the source link, and your email and address, which we use to limit abuse. To pull the figures out of a report, its text is sent to an AI model: DeepSeek's, through DeepSeek's own service. Approved reports are published.

If you upload screenshots, we store them with your submission, re-encoded with their metadata removed, and send them to Google's Gemini model through OpenRouter, which writes out the text in them. Only our moderators can see the screenshots. The text read from them is kept as your submission's source.

Many reports come from public posts on Reddit and other public web pages. We link to the source and show the author's name as it appears there.

When a moderator edits or removes a report, or changes the hardware and model data behind the site, we keep a record of the change: what it was before and after, who made it and why. We keep these records indefinitely so a change can be checked and undone.

Contacting us

The contact form and the feedback button in the corner of every page send your name, email and message to our inbox by email, using Amazon Web Services. The feedback button also sends the address of the page you wrote from, and your email is optional there; if you are signed in and leave it blank, your account's address is used so we can reply. Cloudflare Turnstile checks the form is filled in by a person. We log that a message was sent, with your address and email.

Advertising with us

Payments for sponsored weeks are handled by Polar, which processes your card details; we never see them. We store your ad, the weeks you booked, the order reference and the amount paid, and we email you about your booking and review.

Cookies and browser storage

  • A sign-in cookie, while you are signed in.
  • A cookie that remembers you dismissed the sign-up prompt, for one week.
  • Google Analytics cookies.
  • StepMetrics' stepmetrics_id cookie, for 400 days, to recognise a returning browser.
  • Cloudflare cookies, when Cloudflare checks that your browser is not a bot.
  • In your browser's own storage: your light or dark theme, the GPU or Mac you saved as your rig (until you clear it), whether you said no to a suggested card, which reports you have viewed recently (to decide when to suggest signing up), and, for the current tab only, which version of an ad you were shown and which ad views were already counted.

Who else handles data

Cloudflare (network and bot checks), Google (analytics, and reading uploaded screenshots through OpenRouter), Amazon Web Services (sending email), DeepSeek (reading submitted reports) and Polar (payments). We do not sell personal data.

How long we keep it

Server request logs: 14 days. Everything else, including ad and site activity records, is kept until you ask us to delete it.

Your choices

You can ask for a copy of your data, for it to be corrected, or for your account and what is linked to it to be deleted, through the contact form. There is no self-service account deletion yet, so we handle these requests by hand. You can block analytics cookies in your browser without losing access to anything on the site.

Changes

When what we collect changes, we update this page and the date at the top.