Chatge Auth
Chatge Auth provides shared sign-in for participating products. It handles linked provider identities, account/product-session references, authorization grants and revocation/security information. Where enabled, it also holds provider credentials and routes authorized events or actions for a product.
Linking identities is not permission for every product to access every capability. Product permissions and workspace authorization still apply. Central sign-out affects participating central sessions; it must not be assumed to end independent legacy sessions or erase stored data.
Chatge Control
Control is a streaming workspace for connected chat, activity and authorized stream tools. It handles membership/roles, channel bindings, received messages/events, settings and action results. Public demos simulate behavior and are not evidence of connected provider operation.
Access depends on the feature and role. The prepared central provider integration and collected history currently require the owner and the authorized channel connection. Other workspace features can be available to invited members. Private history is not public or available to every moderator.
Where available, the history window is 30 days from first receipt by Control for eligible collected messages. It is not a complete platform archive or a physical-deletion guarantee. Collection gaps, disconnections and delivery limits can leave missing periods. Feature availability depends on the deployed release and connection state; check the actual release before treating it as available.
Where overlays/exports are enabled, consider who can access the link, broadcast or downloaded file. Acceptance of an action does not guarantee the audience saw it; check uncertain results before resubmitting.
Chatge Android and desktop applications
Native applications can have device-local storage and network connections to providers or Chatge services. Device storage, operating-system backups and server copies are different locations. Uninstalling an app must not be described as deleting provider/server data without verified evidence.
Some releases may use independent authentication. Describe shared Auth adoption, local credentials, message persistence, diagnostics and backups for the specific release; web-app behavior cannot simply be copied into a native-app notice.
MultiChatge
MultiChatge needs a verified supplement for its existing accounts, connected channels, messages and cloud profiles where enabled. A planned move to shared Auth does not mean an existing installation has moved or that central sign-out controls its sessions.
Suggested short notice for a channel
Draft for a channel owner to adapt: ‘This channel uses Chatge tools to display and manage chat and stream activity. Messages, usernames and related activity may be processed by Chatge and authorized channel staff. Read the Chatge Privacy Policy and this channel's own privacy information for details and privacy contacts.’
Replace ‘Chatge Privacy Policy’ with the approved public link and add the channel's contact and purpose-specific details. This short notice explains processing; it does not itself obtain consent or make a viewer accept the Chatge Terms.