Security

The boring parts, written down

You are about to put your customers' conversations, contracts and recordings into somebody else's system. Here is what keeps them apart.

Separation

How one company never sees another

Isolation is inside the query

Every record carries the company it belongs to, and that condition goes into the database query itself, instead of being checked on the rows after they have arrived. The wrong rows are never fetched, so they cannot leak further.

Your credentials are encrypted

Mailbox passwords, channel keys and telephony keys are stored encrypted with AES-256. They are decrypted at the moment of use and never sent to a browser.

Files are not in a public folder

An attachment cannot be reached by knowing its path. Each one needs a signed link that lives five minutes and is bound to the address that asked for it.

Two-step sign-in

Time-based codes from any authenticator app, for every account.

The session ends with the browser

A closed browser means signed out. This is deliberate: the working day should start with a conscious sign-in.

One event happens once

A webhook delivered five times changes your data once. Repeat delivery is normal on the internet. Duplicate tickets and double-counted calls should not be.

Concretely

The numbers people ask about when choosing a vendor

Credential encryption
AES-256
Transport
TLS with HSTS
File links
5 minutesbound to the address that requests them
Second step
TOTPsix digits, 30-second window
Server session
7 days
Webhook authentication
HMAC-SHA256over the raw bytes, 5-minute window
Backups
encryptedbefore they leave the server
Restore
rehearseda real restore into a throwaway database, rows counted
An agent's profile with active sessions by device and browser
Company settings: mailbox, channels, SLA and API key

Honestly

What we do not claim

ZynTrail has no ISO 27001 or SOC 2 certificate. Writing that costs us one line on this page and saves you an awkward discovery in the middle of a vendor selection.

What exists is above: the mechanisms, and the fact that they are checked rather than assumed. Backups are restored on a schedule into a single-use database and the rows are counted, because a backup nobody has ever restored is a belief, not a backup.

If your buyer wants a document we cannot provide, say so early. That conversation is better in week one than in week ten.

The legal side

Who is the controller and what happens on deletion

You are the controller

The personal data in your tickets is yours. ZynTrail processes it on your instructions, under terms that come with the contract, not on request.

The processing agreement is included

The Article 28 agreement is part of the terms of service, accepted in one action, and provided as a separate document for signature if your process requires it.

Deletion is carried out

An erasure request is executed against the live system, and backups holding the old record expire on a published schedule instead of being edited row by row.

What the law keeps, stays

Invoices and accounting records are kept as long as tax and accounting law requires, and that takes precedence over an erasure request.

Questions about security

Before you write to us

Can ZynTrail run on our own server?

No. ZynTrail is a service we run: we update it, take the backups and rehearse the restore. The software itself is not handed over. That is also a large part of what you pay for: no server to maintain, no weekend for upgrades, and a backup somebody has actually restored.

Who sees our tickets?

Your team, and each person sees only what their role allows. Every company’s data is kept apart from every other’s, connections are encrypted, and every important action is logged, so you always know who did what.

What happens to our data if we leave?

You export it: tickets, customers and reports to CSV and Excel. The company record is deleted, which removes everything hanging off it. Backups already taken keep their copy until they expire on the published schedule.

See it against your own case

Tell us how many people answer customers and which channels the enquiries arrive on. We will show you the same screens your team will work in, with your case rather than a demo script.

Every plan starts with 30 days of full access to the product, every feature included.