Security and trust
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. The Deltastring suite does not read tickets, and we don't export your people data.
How we handle your instance
Data
Deltastring reads and writes configuration objects. When you ask it to, it also updates users and organisations, with a preview, an audit log and undo. We don't read or store ticket content, and we don't export your people data.
Access
Connect over OAuth where Zendesk supports it. Credentials are encrypted at rest.
Control
Deltastring never changes your instance on its own. Every write is one you approved.
Accountability
Every change is recorded: who, what, when, and the state before it. Roll back to any point.
Approval
Destructive and AI-drafted changes go through an approval gate before they reach production.
Isolation
Your configuration and any context you provide are used for your instance, not shared or trained on.
Escalations
Escalations is switched on per Zendesk connection. When it is asked about a ticket, it reads that ticket, its comments and the requester's other tickets in memory, and passes them to your own AI model. You bring the model; we do not host or resell it. Escalations posts an internal note and tags back to the ticket in Zendesk. It stores no ticket content and no ticket ids, and never reads, lists or searches user or organisation records. Outcomes are kept only as configuration-level records: a type plus references to configuration objects.
Certifications
We hold ourselves to enterprise security practices. Where a formal certification is in progress rather than complete, we say so plainly rather than imply otherwise. Ask us and we'll tell you exactly where things stand.
Talk to us. We'll walk you through exactly how Deltastring handles your instance.