1. Who is responsible and what this covers
The proposed operator is [LEGAL OPERATOR NAME], based in Malaysia, at [BUSINESS OR SERVICE ADDRESS]. Privacy contact: [PRIVACY CONTACT AND CONTACT PERSON]. This notice covers Chatge services that expressly link to it and the processing described in Product Details.
It covers account holders, team members, visitors and people whose messages or stream activity are received through a connected channel, including viewers who never create a Chatge account.
Chatge determines how it runs accounts, security and service administration. A streamer or organization may separately decide how to use viewer data in its workspace. Depending on the arrangement, Chatge may process some data on that customer's instructions. Responsibilities and any required data-processing agreement must be confirmed; a streamer and Chatge are not automatically interchangeable controllers.
This is an unfinished review draft, not an effective notice. It does not request or record consent. Reading it or using a connected platform does not grant blanket permission for processing.
2. Information and where it comes from
Depending on the product, enabled feature and provider permissions, information involved includes:
- Account and connection information from you or a provider: provider user/channel IDs, usernames, display names, profile images, approved permissions, connection status and an email address where supplied for an enabled purpose.
- Authentication information: session identifiers, linked-account references, authorization/refresh credentials, authorization records and security events. The relevant service uses credentials to authenticate and operate an authorized connection.
- Workspace information from owners and invited members: membership, roles, invitations, selected channels, preferences, stream settings and action requests/results.
- Chat and stream activity from providers or your instructions: message text, sender IDs/names, timestamps, channel references, badges/roles, stream title/category/status and event details such as a subscription or tip when enabled.
- Technical information from the service and infrastructure: requests, errors, security records, browser/device information and network addresses where logged. Exact production logging fields and providers remain under review.
- Information you choose to send when requesting support, reporting abuse or exercising a privacy right.
3. Why information is used
The intended purposes are sign-in, linking authorized identities, providing enabled chat/streaming tools, managing access, carrying out requested actions, investigating failures or abuse, support and applicable legal obligations. History, where enabled, helps authorized users follow a conversation in the relevant channel.
Required and optional information must be distinguished at collection. Identity/session information is needed for sign-in; membership information is needed for restricted access. Without them, that account feature cannot operate. Optional integrations can remain disconnected, but their features will be unavailable. A public demo does not require connecting a provider account.
Proposed policy: do not sell personal data, use it for cross-context behavioral advertising, or use private workspace content to train general-purpose AI models. These proposed commitments require an audit of all products, service providers and deployment settings before adoption.
4. Basis for processing
The operator must establish the permission or other legal basis required for each purpose under applicable laws, including Malaysia's Personal Data Protection Act 2010 as amended where applicable. OAuth authorization grants technical access; it does not settle every data-protection obligation.
If EEA or UK data-protection law applies, the proposed mapping is: contract for information necessary for a user's requested account features; legitimate interests, after assessment, for proportionate security/abuse prevention; legal obligation for a specific applicable duty; and consent for optional processing where required. Viewer-message processing needs its own role and legal-basis assessment; it cannot rely on a contract a viewer never entered.
Where consent is the basis, explain the purpose and choice separately and provide withdrawal. Withdrawal does not invalidate earlier lawful processing. This notice is not consent to all uses or all international transfers.
6. Cookies and information on your device
The web applications use first-party cookies for sessions and sign-in/authorization flows. Browser storage remembers interface choices such as layout, chat highlights and demo settings. Blocking required cookies can prevent sign-in; clearing preferences resets the associated choices.
The reviewed Control source does not use browser local storage as its private chat-history archive. This does not mean no data reaches your device: rendered pages, browser caches and device backups can contain information. Android/desktop applications need their own verified device-storage details.
Essential sign-in cookies differ from optional advertising or analytics technology. Before optional tracking is introduced, update the notice and controls and obtain consent where required. Infrastructure cookies and lifetimes must also be included in the final inventory.
7. Retention, disconnecting and deletion
The proposed rule is to keep identifiable information only as long as necessary for its stated purpose, legal obligations or a lawful claim, then delete it or make it irreversibly anonymous. The detailed schedule and cleanup processes are not yet approved or verified for every category.
Control's chat-history implementation limits access to eligible collected messages to 30 days from first receipt. This is a visibility limit, not a promise of physical erasure after 30 days. Automatic physical expiry is not implemented or approved. Feature availability depends on the deployed release and connection state; history may also be incomplete.
Signing out ends the relevant session; disconnecting changes future authorization. Neither deletes existing messages, action records, provider copies, backups or other users' copies merely by virtue of that action. Account closure and deletion requests require a separate process, subject to applicable law.
The final schedule must cover accounts, credentials, messages, actions, security logs, support records and backups, including deletion after restoration. A shorter visible history window does not define the underlying storage period.
8. International processing
The operator is based in Malaysia, but connected platforms and infrastructure providers may process information elsewhere. Being based in Malaysia does not mean all data stays there. Hosting locations, support access and onward transfers must be confirmed.
Before a transfer, identify the applicable legal condition and safeguards, including Malaysia's cross-border transfer requirements where applicable. Where EEA or UK law applies, an appropriate transfer mechanism and any required assessment or supplementary measures must also be in place. This draft does not claim any particular agreement or adequacy mechanism is already implemented.
9. Security and incidents
The reviewed Control implementation uses authorization checks, protected server-side credentials and scoped workspace access. This is not a guarantee of absolute security or a statement that all stored content is encrypted. Deployment settings, access reviews, backups and incident response must also be maintained.
Proposed operating commitment: investigate suspected personal-data breaches, take protective action and notify affected people and authorities when applicable law requires. Do not send passwords, session tokens or provider secrets in support/privacy requests.
10. Your choices, requests and complaints
Depending on applicable law and circumstances, you may request access/correction, withdraw consent, limit or object to processing, request deletion/restriction, or request portability. Rights have conditions and exceptions; this notice does not reduce rights the law gives you.
Send requests to [PRIVACY CONTACT] with enough information to identify the account, platform or channel and the request. Viewers without a Chatge account can also request help. We may need proportionate identity/authority verification. Do not send identity documents or sensitive details until a secure and necessary verification method has been explained.
The intended process is to acknowledge, assess and answer within applicable legal time limits, explain any lawful limitation and provide an appropriate review/complaint route. Where a channel owner controls processing, we may coordinate with or direct you to that owner without unnecessarily disclosing your information.
You may complain to Malaysia's Personal Data Protection Commissioner through the official JPDP website, or to a competent authority elsewhere where applicable. Contacting us first does not remove your right to complain to an authority.
11. Children and younger viewers
The proposed account policy is 18+, pending approval. It does not prove all viewers are adults. Provider messages may contain information about younger people who are not Chatge account holders.
Do not provide children's sensitive information or invite a child to create an account contrary to applicable policy. Contact [PRIVACY CONTACT] if a child's information may have been processed inappropriately. The operator must assess and address the concern under applicable law.
12. Updates and related notices
An approved notice will show its effective date, revision date and version, with material changes communicated where required. New purposes may need a new notice, legal assessment or separate consent before processing starts.
Read Product Details for the services you use. English and Bahasa Melayu versions are intended to describe the same practices. Both translations and factual accuracy need review before adoption.