STARBOX

PRIVACY EXPLAINER

What ‘Runs in Your Browser’ Means for Starbox Privacy

The phrase runs in your browser describes where game logic executes, but it does not mean that a website produces no network requests or technical records. Starbox games generate questions, boards, and scores in the loaded page. Best scores use localStorage and are not uploaded by the game code. The hosting service can still receive ordinary web requests, and the site loads the official Google AdSense publisher tag for verification and potential advertising.

Published and reviewed August 22, 2026 · Original Starbox analysis

METHOD & EVIDENCE BOUNDARY

What this note examined

We compared the current source implementation with the published Privacy Policy, Terms of Use, AdSense tag, ads.txt file, and European regulations message described by the site. This explainer summarizes those disclosed flows. It is not legal advice, and hosting or advertising behavior may change when providers update their services or when ads become active.

Game state and best scores stay local

The arcade stores best results under the starbox-scores key in the browser's localStorage. The value belongs to that browser profile on that device. It is not a cross-device account, and the game code does not send it to a Starbox score database. Clearing site data, using a private window, or changing profiles can remove or separate the record. This local design reduces the data needed for a simple game session, but it also means Starbox cannot recover a deleted score.

A page request still reaches the hosting service

Opening a website requires a request for HTML, styles, scripts, and other assets. The hosting provider may record necessary technical logs such as IP address, request time, requested page, browser type, and error information for delivery, security, and reliability. Those logs are different from the local game score. Saying that scores are local should never be expanded into the inaccurate claim that visiting the site creates no server-side technical data at all.

Advertising code creates a separate data context

Starbox loads Google's official AdSense publisher script with publisher ID pub-1466369119300444. Google and advertising partners may use cookies, device identifiers, IP-derived location, web beacons, and similar technologies for fraud prevention, ad serving, limiting, personalization where permitted, and measurement. The root ads.txt authorizes Google as a direct seller for the same publisher ID. Loading verification code does not by itself prove that the site has been approved or that an ad was shown.

Consent and browser controls provide choices

The site has published a Google-certified European regulations message for regions where consent is required. The message can provide consent, non-consent, and settings choices before personalized advertising is used. Browser controls can also block non-essential cookies or clear this site's stored data, including local scores. These controls affect different layers: clearing localStorage removes the score record, while advertising and consent choices govern technologies used by advertising services.

LIMITATIONS

What this article does not establish

This page explains the current published implementation and is not a substitute for the full Privacy Policy or provider documentation. Users with a privacy request should use the Contact page. The site operator must update both disclosures if analytics, accounts, payments, comments, or additional advertising vendors are introduced.

See all research notes

Compare methods, measurements, design choices, and privacy details across the arcade.

Browse notes →