Heralder 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 Heralder app for Zendesk Support (the "App") processes, where it is kept, and your choices. It covers only the App, not Zendesk's products, which are governed by Zendesk's own privacy policy.
1. Summary
- The App runs entirely 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.
- Every request the App makes goes to your own Zendesk account, as the signed-in agent, with that agent's permissions.
- The App keeps nothing outside Zendesk: no copies, archives or indexes of your customers, tickets or files, no browser storage of customer data, no background collection, no analytics, no cookies of its own, and no AI services.
- Great Work LLC cannot see your campaigns, your customers or who used the App.
2. What the App processes, and why
| Data | Why | Where it lives |
|---|---|---|
| A CSV file you choose (emails, names and any other columns) | To build the audience and fill merge fields | Read in your browser's memory for the session; sent only to your Zendesk account, as the tickets you ask it to create |
| Users, organizations and tickets matched by your searches: name, email, locale, tags, organization, user fields, requester ids | To build the audience, fill merge fields and skip people you excluded | Read from Zendesk into browser memory for the session |
| Agents, suspended users, users with the opt-out tag, recent Heralder ticket requesters | To skip them | Read from Zendesk into browser memory for the session |
| Active triggers, groups, brands, forms, custom statuses, support addresses, macros | To fill the settings form and check which trigger will email the tickets | Read from Zendesk into browser memory for the session |
| Campaign tickets you create | The purpose of the App | In your Zendesk account, like any ticket |
| A campaign log ticket: campaign name, message template, ticket settings, the audience description (a file name and fingerprint, or a search), counts, resumes and undos, and who sent it | Audit trail, progress and resume | In your Zendesk account, as an internal ticket; it never lists recipients |
| The installation's plan name and settings, and the signed-in agent's id, name, email and role | To apply plan limits and record who sent a campaign | Read from Zendesk; the sender's name and id are written to the log ticket |
When you close the App, everything it held in memory is gone. Data the App wrote into Zendesk stays there, under your control, and follows your Zendesk retention and deletion 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 API tokens) and keep it in our email system for as long as needed to help you, at most 24 months. Billing 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 own Zendesk account. We have no subprocessors for the App itself; for billing, Stripe and Zendesk act under their own terms.
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 and calls only your Zendesk account. Message text and merge values are escaped before they are placed in a ticket comment, so customer data cannot inject markup. Report a security issue to hello@greatwork.company; we treat it as urgent.
7. Your choices and rights
- Admins can restrict the App to specific roles or groups, or uninstall it at any time. Uninstalling removes the trigger the App installed; campaign tickets and log tickets stay in Zendesk until you delete them.
- People who should never receive a campaign can be given the opt-out tag.
- Requests about personal data in your Zendesk account go to your Zendesk 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.