A count. Not a profile.
Reviewed 16 October 2026. Woodhouse receives anonymous tab-session events from this site, Protocol 11 and SHOALSHOT. Other projects publish their own aggregate reports and keep their own privacy choices.
What is counted
Visits, active sessions, deliberate project-link clicks and reported gameplay starts, finishes, replays and active seconds. Active time requires a visible, focused, unpaused product with recent input. Music listening is reported separately by LoftwahFM.
The report’s measure selector separates gameplay, visits, mini-app actions and audible listening. Open a project’s source details for its exact definitions and available fields. Starts and completions are not a matched cohort; dividing them does not establish a completion rate. Browser identifiers, where a project offers optional consent, are not unique people.
Dates, gaps and comparisons
Custom reports accept inclusive UTC dates, with up to 90 days in one window and no future dates. A closed calendar window does not guarantee complete measurement. Today, the first collection day, unavailable sources and expired history remain distinct. Missing values are gaps, never zeroes. The report freezes the selected dates, figures and capture time in its permanent link and exports.
Historical production verification may be mixed into older counts and cannot always be identified or subtracted. The coverage calendar labels this legacy history. Growth findings require a source-declared comparison boundary, exact daily counts and complete adjacent UTC weeks. Bounded or sampled counters do not earn growth records. A movement in reports does not establish its cause.
History limits belong to each source: App Composer retains a bounded 35-day activity window; LoftwahFM retains accepted listening aggregates for 185 days. Woodhouse keeps anonymous raw events for 90 days and durable daily aggregates beyond that. Game-owned distinct-browser measures may need raw history that has already expired even when daily counters remain. The source details in each dated report expose its actual coverage and limitations.
What this cannot tell you
This dashboard does not currently establish portfolio cohort retention, revenue, paying customers, acquisition cost, customer value or product–market fit. It does not join identities across products or record a person’s browsing journey. Privacy choices, offline use and blocked requests can hide real activity; accepted browser events can also be fabricated. Treat this as product evidence with stated limits, not an audited business statement.
What stays private
These three sources create a random tab-session identifier. It expires after 30 minutes of inactivity. Without the separate optional choice below, it does not identify a returning browser. We store a one-way hash, event IDs and timestamps with a 90-day retention window to deduplicate reports. Expired records are removed during collection or the hourly reporting refresh. A short-lived hash of the IP address limits request volume; the address itself is never stored. No email, account ID, save, precise location, page URL or raw referrer is collected by this collector.
Daily totals and saved public reports contain aggregate numbers and may be kept indefinitely. Raw sessions and events never appear in public reports. Counts describe accepted reports, not verified humans. Offline play, network failures, browser blocking and privacy choices can cause undercounting.
Your choice
Do Not Track, Global Privacy Control, preview and designated test traffic are excluded. Add ?analytics=off to a page address to disable this measurement for that visit. Anonymous play and saved progress work independently of reporting.
This browser setting applies to Woodhouse. Protocol 11 and SHOALSHOT honour their own ?analytics=off option; Bubbles provides an explicit opt-in in its settings. There is no shared account or cross-project browser identity.
Optional: recognise a returning Woodhouse browser
Off by default. You can allow Woodhouse to remember a random identifier on this browser for up to 90 days. This adds visits to the reporting-browser count and recognises an earlier, different tab session, even on the same day. It does not identify a person, link devices, join products or measure cohort retention. Anonymous reporting works without this choice.
The identifier stays on this origin; the collector stores only a project-scoped one-way hash with private visit associations for 90 days. Daily charts and period totals count distinct retained identifiers separately. Rotating or clearing storage and expired history hide returns. Revoking this choice stops future browser associations and attempts to remove the local token; it does not erase previously accepted private associations or saved aggregate reports.