Privacy

FrameReady uses saved hardware data to improve future comparisons.

The Can I Run tool works without an account. Saved rig results and optional reports are used for summary views, not public personal profiles.

What the tool uses

  • Selected game and platform.
  • CPU and GPU choice, RAM band, storage type, target resolution, and target FPS.
  • Readiness result, evidence label, and main weak-point category.
  • Optional upgrade intent, benchmark report, issue report, or settings preset.

Browser detection

Browser-assisted detection is optional. It only runs after you click the detection button. A browser can expose limited signals such as approximate memory, logical CPU threads, platform hints, and sometimes a GPU renderer string through WebGL.

  • Detection can be missing, rounded, masked, or wrong.
  • Detected values are suggestions unless FrameReady can match them to a broad class.
  • Manual selection stays available, and manual edits override detected values.
  • Raw browser strings are used client-side for matching where possible.

What is not collected

  • No email, name, phone number, account login, or exact location is required for the tool.
  • No free-text personal notes are accepted in the current report forms.
  • No browser detection runs silently on page load.
  • No GA4 or external analytics script is active.
  • Ad placeholders may appear, but Google ad code loads only after AdSense is configured.
  • Affiliate click redirects may store product category, page path, and recommendation type without personal identifiers.
  • FrameReady does not sell raw personal records.

Ads and affiliate links

FrameReady may show labeled ad placeholders and disclosed affiliate links. Real ads should stay separate from forms, result actions, admin pages, and private APIs.

  • Ad placeholders are labeled as advertisements.
  • AdSense code loads only when the publisher and slot settings are configured.
  • Affiliate redirects do not require an account, name, email, or exact location.
  • Monetization data should stay aggregate and should not expose personal records.

How saved data is used

If you choose to save a result, FrameReady stores the confirmed rig fields and result data. Private summary views are designed around grouped counts, not personal profiles.

  • Small groups are hidden before summary counts are shown.
  • Private submission APIs return noindex and no-store headers.
  • Private pages are marked noindex.
  • Optional email alerts are future work and must stay separate from rig and report data.