This is the first published version of this policy. Changes to it are made as described in section 16.
This is a translation provided for convenience. The Bulgarian text is authentic and prevails in the event of any discrepancy.
Who operates ZynTrail
#| Legal name | Dedilayer Ltd. |
|---|---|
| Registered seat and address of management | Sofia, Bulgaria |
| Email for data protection matters | privacy@zyntrail.com |
| Service website | https://app.zyntrail.com |
These details are also published pursuant to Art. 4 of the Bulgarian Electronic Commerce Act (Закон за електронната търговия).
No Data Protection Officer has been designated. The reasoning is set out in section 12. For any data protection matter, use the address above.
ZynTrail's two roles
#ZynTrail is a platform that companies use to serve their own customers. For some data we decide; for other data the customer company decides. In law these are two distinct roles:
| Category of data | ZynTrail's role | Who is the controller |
|---|---|---|
| Customer company account and subscription data: contact person, email, billing, payments | Controller | ZynTrail |
| Identification, sign-in, sessions and security logs for the customer's users | Controller (limited scope, see 2.1) | ZynTrail |
| Everything the customer company enters into or receives through the platform: its own customers and contacts, tickets, messages, files, calls | Processor | The customer company |
| Working-time data of the customer's staff: shifts, leave, swaps, attendance, activity | Processor | The customer company |
Sections 3 – 13 concern the first two rows and constitute the notice required by Arts. 13 and 14 GDPR.
Section 14 concerns the last two rows. It is informational only. For that data ZynTrail is not the controller and this policy does not constitute a notice under Art. 13 or Art. 14 GDPR. That notice is owed by the relevant customer company.
2.1 Security log
#Who signed in and when, from which address, which session was rejected, which administrator changed what: we create these records on our own decision, in order to protect the environment. The customer does not instruct us to keep them and cannot instruct us to stop without leaving us unable to protect the other tenants. So for these we are the controller, on the basis of Art. 6(1)(f) GDPR read with Recital 49, which expressly recognises network and information security as a legitimate interest.
Shift, leave and attendance data is not ours. It is the customer company's HR data, even though it concerns people who hold accounts with us. For that data we are a processor.
2.2 How you came to see this policy if you work for one of our customers
#Your account was created by your employer, not by you. So we obtained your data indirectly for our own layer of processing, and the applicable notice is Art. 14, not Art. 13. This policy is always available on the sign-in screen and in the platform. Your employer is bound by its contract with us (section 9 of the Terms of Service) to inform you before it creates your account.
What we process as controller
#Contact person and administrators of the customer company: first and last name, work email, work telephone (where provided), role in the system, interface language.
All users with an account: account identifier, role, department, sign-in records and active sessions, date and time of last sign-in, the browser and device of each session, the IP address of each session and of recent sign-ins, IP address in web server logs, session cookie identifiers, two-factor sign-in data (encrypted secret and backup codes), the count of failed sign-in attempts and any temporary lock, records of actions in the security log. We keep the IP addresses of sessions and sign-ins for security and delete them 12 months later.
Users who have switched on notifications in their browser or on their phone: the push subscription address that the browser creates.
Sign-in with Microsoft, where the company has connected Microsoft 365: the directory and user identifiers in Microsoft Entra ID, the work user name and email from Microsoft's token, the groups the user belongs to, and whether the account is enabled in Microsoft. When the company switches on directory sync, users and groups are synced once a day, and, when it also connects SCIM 2.0, in real time. The Microsoft password is entered at Microsoft only.
For billing: the customer company's name, EIK (Bulgarian company ID), VAT number, address and contact person; Stripe customer and subscription identifiers; payment history, amounts, dates and status. Payment card data never reaches our servers and we never see it. Payment takes place on a page hosted by Stripe.
For usage metering: the number of language units (tokens) processed, per tenant and per period. We count volume, not content: request text is not stored for metering purposes.
Enquiries through the form on www.zyntrail.com: name, email, company, the number of people who answer customers, the channels the visitor is interested in, the text of the message and, if filled in, where they heard about us. The page adds its language, the plan chosen (when the visitor came from a plan button), the address of the previous page and the campaign parameters (utm_source, utm_medium, utm_campaign) when present, and how long the form was open. We use the last one to recognise bots.
Visitors to www.zyntrail.com, only if they have accepted statistics cookies: a pseudonymous browser identifier (_ga cookies), the pages visited, where the visit came from (search engine, advertisement, link), approximate location down to city level, device type and browser. Google Analytics collects them. We do not link this data to a name, an email address or a platform account.
Registration requests through app.zyntrail.com/register: country, the company's name, registration number and VAT number; the person's name, email and telephone (where provided); language, time zone and chosen plan; IP address; the version and checksum of the Terms of Service accepted; the result of the register checks.
The company's name and registered address are filled in from the registration or VAT number entered: for Bulgarian companies from the Bulgarian Commercial Register and Register of Non-Profit Legal Entities (Registry Agency), for companies in other EU countries from the European Commission's VIES system. When the register returns nothing, and for companies outside the EU, the person types them in. The name in Latin script is only shown for checking and is not stored. Managers' names and the telephone numbers and email addresses filed in the register are not taken. For a sole trader, the business name contains the name of the individual.
This list is exhaustive for our role as controller. Data we process on a customer's instructions is described in section 14.
Purposes and legal bases
#Each purpose has one basis.
| Purpose | Basis | Note |
|---|---|---|
| Creating and maintaining the account; providing the service | Art. 6(1)(b), contract | The contracting party is the company. For the individual who represents it, the basis is (f), since that person is not personally a party |
| Invoicing and debt collection | Art. 6(1)(b) | |
| Accounting and tax reporting | Art. 6(1)(c), legal obligation | Accountancy Act and Tax and Social Insurance Procedure Code |
| Sign-in, session management, detecting and preventing abuse | Art. 6(1)(f) | The interest is preventing unauthorised access and preserving the integrity of an environment shared by several independent tenants |
| Service communications: outages, changes, expiring subscription | Art. 6(1)(b) | Part of the service; not switched off by unsubscribing |
| Commercial communications to existing customers | Art. 6(1)(f) | Every message carries an opt-out. See also 4.1 |
| Replying to an enquiry sent through the website form: a demo, a trial, a question | Art. 6(1)(b), steps taken at the enquirer's request before entering into a contract | Where the enquirer writes on behalf of a company, the basis for their own data is (f) |
| Checking a registration request and creating the account from it | Art. 6(1)(b), steps taken at the person's request before entering into a contract | The register checks and protecting the form from abuse rest on (f) |
| Establishing, exercising and defending legal claims | Art. 6(1)(f) | |
| Website visit statistics and ad measurement (Google Analytics) | Art. 6(1)(a), consent | Only after “Accept” in the banner. Consent can be withdrawn at any time from “Cookies” at the bottom of every page, as easily as it was given (section 13) |
We use consent only for website statistics (the last row of the table). It is the basis for nothing else: declining the cookies affects neither your enquiry nor your use of the platform.
Balancing test. Where the basis is legitimate interest, an assessment weighing that interest against your rights has been carried out and documented. We provide it on request at the address in section 1.
4.1 Right to object
#Where we process on the basis of legitimate interest, you have the right under Art. 21 GDPR to object at any time. Where the objection concerns direct marketing we stop immediately and without assessment. In other cases we stop unless we demonstrate compelling legitimate grounds which override your interests.
Who we share data with
#Recipients by category, with country and transfer basis, are set out in section 6. The named list of sub-processors (name, country, purpose and transfer mechanism) is Annex III to the Data Processing Agreement, at the end of the Terms of Service. We also send it on request at privacy@zyntrail.com.
Beyond sub-processors, data may be disclosed to: accountants and auditors (legal obligation); legal advisers and enforcement agents when defending claims; and competent authorities where required by law.
We do not sell personal data and we do not provide it to third parties for their marketing purposes.
Transfers outside the EU/EEA
#| Recipient | Country | Transfer basis |
|---|---|---|
| Contabo GmbH: hosting of the platform and of the phone system (rented servers) | Germany; the data centre is in the EU | No transfer |
| Google Cloud Text-to-Speech: turns into speech the text of the phone system's voice menus and greetings that the customer company enters (no caller data) | Ireland, with possible onward transfer to the USA | Adequacy decision (EU–US Data Privacy Framework) |
| Stripe (payments) | Ireland, with onward transfer to the USA | Adequacy decision (EU–US Data Privacy Framework); should it lapse, Standard Contractual Clauses under Implementing Decision (EU) 2021/914 |
| Google (Gmail, Drive) | Ireland, with onward transfer to the USA | As above |
| Google Analytics (website statistics, consent only) | Ireland, with onward transfer to the USA | As above |
| Meta (Messenger, Instagram, WhatsApp) | Ireland | The customer connects its own account; Meta is an independent controller for its platform |
| Microsoft (sign-in with Microsoft 365 and the customer company's directory, Microsoft Entra ID) | Ireland, with possible onward transfer to the USA | Adequacy decision (EU–US Data Privacy Framework). The customer company connects its own directory |
| Brevo (Sendinblue SAS): sending email from zyntrail.com addresses, including registration emails and system notices | France | No transfer |
| Scaleway SAS: encrypted copies of the platform's backups, kept for up to 30 days; they are encrypted before they leave our servers, and Scaleway cannot read them | France | No transfer |
| Sentry (Functional Software, Inc.): reports of errors in the platform, including errors in the browser (the page address and the browser type, without the visitor's IP address), so that we can fix them; passwords and access keys are removed before a report is sent | Germany (Sentry's EU data region); the provider is based in the USA | Standard Contractual Clauses under Sentry's data processing agreement |
| European Commission, VIES system: checking a VAT number at registration and for the reverse charge; only the VAT number is sent | EU | No transfer |
| Telegram | United Arab Emirates | No adequacy decision. See 6.1 |
| OpenAI | Ireland, with onward transfer to the USA | Standard Contractual Clauses under the data processing agreement |
| Google Gemini | Ireland | As above. Paid tier only, under which submitted data is not used to train models |
| Phone system (ZynTrail Voice): software the Provider runs itself, on a Contabo GmbH server in the EU | EU | No transfer |
| Browser push services (Google Firebase Cloud Messaging, Apple Push Notification service, Mozilla): they receive only the technical subscription address and the notification text, encrypted under the Web Push standard, and only for users who have switched notifications on | USA | Adequacy decision (EU–US Data Privacy Framework) or Standard Contractual Clauses, depending on the provider |
Stripe is not our sub-processor in the strict sense. For the payment transaction itself Stripe acts as an independent controller, because it has its own obligations under payment services and anti-money-laundering law which we cannot instruct away.
The same applies to Google and Meta as regards channels: there the customer company connects its own account and has its own relationship with those providers. We act under a grant it has given us.
6.1 Telegram
#Telegram is operated by an entity established in the United Arab Emirates. There is no adequacy decision under Art. 45 GDPR for that country. The channel is disabled by default and is enabled only by an express decision of the customer company, which as controller assesses and documents the permissibility of the transfer for its own data.
How long we keep data
#| Data | Period |
|---|---|
| Account and user profile data | For the term of the contract and 30 days after the subscription ends, in read-only mode. Then deleted together with the company within 14 days, after email warnings 14 days and 3 days before deletion (section 6 of the Terms of Service) |
| Accounting documents and invoices | Kept outside the platform, in Stripe and in our accounting, for the period required by the Accountancy Act and the Tax and Social Insurance Procedure Code. This overrides an erasure request. The payment history shown in the platform is deleted together with the account |
| Security log, sign-in records, the IP address and browser of sessions, recent sign-in addresses | 12 months |
| Website form enquiries that did not lead to a contract | 12 months from the last correspondence on the enquiry |
| Registration request with an unconfirmed email | 7 days |
| Registration request that did not lead to a contract | 12 months |
| Registration request that led to a contract | For the term of the contract and 3 years after termination (the period under Art. 111 of the Obligations and Contracts Act for claims arising from periodic payments, which subscription fees are), because it holds the record of the Terms accepted (section 3.2 of the Terms of Service) |
| Website visit statistics | Up to 14 months in Google Analytics; the _ga cookies stay in your browser for up to 2 years, or until you withdraw consent |
| Data entered by the customer into the platform | On the customer's instructions while the contract runs (section 14). After the subscription ends: 30 days in read-only mode, then deletion within 14 days |
7.1 Backups
#Erasure is executed against the live system. Backups are not edited record by record; that is technically impossible for an archive which must remain internally consistent and restorable.
Copies are overwritten on a rolling cycle: up to 7 days for the on-server copy and up to 30 days for the offsite copy. An erased record may therefore persist in a backup for at most 30 days after its erasure from the live system. During that period the copies are not opened or read, except in an actual disaster recovery event.
Your rights
#You have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), portability (Art. 20) and objection (Art. 21).
Response time: one month from receipt of the request. Where the request is complex or numerous, that period may be extended by a further two months; we will inform you of the extension and the reasons within the first month. This is the period under Art. 12(3) GDPR.
8.1 If you are a customer or counterparty of a company that uses ZynTrail
#Then we process your data on that company's instructions, and it, not us, is the controller. Address your request to it.
If you nevertheless address it to us, we will:
- not respond on the merits, because we have no right to dispose of someone else's data;
- forward the request to the relevant controller without undue delay and no later than 5 business days;
- tell you that we have forwarded it and to whom, unless doing so would breach the confidentiality we owe our customer.
We cannot always establish which company you dealt with without searching across all tenants' data. Such a search is itself a processing operation for which we have no basis. So if you write to us, name the company you dealt with. Without it we cannot advance your request.
8.2 Complaint to a supervisory authority
#You have the right to lodge a complaint under Art. 77 GDPR:
Commission for Personal Data Protection (Комисия за защита на личните данни) 2 Prof. Tsvetan Lazarov Blvd., Sofia 1592, Bulgaria tel.: +359 2 915 3 518 · email: kzld@cpdp.bg · www.cpdp.bg
You may also complain to the supervisory authority of your habitual residence if that is in another Member State. Independently of any administrative complaint, you also have the right to an effective judicial remedy under Art. 79 GDPR.
Whether you must provide your data
#To create an account we need the company's name and registration number (the EIK for Bulgarian companies, the VAT number for companies in another EU country), and the contact person's name and email. Without them no contract can be concluded and the service cannot be provided. The remaining fields (telephone, preferred language) are optional and leaving them blank has no consequences.
Automated decision-making
#ZynTrail does not take decisions based solely on automated processing which produce legal effects concerning you or similarly significantly affect you within the meaning of Art. 22 GDPR.
AI features classify an enquiry, draft a reply and summarise a conversation. The customer company chooses how they work: manual: only when an agent asks; with approval: the assistant drafts, and an agent reviews and sends; automatic: the assistant sends the reply itself, but only during the hours the company has set. Automatic mode is switched on by the customer company, which can switch it off at any time. The assistant writes from the company's own documents and knowledge base. Every reply the assistant sends automatically ends with a line saying it was sent by an AI assistant (section 11). Refusing service and setting a price remain decisions for the company's staff.
The working-time module calculates indicators for staff: late start (starting work more than 15 minutes after the shift begins) and adherence to schedule in percent. They serve only as information for the manager, who decides what to do.
If that changes, this section will be changed in advance.
AI features
#- The provider is determined by the subscription plan, is not chosen by the customer company, and is named in section 6.
- Processing is carried out on the customer company's instructions; it remains the controller of the content.
- Submitted data is not used to train any model, neither ours nor the provider's. This is contracted with every provider we offer. A provider for which we cannot guarantee it is not offered.
- We meter usage in language units. Content is not stored for metering purposes.
- The customer company can disable AI features entirely from its settings.
- Every reply the assistant sends automatically, without an agent approving it, ends with a line saying it was sent automatically by an AI assistant. The line is in the language of the reply and is always added; there is no setting to switch it off. In this way the person learns that they are interacting with an automated system, under Art. 50 of Regulation (EU) 2024/1689.
- A draft from the assistant that an agent has reviewed and sent is the agent's reply.
Why no Data Protection Officer has been designated
#Designation is mandatory under Art. 37(1) GDPR where the core activities require regular and systematic monitoring of data subjects on a large scale, or large-scale processing of special categories.
The first limb, processing personal data on customers' behalf as a core activity, is satisfied. The second, "large scale", is not satisfied at the present number of tenants and volume of data, assessed against the criteria in Article 29 Working Party guidance (WP243), endorsed by the European Data Protection Board.
An officer has therefore not been designated, and a contact point for data protection matters is provided instead. An officer designated under Art. 37 must be notified to the Commission for Personal Data Protection and must be independent, and a person who runs the company and builds the system does not meet that requirement.
The assessment is documented, dated, and reviewed upon: a material increase in the number of tenants, the first tenant processing Art. 9 data, or a request from a supervisory authority.
Cookies
#We use two kinds of cookies. In the platform (app.zyntrail.com), strictly necessary ones only:
| Name | Purpose | Type | Duration |
|---|---|---|---|
zyntrail_token | Maintaining an authenticated session | First-party, HttpOnly | Until the browser is closed |
zyntrail_refresh | Renewing the session without re-entering a password | First-party, HttpOnly | Until the browser is closed |
XSRF-TOKEN | Protection against cross-site request forgery | First-party | Until the browser is closed |
_csrf | Protection against cross-site request forgery, together with XSRF-TOKEN | First-party, HttpOnly | Until the browser is closed |
zt_mssignin | Links the return from Microsoft to the sign-in that started it; only during sign-in with Microsoft | First-party, HttpOnly | 10 minutes |
zt_oauth | Links the return from an external provider to the connection an administrator started, such as a mailbox or a channel | First-party, HttpOnly | 10 minutes |
No consent is required for these cookies: they fall within the exemption in Art. 4a(4)(2) of the Bulgarian Electronic Commerce Act (Закон за електронната търговия), being necessary to provide a service explicitly requested by the user. Without them, signing in is impossible.
On the website www.zyntrail.com: statistics cookies, only with your consent. On the first visit the site shows a banner with two equal buttons, “Accept” and “Decline”. Until you press “Accept”, nothing is loaded from Google and no cookie is set.
| Name | Purpose | Type | Duration |
|---|---|---|---|
_ga | Tells separate visitors apart without knowing who they are | Google Analytics, third party | 2 years |
_ga_3BJBKMD03X | Keeps track of the current visit | Google Analytics, third party | 2 years |
_gcl_au | Links a visit from a Google ad to a later enquiry | Google Ads, third party | 90 days |
Your choice is kept in your browser (zt_consent in localStorage) so that we do not ask on every page. You can change it at any time from “Cookies” at the bottom of every page, or here. If you decline after accepting, the site deletes the _ga and _gcl cookies it has already set.
The site also keeps the following entries in your browser:
| Name | Purpose | Type | Duration |
|---|---|---|---|
zt_lang | Remembers the language you chose on the site | First-party, localStorage | Until you clear it in the browser |
zt_demo, zt_demo_started | Only on the demo: remember the state of the demo | First-party, localStorage | Until you clear them in the browser |
zt_ref | The address of the page you came from. Written only after you press “Accept” and passed to Google Analytics | First-party, sessionStorage | Until the tab is closed |
zt_lang and the demo entries are necessary for the page you asked for (Art. 4a(4)(2) of the Bulgarian Electronic Commerce Act). zt_ref is written only with your consent.
We use no remarketing, no social-network pixels and no advertising cookies other than those listed.
To show you the right language, the website determines your country from your IP address using a local database (IP Geolocation by DB-IP, https://db-ip.com, CC BY 4.0). The check runs on our own server: the IP address is not stored and is not sent to third parties.
The registration form on app.zyntrail.com is protected from automated requests by a small computational task the browser solves on its own. It uses no cookies and sends no data to third parties.
Data the customer company enters into the platform
#This section is informational. For the data described here, the controller is the customer company.
On its instructions we process: data about its customers and contacts (name, EIK, VAT number, responsible person, address, telephone, email, preferred language); the content of tickets and messages arriving by email, website chat, Messenger, Instagram, WhatsApp and web form; attachments; telephone call data including the audio of recordings; orders and shipments from connected online shops and marketplaces; ratings and comments from the satisfaction survey; drafts, summaries and replies from the AI assistant; internal correspondence between the customer's staff; and shift, leave (including sick leave) and attendance data.
Our relationship with the customer company is governed by a Data Processing Agreement (Annex 1 to the Terms of Service), concluded under Art. 28 GDPR.
14.1 Call recording
#Where the customer company uses the telephony functionality, it decides whether calls are recorded. Its administrator switches recording on and off in the telephony settings.
The controller of the recording is the customer company, not ZynTrail. It decides whether to record, for what purpose, for how long, and how it informs people. We provide the means.
What the law requires of it, and what our platform enables it to do:
- Notification before the recording begins, not after. The announcement must precede the first recorded second and state: that the call is being recorded, who the controller is, for what purpose, for how long, and where the full information can be found.
- Both parties are data subjects: the external participant and the customer's employee. Informing only one is not sufficient.
- For the employee, consent is not a valid basis, because of the imbalance inherent in an employment relationship. The customer should rely on legitimate interest with a documented assessment.
- The recording is stored on ZynTrail's phone system, on a server in the EU. The Provider holds the audio itself, as a processor acting on the customer company's instructions.
- Recordings are kept for 90 days and then deleted automatically. The company's administrator can choose another period in the telephony settings: 30, 90, 180 or 365 days. We set a longer period on the company's written request.
- At the company's request we record a spoken announcement about recording in the phone system's greeting.
ZynTrail also holds the call metadata (direction, status, duration, operator, contact).
- The six-month traffic-data retention duty under Art. 251b of the Electronic Communications Act does not apply either to us or to our customers. It concerns undertakings providing public electronic communications services.
If you called a company that uses ZynTrail and have questions about the recording, address them to that company. See section 8.1.
14.2 Messenger, Instagram and WhatsApp
#A customer company can connect its own Facebook Page, Instagram professional account and WhatsApp Business number. It does so by signing in with Facebook or Instagram, or through Meta's WhatsApp sign-up window, and it chooses which Pages, accounts and numbers to connect.
From then on we receive through Meta's platform, and process on the customer company's instructions:
- the messages people send to the connected Page, account or number: text, attachments and the time they were sent;
- the sender's name, where Meta provides it, and the identifier Meta gives the sender for that Page or account; on WhatsApp, the sender's phone number;
- the name and identifier of each connected Page, account and number, and the access tokens Meta issues for them;
- for the person who made the connection, the identifier Meta gives them for our app.
This data serves three purposes only: showing the conversations to the customer company's staff as tickets, delivering their replies to the same conversation, and managing the company's WhatsApp message templates. It is put to no other use: no advertising, no sale, no profiling, and no training of AI models (section 11). Replies are sent only within the time Meta allows; after 24 hours on WhatsApp only a template approved by Meta is sent.
Access tokens are stored encrypted. When the customer company disconnects a channel, its tokens are deleted and messages from it are no longer accepted. Messages received before that stay in the company's tickets until the company deletes them.
How to ask for deletion:
- If you wrote to a company that uses ZynTrail, that company is the controller. Ask it, or write to privacy@zyntrail.com (section 8.1).
- If you connected a Page or account and remove ZynTrail in your Facebook or Instagram settings, under Apps and websites, we stop the Messenger and Instagram connections at once and delete their access tokens.
- If you also send a deletion request from there, we delete the connections you made and their tokens, and you receive a confirmation code with a page where you can check the status. Conversations already received remain part of the company's records; to have them deleted, ask the company or write to us.
- A WhatsApp number connected through Meta's sign-up window is disconnected by the customer company in ZynTrail (Settings → Messaging channels) or by writing to privacy@zyntrail.com. The connection then stops and its access token is deleted.
On its own platform Meta processes data as an independent controller under its own privacy policy (section 6). The full procedure is on the page Deleting your data.
14.3 Online shops: orders, products and parcels
#In the Sales section a customer company can connect its online shops (WooCommerce, Shopify, PrestaShop, CloudCart, OpenCart, Magento, Shopware, BigCommerce, Ecwid, Shoptet, Shoper, IdoSell, Gomag, Lightspeed, Wix, Squarespace) and its seller accounts on marketplaces (eMAG, Kaufland, bol.com, Trendyol, OTTO and Mirakl marketplaces such as Decathlon, Carrefour and MediaMarkt). It does so with a key or user it creates in the shop or marketplace, or by approving ZynTrail in Shopify, and it can disconnect any of them at any time.
From then on, on the customer company's instructions, we read:
- the orders: the order number, date, status and amounts; the products; the buyer's name, email and telephone; the delivery and billing address; the payment and delivery method; the buyer's note; and tracking numbers;
- the products: name, SKU, price, stock and warehouse. These contain no personal data;
- buyer messages from Kaufland and Mirakl marketplaces and product questions from Trendyol: the buyer's name or user name, the text, any attached files and the order it is about. They become tickets in the customer company, and the replies are sent back to the marketplace. Replies on Trendyol are public.
- A copy of the orders is kept so that they can be shown next to tickets, listed and searched. A copy is kept for up to 2 years from the date of the order and is deleted when the shop or marketplace is disconnected, together with its products and parcel data. Marketplace messages are kept as tickets, under the rules for tickets.
- Some marketplaces give a code instead of the buyer's email (for example eMAG). Orders from marketplaces and from platforms other than WooCommerce, PrestaShop, CloudCart, OpenCart and Shopify are read only.
- When the customer company changes an order from ZynTrail (its status, a tracking number, a note, the delivery address, a cancellation or a refund), the change is made in the shop itself. Stock is only read.
Parcels. To show where a parcel is, the platform sends the tracking number (and no other buyer data) to the courier whose account the customer company added (Speedy, Econt, BOX NOW, Sameday, DPD Romania, GLS, DHL or Packeta), to InPost's public tracking service when the customer company switches it on, or to 17TRACK if the company uses its own 17TRACK key. 17TRACK is outside the EU (China, Hong Kong). Only the tracking number is sent to it, without other buyer data. The customer company switches 17TRACK on itself, with its own key, and the transfer happens on its instruction; the customer company is responsible for the basis of that transfer. These providers work under the customer company's own contract or terms with them. The parcel's status is kept with the order and deleted with it. Without such an account the number is only a link to the courier's page.
A buyer who wants their data deleted should contact the shop. The customer company can export or delete everything about one buyer, including their orders and shipments, with the platform's data subject request functions. For shops on Shopify, Shopify passes the shop's deletion requests to us and we delete the copies automatically.
14.4 The customer company's connected services
#In the platform's settings a customer company can connect its own accounts in other services. Each is connected with a key the customer company creates in that service and can be removed at any time. The key is stored encrypted. The services work under the customer company's own contract with them, and we use them on its instructions.
- Payments (Stripe, PayPal, Mollie). When a ticket is opened we look up the customer's payments by their email and show the amount, date, status, refunds and disputes. The result is held for up to 10 minutes in the server's memory and is not written down.
- Invoices (inv.bg). When a ticket is opened we look up the customer's invoices by email, or by name when the email finds none. An invoice PDF passes through us only when an agent opens or sends it.
- CRM (HubSpot, Pipedrive, Salesforce). When a ticket is opened we read the customer's record by email: name, company, owner, stage and deals. When an agent asks, we write a note in the CRM with the text the agent chose.
- Developer issues (Jira, GitHub, GitLab). When an agent creates an issue from a ticket, the title and text the agent approved are sent to it. After that we read only the issue's state.
- Reviews (Trustpilot). New and edited reviews of the customer company become tickets: the author's name, the rating and the text. The agent's reply is published on Trustpilot and is public.
14.5 Connected mailboxes (Gmail, Microsoft 365, IMAP)
#A customer company can connect its mailboxes to the platform: Gmail by signing in with Google, Microsoft 365 (Outlook) by signing in with Microsoft, or another mailbox over IMAP and SMTP with a user name and password.
Access covers the whole mailbox the customer company connects. The platform reads new messages in it, turns them into tickets and sends the staff's replies from it. For Gmail we use Google's full mail access scope (https://mail.google.com/). For Outlook we use Microsoft's IMAP and SMTP permissions (IMAP.AccessAsUser.All and SMTP.Send).
Access tokens and passwords are stored encrypted. Access stops when the customer company disconnects the mailbox in the platform or withdraws access in its Google or Microsoft account. The messages serve only the customer company's work on tickets: sale, advertising and the training of AI models are excluded (section 11).
ZynTrail's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
14.6 Webhooks, API and integrations (Slack, Microsoft Teams, Zapier, Make, n8n)
#A customer company can set up webhooks, a key for the platform's API, and connections to Slack, Microsoft Teams, Zapier, Make and n8n. Once it does, on ticket events the platform sends ticket data to the addresses the customer company has chosen. This includes the end customer's name, email and telephone, and the name and email of the staff member the ticket is assigned to. With the API key, the customer company's systems create and read tickets.
The recipients work under the customer company's own contract with them. The log of sent data is kept for 30 days. The customer company is responsible for keeping its API key secret and for the addresses it sends data to (section 9 of the Terms of Service).
14.7 Satisfaction survey
#When a ticket that came in by email is closed, the end customer receives a short survey: a rating from 1 to 5 and a comment. The rating and comment are stored with the ticket. The customer company can switch the survey off in its settings.
14.8 Chat on the customer company's website
#A customer company can put the ZynTrail chat on its website. So that the conversation continues when the visitor comes back, the chat keeps an identifier in the visitor's browser (localStorage) until the visitor clears the site's data. The chat also sends the address of the page the visitor is on, and it is shown in the ticket.
The customer company puts the chat on its website and describes this in its own cookie policy.
Security
#We apply the following categories of measures.
- Access to the platform is over HTTPS only, with automatically renewed certificates.
- The customer's credentials for external channels are stored encrypted.
- Attachments are delivered only via a signed temporary URL; the file directory is not publicly served.
- Separation between tenants is verified regularly; within a tenant, further limits apply by role and by department.
- Administrative actions on accounts are written to an audit log.
- Backups every 6 hours, with a performed and documented restore drill.
- Server access by cryptographic key only, with a firewall enabled and automatic security updates.
- The offsite backup is encrypted before it leaves the server (AES-256), with a passphrase the storage provider does not hold. Only ciphertext is stored there. Every file is read back immediately after encryption and before upload.
In the event of a personal data breach affecting data for which we are the controller, we notify the Commission for Personal Data Protection within 72 hours of becoming aware, and affected individuals where the breach is likely to result in a high risk to their rights. Where a breach affects a customer's data, we notify that customer within 24 hours of becoming aware, so that it can meet its own 72-hour deadline.
Changes to this policy
#Every version carries a number, an effective date and a description of the changes. Material changes are notified to the customer company's contact address at least 30 days in advance. When a new version is adopted, the previous ones remain available on this site, unaltered.
Changes are not applied retroactively.
Version 1.0 · Effective 22 October 2026 · The Bulgarian text is authentic.