Historical v1.11.2 telemetry
V1 behavior is different from v2
Section titled “V1 behavior is different from v2”The 1.11.2 package includes instrumentation enabled by default. Its telemetry option is active, not the compatibility no-op found in later v2. This archive does not run that package or emit its package-usage events while you read it. Website analytics are a separate concern.
Opt out
Section titled “Opt out”useBroadcastChannel('my-channel', { telemetry: false });
// Or through the provider:<BroadcastProvider channelName="my-channel" options={{ telemetry: false }}> <App /></BroadcastProvider>;The tagged implementation collects structural mount/method signals such as the hook/provider entry point, names of supplied non-default options, callback shape, batching/browser support, and method names used once per page session. Its historical notice describes a random per-page session identifier and batched delivery to Mixpanel when the page hides or after 30 seconds.
Consult the original tagged telemetry notice and tagged instrumentation code for historical detail. The old notice’s legal/anonymity conclusions are historical assertions, not a fresh legal assessment by this archive. This page does not promise that the historical service endpoint is still maintained.
Historical sources
Section titled “Historical sources”The archive keeps version-specific behavior but corrects misleading prose against that version’s code. It is not a verbatim reproduction of the historical README.
