Clientwell for Zendesk: Privacy Policy
Effective date: October 1, 2026 Publisher: Great Work LLC, 651 N Broad St Suite 206, Middletown, DE 19709, USA Contact: hello@greatwork.company
This policy explains what information the Clientwell app for Zendesk Support (the "App") processes, where it is kept, and your choices. It covers only the App, not Zendesk's or HubSpot's products, which are governed by their own privacy policies.
1. Summary
- The App runs in your browser inside Zendesk Support, through the Zendesk Apps framework. Great Work LLC operates no server for it and receives no data from it.
- It reads from and writes to two places only: your Zendesk account (as the signed-in agent, with that agent's permissions) and your HubSpot account (with the private app token you create).
- Your HubSpot token is stored by Zendesk as a secure setting. Zendesk adds it to requests on their way to HubSpot's API (api.hubapi.com); the token is never sent to agents' browsers and Great Work never sees it.
- The App keeps nothing outside Zendesk and HubSpot: no copies, archives, caches or indexes, no browser storage, no background collection, no analytics or usage statistics, no cookies of its own, no export, and no AI services.
2. What the App processes, and why
| Data | Why | Where it lives |
|---|---|---|
| The ticket's id, subject and requester (name, email); on user profiles the user's id, name, email | To find the matching HubSpot contact and to link HubSpot records back to the ticket | Read from Zendesk into browser memory while the App is open |
| The requester's other email addresses (identities) | To match every address they use | Read from Zendesk into browser memory |
| The number of agents and admins in your Zendesk account | To check that your plan covers your team | Read from Zendesk into browser memory |
| HubSpot contacts matching those emails, and for the contact shown: contact properties (name, email, phone, job title, lifecycle stage, lead status, owner, dates, extra fields your admin lists), the company, associated deals, recent notes, calls, logged emails and meetings (time, title or subject, note text, direction, status, owner), list names; companies matching the email domain; owners, pipelines, stage and status options | To show the CRM picture to the agent | Read from HubSpot into browser memory while the App is open |
| An action the agent confirms (create a contact, change lifecycle stage, lead status or owner, log a note, create a task or a deal) | The purpose of the App | Sent to your HubSpot account. Notes, tasks and deals carry the ticket number and link, optionally the ticket subject, the agent's name and what the agent typed; never the ticket conversation |
| An internal note and a tag describing each action, with the agent's name | So your team can see what was done | Written to the ticket in your Zendesk account |
| The installation's plan name and settings (not the token), the account subdomain, and the agent's id, name, email, role and groups | To show the plan, apply who may take actions, name the agent in notes and match the agent to their HubSpot owner record | Read from Zendesk |
When the sidebar closes, everything it held in memory is gone. What the App wrote stays in your Zendesk and HubSpot accounts under your control and their retention settings.
3. What Great Work LLC receives
Nothing from the App. If you email us for support, we receive what you send (we ask you not to send customer data, passwords or tokens) and keep it in our email system for as long as needed to help you, at most 24 months. Billing for the App is handled by Zendesk through Stripe; we receive the subscription records Stripe provides to sellers (your Zendesk domain, the plan, payment status and billing contact), which we keep as long as tax and accounting law requires.
4. Sharing
We do not sell, rent or share personal information. The App sends data only to your Zendesk account and to the HubSpot API of your own HubSpot account. We have no subprocessors for the App itself.
5. AI and model training
The App uses no AI services, and no data processed by the App is used to train any model.
6. Security
The App has no server or database to breach. It loads the Zendesk Apps framework from Zendesk's CDN. HubSpot requests go through Zendesk's proxy with the token in a secure setting that can only be used in a request header and only for api.hubapi.com. A token with read scopes only gives the panel without actions. Admins choose who may take actions and which actions exist, every action needs a confirmation, and moving a lifecycle stage back is admin-only by default. Report a security issue to hello@greatwork.company; we treat it as urgent.
7. Your choices and rights
- Admins choose who may take actions, which actions exist, which extra fields are shown and whether lists and the domain match are on, and can uninstall at any time. Uninstalling deletes the stored token; delete the private app in HubSpot as well. Notes and tags already on tickets, and records created in HubSpot, stay until you delete them.
- Requests about personal data in your Zendesk or HubSpot account go to your administrator, who controls that data. Questions about this policy: hello@greatwork.company.
- If you are in the EEA, UK or California, you have rights to access, correct and delete personal information we hold about you (in practice, support emails and billing records). Write to us.
8. Changes
We will post changes here with a new effective date and, for material changes, email the billing contact of each paying account at least 14 days before they apply.