ZD Recipes Terms and Conditions

Version 1.0, 20/10/2026

1. Who we are and what this covers

ZD Recipes (zdrecipes.deltastring.com) is a set of one-off digital services run by Deltastring Ltd (“Deltastring”, “we”, “us”), a company registered in England and Wales, company number 15214660, registered office The Office, 37 Leatherhead Gardens, Hedge End, Southampton, England, SO30 2TY, VAT number 471506205.

These terms apply when you buy a recipe (“Recipe”). “You” is the person or organisation buying. Recipes are sold for business use only. By buying, you confirm that you are buying for the purposes of your business, organisation or profession and not as a consumer, and that you can bind the organisation you buy for.

These terms are separate from the terms of service for the Deltastring app. If you also use the app, the app terms apply to that use.

2. What you get

2.1 A Recipe is a single defined job run against your own Zendesk instance through Deltastring, for example a report, a check, a comparison or a set of configuration changes. Each Recipe has a description page that says what it does, whether it only reads or also writes, and its price. That description is part of your contract.

2.2 Each purchase covers one connected Zendesk instance and one run, unless the description says otherwise. A re-run after a failed run is included.

2.3 What you receive is the outcome stated in the description: normally a result you can read in Deltastring, and, for Recipes that change configuration, the changes applied to your Zendesk once you approve them.

2.4 Some Recipes are fulfilled by us by hand rather than by the self-serve flow. The terms are the same either way.

2.5 We may change the list of Recipes and their prices at any time. A change does not affect a purchase you have already made.

3. Your Zendesk and your responsibilities

3.1 You are responsible for your Zendesk instance, its configuration, its data and who may access it. Deltastring is not your Zendesk administrator and does not take over that responsibility.

3.2 You confirm that you are entitled to connect the Zendesk instance and to authorise the work, and that any credentials or tokens you give us are yours to give.

3.3 You choose the instance. Running a Recipe against a sandbox first is strongly advised for any Recipe that writes.

3.4 You are responsible for reviewing the preview (section 4) before you approve. If you approve a change, you are instructing us to make it.

3.5 You are responsible for any effect of a change on your own business processes, on your customers, on your integrations and on third parties that depend on your Zendesk. We can show you what we can see in the configuration. We cannot see everything that depends on it, such as an external system calling a webhook.

3.6 You must have the Zendesk plan and permissions the Recipe needs. Some Zendesk features depend on the plan. A Recipe may not be able to do everything on a lower plan. We will tell you in the preview where we can see this.

3.7 Zendesk is a trade mark of Zendesk, Inc. Deltastring is not affiliated with, endorsed by or sponsored by Zendesk. Your use of Zendesk remains subject to your agreement with Zendesk, including its API limits.

4. How a Recipe runs: preview, approval and undo

4.1 Read first. A Recipe begins by reading configuration from your Zendesk. It does not read ticket content unless the description says so and you have switched that on. It does not store end-user or organisation records. A Recipe changes users or organisations only where its description says so, and only after you approve the preview.

4.2 Preview. A Recipe that writes shows you what it proposes to change before anything is written. The preview lists the objects affected and the before and after values.

4.3 Approval. Nothing is written to your Zendesk until you approve the preview. Where your Deltastring account has an approval workflow switched on, the approval the workflow requires also applies.

4.4 Record. For each applied change we record what changed, when, who approved it and the state before it. Where a change would destroy the only copy of the earlier state and we cannot capture that state first, we will refuse that single change and tell you why.

4.5 Undo. Where we captured the earlier state, you can ask Deltastring to restore it. Undo is available for as long as the change record is kept. For changes to user records that is 90 days.

4.6 Undo has limits. Undo restores configuration as it was when we recorded it. It cannot:

  • restore anything that Zendesk itself deletes permanently, such as an archived Help Centre article, which Zendesk does not allow to be restored;
  • reverse effects that already happened in the meantime, for example a ticket that a trigger already changed or an email a rule already sent;
  • restore configuration that someone else has changed in Zendesk since our change, without overwriting their change. We will show you the difference first.

Where a step cannot be undone, the description says so.

4.7 We do not promise that a Recipe will find every problem or dependency in your configuration. A report reflects the configuration we could read at the time of the run.

5. Price and payment

5.1 Prices are shown in pounds sterling and exclude VAT. VAT is added at the applicable rate. You pay by card through Stripe. We do not see or store your card number.

5.2 We send a VAT invoice to the email address used at purchase on request.

5.3 Cancellation and refunds are set out in the refund policy, which is part of these terms.

6. Data

6.1 We process your personal data as set out in our privacy policy at https://deltastring.com/privacy/. Where a Recipe processes personal data in your Zendesk on your instructions, we do so as your processor under our data processing agreement at https://deltastring.com/legal/dpa/.

6.2 You keep ownership of your configuration and data. We claim no rights in it. You give us permission to read and, once you approve, change it for the purpose of running the Recipe.

6.3 Reports and outputs we produce for you are yours to use for your own business purposes. We keep ownership of our software, methods and templates.

7. Using Deltastring properly

You will not: use a Recipe on a Zendesk instance you have no authority to change; try to bypass the approval step; or use the service to break the law or Zendesk’s terms. We may stop a run where we reasonably believe you are doing so.

8. Our responsibility, and its limits

8.1 We will perform each Recipe with reasonable care and skill.

8.2 We do not guarantee that a Recipe will give any particular business result, or that it will suit your setup. The preview and the undo record exist so that you can decide and, where possible, reverse.

8.3 Nothing in these terms limits or excludes our liability for: death or personal injury caused by our negligence; fraud or fraudulent misrepresentation; or anything else that English law does not allow us to limit or exclude.

8.4 Subject to 8.3:

  • we are not liable for loss of profit, revenue, business, goodwill or anticipated savings, or for indirect or consequential loss;
  • we are not liable for loss or damage caused by a change you approved after a preview that showed that change, except to the extent we did not apply it as previewed;
  • our total liability for all claims arising in connection with the Recipes you buy from us, whether in contract, tort (including negligence) or otherwise, is limited in each period of 12 months to the greater of (a) the total price you paid us for Recipes in the 12 months before the event that first gave rise to the claim, and (b) £10,000.

8.5 We are not responsible for the availability, behaviour or changes of Zendesk, or for Zendesk’s API rejecting or altering a change. Where Zendesk rejects a change, the preview or the run result will say so.

9. Ending and suspension

We may stop a run, or refuse a purchase, if payment fails, if we reasonably suspect misuse, or if the Recipe cannot be completed for a reason outside our control, such as the connected instance revoking our access. If we cannot complete a paid Recipe, we will refund it (see the refund policy).

10. Changes to these terms

We may update these terms. The version in force on the day you buy applies to that purchase. We will not change the terms of a purchase after you have made it, except where the law requires.

11. Complaints and contact

Deltastring Ltd, The Office, 37 Leatherhead Gardens, Hedge End, Southampton, England, SO30 2TY Email: hello@deltastring.com Security reports: security@deltastring.com

If something has gone wrong, email us first with the Zendesk subdomain and the date. We aim to reply within one working day, UK hours, Monday to Friday.

12. General

12.1 These terms and the refund policy are the whole agreement for the purchase.

12.2 If a part of these terms is unenforceable, the rest still applies.

12.3 Only you and Deltastring have rights under this contract. A third party has no right to enforce it.

12.4 You may not transfer the purchase to someone else without our agreement. We may transfer our side to a successor to our business.

13. Governing law

These terms, and any dispute or claim arising out of them or their subject matter, are governed by the law of England and Wales. The courts of England and Wales have exclusive jurisdiction.