GreenChatPrivacy policy
This draft covers the GreenChat website, workspace, customer chat, SDK and staff app. The operator, applicable regions, effective date and privacy contact are pending confirmation.
Draft for legal review · Effective date pending
Applications and inquiries
The application form collects organization and contact details, region, optional website, intended use and acknowledgment to process and review applications. Contact inquiries include your name, email, category and message. Requests may be rate-limited and logged for security. Keep credentials, payment data and unrelated personal information out of either form.
Customer and staff information
Support may process customer identifiers and profiles, messages, history, image attachments, and conversation and channel assignments. Staff accounts involve login data, organization roles, device sessions and notification registrations. When enabled, push may use device tokens and notification metadata. Payloads depend on client, server and preview settings.
Organization and GreenChat responsibilities
Organizations choose why they use support, who receives conversations and which channels are enabled. They are responsible for informing their customers. GreenChat processes service data under the applicable arrangements and handles information needed for website intake, security and operations. Formal roles, legal bases, processor terms and subcontractors remain subject to confirmation.
Access, protection and receipt codes
Organization boundaries, staff roles, channel permissions and authentication limit access. Authorized platform staff can review website inquiries. Anyone with your receipt code can see the status and applicant instructions. Keep it private. Operational access, encryption, backups and incident response details are pending confirmation.
Retention, deletion and account closure
Retention periods, deletion rules, backup expiry and account closure procedures are pending confirmation. Use the contact form to request access, correction, deletion or account closure, or to raise a complaint. The relevant organization may need to verify your identity and handle requests involving its conversations. Avoid including identity documents or full transcripts in the first message.
ContactProviders and cross-border use
When enabled, push can be delivered through Google FCM or Apple APNs. Infrastructure providers, data locations, transfer arrangements and safeguards are pending confirmation. Regional notices and processes for individual rights and transfers require review before release.
Updates and effective date
The release date, effective date, change notice and regional addenda are pending confirmation. See the cookie policy for information on browser storage.
Cookie policy