Tenurewell 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 Tenurewell app for Zendesk Support (the "App") processes, where it is kept, and your choices. It covers only the App, not Zendesk's or Recurly'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 Recurly site or sites (with the API key you create).
- Your Recurly private API key is stored by Zendesk as a secure setting. Zendesk adds it to requests on their way to Recurly's API (v3.recurly.com or v3.eu.recurly.com); the key is never sent to agents' browsers and Great Work never sees it.
- The App keeps nothing outside Zendesk and Recurly: 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, brand and requester (name, email); on user profiles the user's id, name, email | To find the matching Recurly account and choose the Recurly site | Read from Zendesk into browser memory while the App is open |
| The requester's other email addresses (identities), and if your admin set a mapping, their user record (one user field, external id) | To match every address and the mapping you chose | Read from Zendesk into browser memory |
| Recurly accounts matching those emails or codes, and for the account shown: subscriptions (plan, add-ons, coupons, dates, status, amounts), recent and past-due invoices (amounts, dates, status, dunning emails sent), recent transactions (amounts, dates, status, card type and last four digits, decline messages), credit balance and pending line items, card expiry month and year | To show the billing picture to the agent | Read from Recurly into browser memory while the App is open |
| An action the agent confirms (refund, cancellation or reactivation, pause or resume, renewal date, coupon, credit, collection of a past-due invoice) | The purpose of the App | Sent to your Recurly site |
| A note on the Recurly account for each action, with the Zendesk ticket number and the agent's name (unless your admin turns it off) | So your finance team can trace changes in Recurly | Written to the account in your Recurly site |
| 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 key), and the agent's id, name, role and groups | To show the plan, apply who may take actions, and name the agent in notes | Read from Zendesk |
Recurly's account record includes a hosted login token for the customer's account pages; the App drops it as soon as Recurly's response arrives and never shows or uses it. When the sidebar closes, everything it held in memory is gone. What the App wrote stays in your Zendesk and Recurly 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, card details, passwords or keys) 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 Recurly API of your own Recurly sites. 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. Recurly requests go through Zendesk's proxy with the key in a secure setting that can only be used as the Basic authentication user name, and only toward Recurly's two API hosts. Every write carries an idempotency key, so a retried request is never applied twice. Actions are off for everyone except admins until an admin allows more roles, every action needs a confirmation, and refunds and credits above limits you set need an admin. 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, the refund and credit limits and the coupons agents may apply, and can uninstall at any time. Uninstalling deletes the stored keys; revoke the API key in Recurly as well. Notes and tags already on tickets stay until you delete them.
- Requests about personal data in your Zendesk or Recurly 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.