Your plan Local layout sample · no account or cross-domain sync

A tracker layout,
not viewer state.

This preserved concept demonstrates planning information architecture. Twitch remains the authority for personal watch progress, earned rewards, inventory, and claims.

SampleTracked-game layout

KnownPublic requirements only

UnknownViewer progress

0Notifications sent

What a real tracker would require

future privacy slice

Public requirements

Source-backed reward names, watch requirements, earning windows, eligible-channel scope and claim guidance.

Viewer state

Unknown here. Progress, earned rewards and inventory remain on the official platform unless a reviewed account source exists.

Ordering

Only known deadlines can be sorted. Unknown or conflicting windows fail closed instead of becoming a generated countdown.

Privacy

A production tracker needs explicit consent, minimum OAuth scope, export, revocation and deletion behavior.

No personal plan is calculated The earlier mock inferred viewer progress and claim state that a public browser page cannot know. This preserved route now documents the boundary instead of presenting those values as real.

Delivery belongs on StreamAlert

static handoff · nothing subscribed

One network delivery layer

StreamAlert is the proposed home for watchlists, the network Discord bot, browser push, email, RSS and webhooks. This StreamDrops page does not install an app, register a device, or send a notification.

Open the watchlist concept →

Nothing is subscribed

The linked StreamAlert pages are static, noindex product prototypes. Their controls only preview rule wording in the current tab; they do not persist preferences or contact a delivery service.

0 notifications sent No account connection

A tracker layout,not viewer state.