Privacy Policy

Version 1.0, 20/10/2026

This policy explains how Deltastring Ltd handles personal data when you visit deltastring.com, use the Deltastring app at beacon.deltastring.com, or connect Deltastring to an AI assistant through our MCP server. It replaces the separate policies previously published on deltastring.com/privacy/, deltastring.com/legal.html and beacon.deltastring.com/privacy.

Who we are

Deltastring Ltd, a company registered in England and Wales, company number 15214660, VAT number 471506205, registered office The Office, 37 Leatherhead Gardens, Hedge End, Southampton, England, SO30 2TY. “We” and “us” mean Deltastring Ltd.

Privacy contact: hello@deltastring.com. We have not appointed a Data Protection Officer; please use this contact.

Two roles

  • Controller. For your Deltastring account (who you are, how you sign in, billing, how you use the app and the website), we decide how the data is used and we are the controller.
  • Processor. For the data we read from your Zendesk instance on your instructions, your organisation is the controller and we act as its processor. Our data processing agreement governs that processing. This policy describes it so you know what happens, but the agreement is what binds us.

What we collect and why

Your account

Data Why Legal basis
Name, email address, job title (optional), password hash or your Google sign-in, multi-factor settings To create and secure your account Contract
Team membership and roles To share connections with colleagues Contract
Subscription, seat count, billing period, Stripe customer and subscription identifiers To bill you. We do not see or store card numbers; Stripe does Contract, legal obligation (tax records)
Preferences (time zone, language, theme, notification settings) To run the app the way you set it Contract
Emails we send you (verification, password reset, sync failures, account notices) To operate the service Contract

Your Zendesk configuration

In short. Deltastring changes your Zendesk configuration. When you ask it to, it also updates users and organisations: you see each change before it’s made, only editors can make it, every change is logged with what it replaced, and you can undo it. We don’t read or store ticket content, and we don’t export your people data. The one exception for ticket content is Escalations, described below: it is opt-in, reads a ticket in memory only, and stores no ticket content or ticket id.

When you connect a Zendesk instance, Deltastring stores encrypted credentials for it and syncs its configuration on a schedule you choose (daily by default) or when you ask. A sync reads configuration objects such as triggers, automations, macros, views, ticket fields and forms, groups, brands, SLA policies, schedules, webhooks, dynamic content, custom object schemas, Help Centre structure and article content, and voice and messaging settings.

Configuration can contain personal data, for example a staff member’s name inside a trigger condition or an email address in a macro. We store it as part of the snapshot because it is part of the configuration.

Staff records. To show who a rule assigns to and to report on unused seats, a sync stores your Zendesk agents and admins: name, email address, role, whether the account is active or suspended, last sign-in time and group memberships.

What a sync never stores. A sync does not fetch or store ticket content, end-user (customer) records or organisation records. This is enforced in the code twice: the request asks Zendesk only for agents and admins, and every record returned is checked again so that an end user is dropped before anything is saved. The one exception to reading tickets is Escalations, described below.

On-demand user tools. Some tools act on Zendesk users when you ask them to, for example bulk updating user fields, tags, or group and organisation memberships, or resolving which users a Help Centre segment covers. These read the user and organisation records the request needs, in memory, return the result to you, and do not store those records. If you apply a change, we log it with the values it replaced so it can be reversed. We keep those prior values for 90 days.

Change history. When you change configuration through Deltastring we keep a record of who did it, when, what changed and the state before, so it can be reviewed and reversed.

Legal basis: we process this data to perform our contract with your organisation and on its instructions as its processor.

Escalations (ticket reads, switched on by you)

Escalations is off unless your organisation switches it on for a Zendesk connection. When it is on and one of your agents runs an Escalation, we read the ticket, its comments and the requester’s other tickets from your Zendesk. We do not look up user or organisation records, and we do not search.

We process that ticket content in memory to produce the brief. We do not store it. It does not go into our database, our logs or our audit records.

The ticket context is passed to the AI model and connectors that your organisation has chosen and controls. We do not provide or resell the model. What the model provider does with the data is governed by your agreement with it.

We post the brief as an internal note in your Zendesk.

We keep a record of the outcome at configuration level only: a configuration problem, the configuration objects it concerns and a count. It is linked to tickets only by a shared tag that exists in your Zendesk, never by ticket number. Our audit record shows that a ticket read happened. It does not say which ticket.

For this processing your organisation is the controller and we are its processor, under our data processing agreement.

The MCP server and your AI assistant

Deltastring’s MCP server lets an AI assistant you choose (such as Claude or ChatGPT) work with your Zendesk configuration through Deltastring.

  • Your AI provider is your choice. The assistant, its model and its account belong to you or your organisation, under your agreement with that provider. That provider is not our sub-processor and we do not control what it does with data.
  • What we receive. Your assistant sends us tool calls: the name of the tool and its arguments (for example a search term or an object id). We never receive your conversation. MCP does not send it, and we do not ask for it.
  • What we send back. Tool results: the configuration objects, search results, comparisons, health findings or change plans the tool produced from your Deltastring data, and for the on-demand user tools above, the user data the request needed. For an Escalation, tool results can include ticket content read for that run. These results go into your assistant’s conversation and are then held by your AI provider under your agreement with them.
  • What we keep. For each tool call we record the tool name, the connection it targeted, the outcome, which access token was used and the client name your assistant reports. We keep these records for 90 days. We do not log tool arguments or results. Where a tool creates a change plan, the plan is stored like any other change made in the app.
  • Access. An assistant can only reach the connections you authorised for it. Tokens can be read-only or allowed to propose changes, and you can revoke them at any time in Settings.

The website and app in your browser

  • Server logs record IP address, browser type, the page requested and the time. We use them to run and secure the service and keep them for a limited period.
  • Cookies: we set only the cookies needed to sign you in and protect forms (access_token, csrf_token).
  • Support chat: the support chat widget on deltastring.com is provided by Zendesk, which may set cookies or use local storage in your browser to run the chat and remember a conversation.
  • Product analytics: we record in-app events (for example “sync completed”) against your account to improve the product. We keep them for 90 days. Legal basis: legitimate interest in understanding how the product is used.
  • When you sign up, our team receives a notification containing your email address, posted to Slack.
  • When you email us, your message is handled in our own Zendesk.

Enquiries and consulting

If you contact us or work with us as a consulting client, we hold your contact details and what you send us to reply and to deliver the work. Legal basis: legitimate interest, or contract where we work together. We keep enquiries for 2 years and engagement records for the length of the engagement plus 6 years.

AI features inside Deltastring

Deltastring contains optional AI features that would send configuration to an AI provider to generate summaries. They are switched off for every account. If they are switched on in future we will update this policy and the sub-processor list first. We do not use your configuration or your data to train AI models, and we do not sell it.

Who we share data with

We use a small number of service providers (sub-processors) to run Deltastring. The current list, with what each one does, is at https://deltastring.com/legal/sub-processors/. We give notice before adding one, as the data processing agreement describes. We do not sell personal data and we do not share it with advertisers. We may disclose data where the law requires it.

Where data is held

The Deltastring app and its database are hosted in the Netherlands, in the EU. Email, backups and configuration version history are held with our UK hosting provider. Some providers may be based in, or access data from, countries outside the UK and EEA; where personal data leaves the UK or EEA we rely on adequacy regulations or on the UK International Data Transfer Agreement or Addendum and the EU Standard Contractual Clauses.

How long we keep data

Data Kept for
Configuration snapshots The most recent 50 per connection
Change and audit history 7 years
Prior values kept so a user-record change can be reversed 90 days
MCP tool-call records and product analytics 90 days
Webhook delivery logs 30 days
Unapplied (pending) changes 7 days
Expired access tokens 7 days after expiry
Stripe event records 90 days; invoices and payment records 7 years for tax
Database backups The 14 most recent copies, about two weeks
Server logs A limited period
Booking data (names and email addresses of people who book a call) 12 months

Deleting your account. You can delete your account in Settings. Deletion signs you out everywhere, revokes your access tokens and API keys, clears linked Google or Microsoft tokens, and permanently deletes your Zendesk connections together with their snapshots and change history. Your remaining personal data is kept for 60 days in case you change your mind, then scrubbed automatically. You can ask for it to be scrubbed straight away from the same page. Backups age out as described above.

Version history on our UK host. Deleting a connection removes the working copy of its version-history repository from the application server. Nothing in the deletion removes the copy on our UK hosting provider. That copy is not removed automatically; it is deleted on request. Email hello@deltastring.com to have it removed.

Exporting your data. Email hello@deltastring.com and we will send you your configuration data.

Security

Zendesk credentials are encrypted at rest with a fresh key per record, wrapped by a master key (Fernet: AES-128 with HMAC-SHA256). Passwords are hashed with bcrypt. All traffic uses TLS. Access to a connection follows Deltastring’s permission model, and access to production is limited to Deltastring personnel who need it. Our security page explains how to report a vulnerability.

Your rights

You can ask for access to your data, correction, erasure, restriction, portability, and you can object to processing based on legitimate interest. Write to hello@deltastring.com. We reply within one month. Where we hold data as a processor for your organisation, we will pass your request to them and help them answer it.

You can complain to the Information Commissioner’s Office (ico.org.uk). We would appreciate the chance to sort it out first.

Children

Deltastring is a business tool and is not for anyone under 18.

Changes

We will update this page when our practices change and give the date at the top. For material changes affecting customers we will email account owners before the change takes effect.