Privacy

• Device SoC model + vendor + RAM size + Android version.
• Raw measurement ratios and the computed sub-scores.
• Thermal status and battery percentage at the moment the bench ran.
• The ClientKey id used to sign the submission.
• Optional: extended hardware info (CPU clusters, GPU vendor/renderer, sensor names, kernel fingerprint). Disabled by default in the upload payload until you opt in.

No IMEI. No MAC address. No IP geolocation. No account login. No contacts, files, installed apps list, location, microphone, or camera. The app requests zero runtime permissions beyond the standard INTERNET and notification access.

The Android app shows a single Google AdMob banner at the bottom of the Home screen. No ads appear during a benchmark run, on the Results screen, or anywhere on this website. To serve the banner, AdMob may read your device’s Advertising ID (resettable from Android Settings → Google → Ads) and minimal request metadata. In the EU/UK/CH, a consent dialog asks whether you accept personalized ads on first launch — you can decline and still use the app normally. Full details: Google’s ads policy.

Scores need device + hardware context to be meaningful when compared. That’s it. Knowing your phone is a Pixel 8 Pro with 12 GB RAM on Android 15 is what lets the leaderboard show a useful median for “Pixel 8 Pro on stock OS.”

Run data lives in a Postgres database on a Debian VM we control. No third-party analytics, no Google Tag Manager, no Facebook Pixel, no Sentry, no Datadog, no LogRocket. The only outbound traffic from this website is to its own database. The Android app additionally talks to Google AdMob (see the “Ads” section above) for the Home-screen banner only.

Every submission is HMAC-SHA256 signed with a per-version key, so a specific build can be revoked (set the matching ClientKey row to inactive) without affecting any historical data already submitted.

Android → Settings has a Submit runs to leaderboard toggle (default ON). Off → runs stay 100% on-device and never leave the phone. You can still share screenshots and the PNG score card from the Results screen.

WSA / AVD scores are detected and never submitted — emulated GPU and sensor stacks don’t represent any real device, so leaking them into the leaderboard would just add noise.

This website uses no cookies. No localStorage or sessionStorage outside the Next.js SSR cache. We don’t need a cookie banner because we don’t set any cookies.

Want a specific run deleted? Mail feedback@fastandfast.com with the Run ID (the XXXX-XXXX identifier from the URL or Results screen) and we’ll purge it.