Privacy

Current code and services

This build is a static, nonindexable site. It has no reader accounts, comments, payment flow, analytics tag, advertising tracker, newsletter form, waitlist, provider endpoint, or first-party cookie logic. Spec & Signal does not currently collect names, email addresses, VINs, precise garage information, or search terms through the site.

Site search uses a static index downloaded from Spec & Signal and processes the query in your browser. A committed query is retained only in the page URL fragment so reload, Back, and Forward work; fragments are not sent in the HTTP request. Search text is not stored by the site, sent to a search provider, or included in analytics.

Normal hosting infrastructure may process technical request data when the site is eventually deployed. No hosting service or retention policy is configured in this batch, so this page does not make claims about a future provider.

Optional audience measurement

The repository now contains a strict measurement contract and a no-op adapter for local qualification. A public GA4 measurement ID is recorded in the checked-in build configuration, but measurement, tag loading, and network transport remain disabled. The production artifact contains no consent client, Google tag, analytics request target, analytics cookie logic, or measurement property ID.

The planned production approach uses basic consent: the Google tag must remain unloaded unless a reader explicitly allows optional audience measurement. Declining cannot block reading, search, newsletter access, or any other site function. A policy-versioned first-party browser choice is qualified only in a production-excluded test surface; this build does not read or write that choice.

Every declared event requires consent and allows only fixed categories, bounded counts, or query-free paths and stable content identifiers found in a checked-in public-value registry. Automatic pageviews and affiliate measurement are off. Search terms, email addresses, names, phone numbers, VINs, precise garage data, arbitrary free text, full source or outbound URLs, explicit IP-address parameters, subscriber state, and provider-to-analytics identity joins are rejected. Search pageviews may use the registered /search/ path only; the query and fragment are excluded. Source interactions may use a registered repository-owned source ID, never the destination URL.

Before any live measurement can launch, Spec & Signal must document retention, access, deletion, regional behavior, a monitored privacy contact, and the final property configuration. Live qualification must also prove that automatic and enhanced measurement are off, consent and revocation work as described, and DebugView receives only the declared event fields. The code can reject an IP address as an event parameter; it does not claim that a future third-party network request would reveal no connection metadata to that provider.

Before newsletter signup can launch

The weekly briefing is coming soon, but Spec & Signal is not collecting email addresses or operating a waitlist. Launching a waitlist would create the same subscriber-data obligations as launching signup, so no email field will appear until an appropriate provider and complete consent, privacy, retention, deletion, abuse-prevention, and sender-compliance controls are approved.

If signup launches later, it will use double opt-in. Subscriber state will belong with the approved mail provider, not in Git or Google Analytics. Provider privacy, retention, deletion, bounce, complaint, and unsubscribe behavior must be reviewed and reflected here before the form is enabled.

This policy must change whenever the actual data flow changes. The identity gate prevents a placeholder publisher or unmonitored contact assertion from qualifying for staging or release. See Contact for the current structured status.