Privacy

This notice covers the public Beta Cadence website and its embedded editor area. Public visitors do not need an account. Site editors authenticate with the separate Sanity and GitHub services, which process editor account information under their own terms and privacy notices.

Beta Cadence is an independently operated website based in the United States. Its controller and operator is Bradley Fosler. The site operator controls the editorial dataset, analytics configuration, and the purposes described in this notice. Hosting, analytics, content-management, domain, and project providers may act as service providers or as independent controllers under their own notices.

Like most hosted websites, the infrastructure serving this site may process request and diagnostic information such as an IP address, requested URL, date and time, browser or device details, referrer, response status, and security signals. This information is used to deliver pages, prevent abuse, diagnose failures, and understand service performance.

Vercel hosts the application. Cloudflare manages the site’s domain and may also process requests when its proxy or security features are enabled. Sanity hosts the editorial release dataset and editor workspace.

When a Google Analytics measurement ID is configured, the site offers a clear analytics choice. Consent Mode defaults analytics storage, advertising storage, advertising user data, and ad personalization to denied. The Google Analytics tag does not load until “Accept analytics” is selected. Accepting grants analytics storage only; the advertising settings remain denied.

After consent, Google Analytics may process page URLs and titles, referrers, general device and browser information, approximate location, engagement data, and identifiers used to distinguish visits. The site is designed not to send names, email addresses, credentials, or free-form visitor text to Google Analytics.

As product measurement is connected, structured events may describe actions such as viewing a release or forecast, filtering a platform, exporting a calendar entry, following release notes, interacting with a timeline, sharing a release, or requesting a notification. Event properties are limited to product context such as platform, version, confidence label, sample size, or action type—not the visitor’s typed content.

A direct load of the /studio editor route never initializes Google Analytics or shows the analytics prompt. The public site does not link into Studio. If an unexpected client-side transition enters the editor from an already measured public page, the application forces a full reload to remove the loaded tag.

• Decline analytics when the preference prompt appears; the Google Analytics tag will remain unloaded.
• Use the site’s “Analytics preferences” control to change a saved choice. The preference itself is stored in the browser’s local storage so the site can remember it.
• Clear site storage in the browser to remove the saved preference and any analytics cookies already stored.
• Google also offers a Google Analytics opt-out browser add-on.

Google Search Console provides the site operator with search and indexing reports, such as queries, impressions, clicks, ranking position, and crawl issues. It does not require a separate analytics tag on this site. Google independently controls the information it processes when people use Google Search.

• Requests, security signals, and diagnostics are processed as reasonably necessary to deliver, protect, and maintain the site and to pursue the legitimate interest in operating a reliable public reference.
• Optional Google Analytics is processed only after consent. That consent can be withdrawn through “Analytics preferences.”
• Public corrections and feedback are processed because the sender chose to submit them and because reviewing the public dataset is a legitimate editorial interest.
• Information may also be processed when necessary to comply with a legal obligation or protect the rights and safety of the site, its operator, or others.

These descriptions are intended to explain the site’s practices, not to limit rights that apply under a visitor’s local law.

Advertising is not currently active. The site does not currently load Google AdSense, Google Ad Manager, or another advertising tag. The presence of this notice or an ads.txt file alone would not mean that ads are running.

If advertising is introduced, this notice will be updated before activation to name the provider and explain the information used. Required consent and opt-out controls will be added for applicable regions, and paid placements will be labeled. Advertising will not be used to alter the historical dataset or forecast calculation.

Depending on where a visitor lives, applicable law may provide rights to request access, correction, deletion, portability, or restriction of personal information; to object to certain processing; to withdraw consent without affecting earlier processing; and to complain to a local data-protection authority.

The on-site analytics control handles consent choices without requiring a request. For another privacy request, use the private role address shown below when configured. A request may require enough information to identify the relevant record and verify that the requester is entitled to it. Beta Cadence cannot directly fulfill requests for information controlled independently by Google, GitHub, Vercel, Cloudflare, Sanity, or another provider.

General feedback and data corrections can be submitted through the contact page. Reports opened in the project’s GitHub repository are public, so do not include private information, credentials, or anything you do not want published.

Privacy questions that require a private reply can be sent to business@bradleyfosler.com.

Information is processed by service providers only as needed for hosting, domain delivery and security, editorial content, consented analytics, and project communication. Those providers may process information in countries outside the visitor’s own. They maintain their own privacy notices and legal obligations.

• Vercel Privacy Policy
• Cloudflare Privacy Policy
• Sanity Privacy Policy
• Google Privacy Policy and Google’s information for partner sites
• GitHub General Privacy Statement

Information may also be disclosed when reasonably necessary to comply with law, protect the site or its users, investigate abuse, or complete a legitimate transfer of the project. There is currently no advertising-data sale or cross-context behavioral advertising program on the site.

The analytics choice remains in local browser storage until it is changed or site storage is cleared. Before GA4 is activated, its user-level event-data retention will be configured to two months; aggregated reports may remain available longer. Operational and security records are retained under provider settings for as long as reasonably needed to deliver, secure, and troubleshoot the service.

Public GitHub submissions and their revision history can remain visible after an issue is closed. Editorial source records are retained while useful to document and correct the public dataset. Legal, fraud-prevention, or security needs may require a longer period. Provider-controlled records remain subject to the relevant provider’s settings and policies.

The site is a general technical reference and is not directed to children under 13. It does not ask public visitors to create an account or submit a birth date. If a future feature intentionally collects visitor contact information, this notice and the feature design will be reviewed before launch.

This notice may change as the site adds features, vendors, or advertising. The date at the top will change when a material update is published. Continued availability of an old cached copy should not be treated as the current notice.