- Channel3 keys and Twitch secrets remain in the API environment and never enter browser bundles.
- Production startup rejects demo mode or missing Channel3, Extension JWT, and EventSub secrets.
- Twitch Extension JWTs are verified with HS256, role-checked, and bound to their signed
channel_idclaim. - Creator approval also requires the product ID to appear in the verified channel's current Channel3 topic results before it is stored; per-channel and active-channel approval caps remain enforced by the shared store mutation.
- EventSub uses the raw request body for HMAC verification, enforces timestamp freshness, and rejects duplicate message IDs within the replay window.
- Only a broadcaster's own
!gear <topic>chat message changes stream context. - Viewer intent accepts only channel, product, and action. Product membership is revalidated; no viewer ID is required in the request or persisted as analytics.
- Low-count aggregates are hidden and visible totals are bucketed in groups of five.
- SafeSearch defaults on. Weapons and weapon-specific accessories remain blocked even if SafeSearch is disabled.
- Product and image URLs require HTTPS, standard TLS port, no embedded credentials, and configured hostname allowlists.
- CORS uses an explicit origin list, JSON bodies are size-limited, and viewer-action limits run after JWT verification. The short-lived in-memory key uses the signed Twitch opaque user ID when present, with a request-address fallback if it is absent; no linked identity is requested. See Twitch's Extension JWT schema.
- When
DATABASE_URLis configured, mutable state uses a Postgres transaction and row lock. Otherwise the store can use private Blob with conditional-write retries, or a private local file with atomic replacement. Metric and active approval channel/product cardinality have application caps; topic cardinality does not. - Container context excludes
.env, data, build output, logs, and archives; runtime runs as an unprivileged user.
Before a multi-instance public launch, replace process-local replay and rate-limit state with shared TTL storage, add gateway-level abuse controls and observability, and rotate credentials through the deployment platform's secret manager. Catalogue route and Channel3 budgets are also process-local, so replicas multiply the effective limits. The current Render deployment uses managed Postgres; a free database has an expiry and operational limits. These are scale and operations gates, not hidden claims of the hackathon build.
Intent metrics store aggregate action counts without viewer IDs. Twitch's signed opaque user ID is used only as a short-lived in-memory rate-limit key; the request address is used transiently if that claim is absent. Neither is persisted in analytics or sent to the ranking store. The signed Twitch channel ID is retained, and Twitch, Channel3, retailers and hosting infrastructure may process their own data. Ranking uses the same published five-action buckets returned to callers, so suppressed per-product counts cannot independently affect result order. This ranking change is included in the Render API release recorded in validation. Published totals remain action counts rather than unique-viewer counts; bucketing does not establish anonymity or differential privacy.
StreamCart does not build viewer profiles for advertising. Product links may earn commission; a viewer who follows one leaves StreamCart and Channel3 and the retailer may process click and device data under their own policies. Channel3 describes its click analytics and optional advertising cookies in its privacy policy. Do not describe this as an end-to-end absence of tracking.