Privacy

Last updated October 4, 2026. This page describes the services and data handling actually in use on whynba.com, published by Dune Entertainment LLC.

Advertising (Google AdSense)

Public pages load Google AdSense (publisher ID ca-pub-3483557454826284). When ads load, your browser connects to Google services such as googlesyndication.com, doubleclick.net and adtrafficquality.google. Google and its partners may use cookies, device identifiers and information about your visit to show and measure ads and to detect invalid traffic. Google explains this in How Google uses information from sites or apps that use its services. You can review ad personalization at My Ad Center.

Consent messages (Google Funding Choices)

The site loads Google’s consent-messaging service (fundingchoicesmessages.google.com). When a consent message is shown, Google stores your choice in cookies for this site, such as FCCDCF and FCNEC.

Analytics (Google Analytics 4)

We measure visits with Google Analytics 4 (property G-PP075W65TH). It loads on public pages for visitors who are not signed in to the site’s administration and sets first-party cookies such as _ga and _ga_PP075W65TH. Google receives page addresses, referrers, browser and device information, and your IP address as part of the connection. Google’s handling is described in its Privacy Policy. You can block Google Analytics with the Google Analytics opt-out browser add-on.

Delivery and security (Cloudflare)

whynba.com is delivered through Cloudflare, which receives every request, including your IP address, to cache, deliver and protect the site. Pages also load Cloudflare’s browser beacon (static.cloudflareinsights.com), which reports page-load measurements to Cloudflare. See the Cloudflare Privacy Policy.

Our server logs and backups

Our web server records each request: the visitor IP address forwarded by Cloudflare, date and time, requested address (including query parameters such as a selected time zone, teams or search terms), response status, referrer and browser user agent. These access logs are rotated daily and kept for 14 days. The site database is backed up daily; copies on the server are deleted after about a week, and encrypted backup copies are also stored off the server.

Reactions and comments

When an article’s reactions load, the site sets a random identifier cookie, wn_reader (HttpOnly, one year), so it can recognize your own reaction. The server stores a keyed hash of that identifier with your reaction, not the identifier itself. Comments store the text and the optional name you enter and are published immediately; no email address or IP address is stored with a comment. To limit abuse, the server keeps a keyed hash of your address for up to ten minutes. To ask about a comment you posted, contact us using the details below.

Preferences saved in your browser

Saved articles are kept in your browser’s local storage, and the automatic next-article setting in session storage. Neither is sent to us. Game time-zone and team-following choices are described below.

Embedded media

Instagram, YouTube and X embeds connect to their providers only after you choose to load them. The provider then receives connection information, including your IP address, and may use cookies or similar technologies under its own policies. Team logos, player headshots and video thumbnails are served from this site’s own image cache. Links to other sites take you to services with their own policies.

Site administration

WordPress sets cookies for editors who sign in to the administration area. Visitors do not need an account.

Contact the editorial desk

[email protected] · Dune Entertainment LLC

Technical diagnostics

Browser failure reporting is enabled. When enabled, the site can send up to three failure categories per page: an uncaught site-script error, an unhandled promise rejection, or a site script that failed to load. It sends no error text, stack, page address, search term or visitor identifier, and sets no diagnostic cookie or browser-storage identifier. Browser reporting respects Do Not Track and Global Privacy Control.

Failure history contains daily category counts and first/last observation times. Reports cover fourteen UTC calendar days; an hourly task removes older rows, so cleanup can be delayed if the worker stops. Separate request protection uses a keyed, minute-specific address hash, not a raw IP address; expired quota records are removed by scheduled cleanup. Your address still reaches the server as part of ordinary HTTP delivery. Web server access logs are described in the server logs section above.

Game time zone

Game times can use the time zone reported by your browser. Choosing a game time zone saves that preference in local storage on this device, without an account or analytics event. Choosing Device time zone clears a saved override. If storage is unavailable, your choice lasts only on the current page. Opening a scores or schedule view includes its time zone in the request URL, where it may appear in ordinary server logs. No precise location is requested.

Team following in your browser

Following is optional and uses local storage on this browser to save selected NBA team identifiers. It does not require an account, set a tracking cookie, or send a follow/unfollow event to an analytics service. Choices remain until you clear them on the Teams page or clear this browser’s site data. They do not automatically sync to other devices. When you open a filtered scores, schedule or report view, its selected team identifiers are included in the URL sent to this site and may appear in ordinary server request logs. If storage is unavailable, the page explains that changes are temporary.