These Terms govern the relationship between Dedilayer Ltd. and legal entities and sole traders using the ZynTrail platform. The service is not offered to consumers within the meaning of the Bulgarian Consumer Protection Act.
This is a translation provided for convenience. The Bulgarian text is authentic and prevails in the event of any discrepancy.
Provider
#| Legal name | Dedilayer Ltd. |
|---|---|
| Registered seat and address of management | Sofia, Bulgaria |
| sales@zyntrail.com · data protection: privacy@zyntrail.com | |
| Data protection supervisory authority | Commission for Personal Data Protection, www.cpdp.bg |
Published pursuant to Art. 4 of the Electronic Commerce Act (Закон за електронната търговия).
Definitions
#Service: the ZynTrail platform at https://app.zyntrail.com, together with all features included in the subscription.
Customer: the legal entity or sole trader that has concluded a contract on these Terms.
User: a natural person holding an account in the Service, created by the Customer.
Customer Data: all data the Customer enters into the Service or which arrives in it through connected channels, including data about its own customers and counterparties, messages, files and call recordings.
Annex 1: the Data Processing Agreement, which forms an integral part of these Terms.
Formation of the contract
#3.1 How it is concluded
#The contract is concluded either through the registration form at https://app.zyntrail.com/register or on request to the Provider, in which case the Provider creates the account.
Through the form, the steps and their legal effect are:
- The Customer's representative fills in the company's details and their own, and ticks that they accept these Terms and Annex 1 on the Customer's behalf and are authorised to represent it. Sending the form is the Customer's statement to conclude a contract on these Terms.
- The Provider confirms receipt by email to the address given. The representative confirms that address through the link in the email within 24 hours; without that confirmation the statement has no effect.
- The Provider reviews the request, including the registration number and, for EU companies, the VAT number in the European Commission's VIES system. The Provider may decline to conclude a contract without giving reasons.
- On approval the Provider sends a link to set a password. The contract is concluded when the representative sets the password and the account is activated; the trial under section 5.1 starts then.
Until the form is sent, every field can be corrected, and the form points out invalid data, such as an EIK with a wrong check digit. After sending, an error is corrected by writing to sales@zyntrail.com and, once the account is active, in its settings.
The Provider keeps the record under section 3.2. The Customer receives the text of the Terms under section 3.3, and every version stays available at a permanent address on the website. The language of the contract is set by section 3.5.
Electronic acceptance is valid under Art. 293(4) of the Commerce Act (Търговски закон): the written form is deemed observed where the statement is recorded technically in a manner permitting its reproduction. It also takes effect under Art. 25(1) of Regulation (EU) No 910/2014, under which an electronic signature shall not be denied legal effect solely because it is in electronic form.
Customers who prefer it may sign the contract with a qualified electronic signature.
3.2 What is recorded on acceptance
#On acceptance the Provider records and retains unaltered: the Customer's name and registration number; the name and email address of the accepting individual and their statement that they are authorised to represent the Customer; the version number and SHA-256 checksum of the exact authentic Bulgarian text of the Terms and Annex 1 accepted; the date and time in UTC; the IP address; and the method of acceptance (registration form, request, or qualified electronic signature).
The record is kept for the term of the contract and three years after termination. Every superseded version remains available at a permanent address.
3.3 Binding effect and order of precedence
#Under Art. 298 of the Commerce Act, general terms established by a merchant bind the other party only if they were delivered to it at the time of conclusion. The Provider therefore delivers the full text of the Terms and Annex 1 as an attachment to the email confirming that the account has been created.
Under the same provision, individually negotiated terms prevail over general terms. The order of precedence is:
- an individually signed order form or agreement;
- Annex 1 (Data Processing Agreement);
- these Terms of Service.
3.4 The Customer confirms it is not a consumer
#On acceptance the Customer declares that it is contracting in the course of its trade or profession and is not acting as a consumer within the meaning of the Consumer Protection Act. The Provider collects the EIK (for companies outside Bulgaria another registration number, and the VAT number where there is one) precisely so that this is verifiable.
3.5 Language
#The contract is concluded in Bulgarian. The published English and Russian texts are translations for convenience. In the event of discrepancy, the Bulgarian text prevails.
3.6 Sanctions
#The Service is not provided to persons established in Russia or Belarus, or to persons listed in EU sanctions lists. The basis is Regulation (EU) No 833/2014 and Regulation (EC) No 765/2006. On acceptance the Customer declares that it is not such a person.
The Russian text is for Russian-speaking businesses established in countries where the Service may lawfully be provided.
Scope of the Service
#The features included in each subscription plan are described in the Service and on the website. The Provider may add features. Removal or material restriction of a feature from the current plan is notified at least 60 days in advance and entitles the Customer to terminate without penalty as of the date of the change.
External channels (email, Messenger, Instagram, WhatsApp, Telegram for team alerts, and the Customer's own Twilio account, only for companies that already use it) are connected using the Customer's own accounts. The Customer obtains its phone numbers and lines from its own operator (a SIP trunk or call forwarding), under its own contract with that operator. The Provider provides the software of the ZynTrail Voice phone system. For its own accounts and channels, the Customer declares that it holds the necessary rights and complies with the respective providers' terms. Termination or restriction of access by such a provider is not a breach by ZynTrail.
4.1 Support and onboarding
#Support is by email, at support@zyntrail.com. It covers questions about using the Service, setup and errors.
The Start plan includes up to 1 hour of support a month. On the Business, Pro and Enterprise plans support has no hourly limit, within reasonable use.
Onboarding is free on every plan. It covers the initial setup, done together with the Customer: mailboxes, channels, departments, users and connecting the Customer's own telephone operator.
Developing features for a single customer and work inside the Customer's own systems, for example at its telephone operator, are outside support.
Trial, prices, payment
#5.1 Trial
#A 30-day free trial is provided on account creation. It creates no payment obligation and may be ended at any time.
5.2 Prices
#Prices are stated in euro in the published price list. These Terms refer to the price list rather than reproducing it, so that a price change does not require the contract to be reissued.
Prices are exclusive of VAT. The Provider charges VAT under the Bulgarian Value Added Tax Act where applicable. For customers VAT-registered in another Member State, the place of supply is where the recipient is established and the reverse charge applies, with the invoice bearing the corresponding annotation. The Customer must provide a valid VAT number and notify any change immediately. Where the number is invalid or withdrawn, the Provider charges Bulgarian VAT and the Customer owes the difference.
5.3 Payment
#Payment is made by card through Stripe or by bank transfer against an issued invoice. The Provider does not receive or store payment card data. The subscription renews automatically for a further term equal to the preceding one unless terminated.
5.4 Price changes
#The price is fixed for the current subscription term. Changes take effect from the next term and are notified at least 30 days before the renewal date. The Customer may decline by terminating before renewal. Continued use after the start of the new term constitutes acceptance.
The Provider does not reserve a right to change the price unilaterally within a current term.
5.5 Late payment
#On late payment the Provider is entitled to statutory interest under Art. 294 of the Commerce Act, and to compensation for recovery costs under the rules on late payment in commercial transactions.
5.6 Refunds
#No statutory right of withdrawal applies between merchants. Amounts paid are not refunded pro rata on termination before the end of the term. Termination takes effect at the end of the paid period.
When the subscription ends: read-only, then deletion
#The subscription ends when the Customer cancels it (at the end of the paid period, under section 8.1), when the free trial ends without payment, or when a payment for a new term is declined and the 7-day grace period runs out. The grace period applies to a card payment that Stripe is still retrying. During it the Service operates unchanged.
For a subscription paid by bank transfer, if the payment for the next period has not arrived by the end of the paid period, the account becomes read-only the next day. The 30 days and 14 days described below run from that day.
After the subscription ends, the account is read-only for 30 days. During those days the Customer and Users see all data and can export it under section 8.3, but cannot create or modify records.
After those 30 days the Customer's company and all its data are deleted from live systems within 14 days (section 8.5). The Provider warns the Customer by email 14 days and 3 days before deletion.
The precise scope of the restriction in this mode, including what happens to incoming messages, calls and external notifications, is described in the Service, in the subscription section.
Availability
#7.1 What the Provider owes
#The Provider exercises the care of a prudent merchant under Art. 302 of the Commerce Act and performs in good faith under Art. 63 of the Obligations and Contracts Act. These duties cannot be excluded by contract and are not excluded by these Terms.
7.2 What the Provider does not guarantee
#The Provider does not guarantee any particular availability percentage. The Service runs from a single server configuration without real-time redundancy.
7.3 Target figures
#| Measure | Value | Source |
|---|---|---|
| Maximum data loss on failure (RPO) | up to 6 hours | Backup every 6 hours |
| Restoring the database from a backup | 6 seconds (measured) | Drill of 1 September 2026 |
| Full recovery of the service onto a new host | not measured | — |
These figures are targets and were measured in a recovery drill.
The six seconds are the time taken to bring the data back from a backup. They do not include detecting the failure, provisioning a new host or repointing addresses.
The drill is repeated and the results documented.
7.4 Planned maintenance
#Planned maintenance is announced at least 48 hours in advance. Emergency security updates are applied immediately and without prior notice.
7.5 Dependencies
#The Provider is not liable for unavailability caused by: Meta (Messenger, Instagram, WhatsApp), Google, Microsoft, Stripe, Telegram, the AI providers, the hosting provider, or the Customer's telecommunications operator (SIP provider). The same applies to the online shops, marketplaces, couriers and payment, invoicing and CRM services the Customer connects.
7.6 Force majeure
#Art. 306 of the Commerce Act applies. The affected party notifies the other in writing within a reasonable time. If the impediment persists long enough that the other party no longer has an interest in performance, either party may terminate.
Termination, data export, deletion
#8.1 Termination
#The Customer may terminate at any time. A subscription paid by card is cancelled under Billing in the Service or in the Stripe portal. A subscription paid by bank transfer is cancelled by email to support@zyntrail.com before the end of the paid period. Termination takes effect at the end of the paid period. The free trial ends by itself and needs no cancellation.
The Provider may terminate on 60 days' notice, and without notice for a material breach not remedied within 14 days of written demand.
8.2 Suspension
#The Provider may suspend access immediately in the event of an active security threat, use of the Service for unlawful activity, or sending unsolicited bulk messages that endanger the Provider's accounts with channel providers. The Customer is notified as soon as practicable.
8.3 Data export
#After the subscription ends (section 6), the Customer has 30 days in read-only mode in which to export its data.
Can be exported:
| Category | Format |
|---|---|
| Customers and counterparties | CSV / XLSX |
| Contacts | CSV |
| Tickets | XLSX |
| Messages per ticket | CSV / text |
| Attachments | Individual download through the Service |
| Shifts, leave and working time | CSV |
| Call recordings | Individual download through the Service; in bulk on written request |
Not exported in a single operation through the interface: call recordings in bulk and a full copy of the database in one file. The Provider supplies this data in a machine-readable format on written request, within 14 days and free of charge.
The list is exhaustive in accordance with Art. 25 of Regulation (EU) 2023/2854.
8.4 Switching providers
#Under Art. 25 of Regulation (EU) 2023/2854 (Data Act):
- the notice period for initiating a switch is no more than 2 months;
- the transitional period in which the data is transferred is no more than 30 days and starts after the notice period (Art. 25(2)(a)); the Customer may extend it once;
- after the transitional period the Customer has at least 30 days to retrieve its data (Art. 25(2)(g)). These are the 30 read-only days under sections 6 and 8.3; when the Customer switches providers, they start after the transitional period ends;
- the Provider imposes no contractual, commercial, technical or organisational obstacles to switching;
- the Provider levies no switching or export charge.
8.5 Deletion
#After the 30 days in 8.3, the Customer's company and all its data are deleted from live systems within 14 days. The Provider warns the Customer by email 14 days and 3 days before deletion. At the Customer's request the data is deleted or returned earlier.
The choice between deletion and return belongs to the Customer, under Art. 28(3)(g) GDPR.
Backups 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 persist in a backup for at most 30 days after erasure from the live system. During that period the copies are not read, except in an actual disaster recovery event.
The Provider's invoices and accounting documents are kept outside the platform, in Stripe and in the Provider's accounting, for the period the law requires. They are the Provider's data in its capacity as controller. The payment history the Customer sees in the platform is deleted together with the account.
Customer obligations and warranties
#The Customer declares and undertakes:
- to have a lawful basis for the data it enters into the Service, and to have informed its own data subjects;
- to inform its own employees about the processing of their data in the Service, including call recording and working-time records, before creating their accounts;
- not to enter special categories of data under Art. 9 GDPR, or criminal conviction data, without prior written agreement with the Provider; the exception is the fact of sick leave in the working-time module, on the terms of Annex 1, point 1;
- not to use the Service for unsolicited bulk messaging;
- to keep credentials confidential and to revoke the rights of departing employees;
- to keep its API keys secret and to be responsible for the addresses to which it sets up data to be sent (webhooks, Slack, Microsoft Teams, Zapier, Make, n8n and others);
- to comply with the terms of the connected channel providers.
Call recording
#Where the Customer uses the telephony functionality, it decides whether calls are recorded. The Customer's administrator switches recording on and off in the telephony settings.
Recordings are kept for 90 days and then deleted automatically. The Customer's administrator can choose another period in the telephony settings: 30, 90, 180 or 365 days. A longer period is set on written request to the Provider.
The Customer is the controller of the recordings. It decides whether to record, for what purpose and for how long, and it owes the notification. The Provider supplies the technical capability.
The Customer undertakes: to inform callers before the recording begins; to inform both the external participant and its own employee; not to rely on employee consent as a basis, insofar as it is not valid in an employment relationship; and to check that the chosen retention period fits the purpose of the recording. At the Customer's request the Provider records a spoken announcement about recording in the phone system's greeting.
Recordings are stored on the Provider's phone system, on a server in the EU (Annex 1, point 14). In that capacity the Provider acts as a processor on the Customer's instructions. ZynTrail also stores the call metadata.
Artificial intelligence
#- The model provider is determined by the subscription plan, is not chosen by the Customer, and is named in section 6 of the Privacy Policy.
- Processing is carried out on the Customer's instructions; the Customer remains controller of the content.
- Customer Data is not used to train models, neither by the Provider nor by the model provider.
- The Customer may disable AI features entirely.
- Every reply the AI 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 Service informs the person that they are interacting with an automated system, in accordance with Art. 50 of Regulation (EU) 2024/1689. The Customer may not remove or misrepresent this notification.
- A draft from the assistant that an agent has reviewed and sent is the agent's reply.
- Special categories of data under Art. 9 GDPR are not to be routed to the AI features (see also Annex 1, section 1).
Intellectual property
#The platform, source code, interface and documentation are and remain the Provider's property. The Customer receives a non-exclusive, non-transferable right of use for the term of the contract.
Customer Data remains the Customer's. The Provider acquires no rights in it and does not use it for its own purposes (section 6 of Annex 1).
If the Customer provides suggestions for improvement, the Provider may use them without obligation to pay. This does not extend to Customer Data.
Confidentiality
#Each party keeps confidential the other's information to which it gains access and does not disclose it to third parties except to staff and subcontractors bound by the same duty. The obligation applies for the term of the contract and 3 years after termination, and for trade secrets until they lose that character.
Liability
#14.1 What cannot be limited
#The limitations in this section do not apply in cases of intent or gross negligence, pursuant to Art. 94 of the Obligations and Contracts Act, which renders void any prior agreement excluding such liability. Nor do they apply where the law otherwise does not permit limitation.
14.2 Scope of damages
#Damages cover loss that was foreseeable at the time the contract was concluded, under Art. 82 of the Obligations and Contracts Act. No compensation is due for lost profits, for indirect loss or for unforeseeable loss.
14.3 Cap
#The Provider's total liability under the contract for all events in any twelve consecutive months shall not exceed the amount paid by the Customer for that same period.
Exception: for breach of the confidentiality obligation and for a personal data breach for which the Provider is responsible, the cap is three times the annual subscription fee.
14.4 GDPR liability
#The limitations in this section govern the contractual relationship between the Provider and the Customer. They do not and cannot affect a data subject's right to seek compensation directly from the Provider or the Customer under Art. 82 GDPR, including their joint and several liability and the right of recourse between them.
14.5 Contractual penalties
#An agreed penalty is not subject to reduction for being excessive, under Art. 309 of the Commerce Act. This rule operates in favour of both parties.
Amendments
#Amendments are notified at least 30 days in advance and take effect from the next subscription term. Continued use after the start of the new term constitutes acceptance. A Customer that does not accept an amendment may terminate before renewal without penalty.
Only amendments required by law or by a change in a sub-processor's terms take immediate effect. In such a case the Provider states the reason expressly.
Annex 1 is amended under section 13 of that Annex, as it reflects the Customer's instructions as controller.
Every version carries a number, a date and a description of the changes. Superseded versions remain available at permanent addresses.
Assignment
#The Customer may not assign its rights without the Provider's written consent. The Provider may assign the contract on a corporate reorganisation or sale of the business, notifying the Customer and giving it a right to terminate within 30 days.
Governing law and jurisdiction
#Bulgarian law applies, pursuant to Art. 3 of Regulation (EC) No 593/2008.
Disputes shall be resolved by the competent court in Sofia, Bulgaria, pursuant to Art. 117(2) of the Civil Procedure Code and Art. 25 of Regulation (EU) No 1215/2012. Under Art. 25(2) of that Regulation, any communication by electronic means which provides a durable record of the agreement is equivalent to writing, so this clause binds where the Terms were accepted electronically.
If any clause is held invalid, the remainder continues in effect and the invalid clause is replaced by a permissible clause of the closest effect.
ANNEX 1. Data Processing Agreement
#Concluded pursuant to Art. 28 of Regulation (EU) 2016/679, between the Customer as controller and Dedilayer Ltd. as processor. This Annex forms an integral part of the Terms of Service and is accepted together with them. On request, the Provider supplies an identical text as a standalone document for signature, including by qualified electronic signature.
1. Subject matter (Annex I under Art. 28(3))
#| Subject matter | Provision of a customer service platform. It consists of modules: channels (email, website chat, Messenger, Instagram, WhatsApp, team alerts in Telegram); telephony with call recording; online shops and marketplaces; connected services (payments, invoices, CRM, developer issues, reviews); satisfaction survey; AI features; working time. The controller decides which modules to use, within its subscription plan |
|---|---|
| Duration | For the term of the contract, plus the 30-day export window under section 8.3 and up to 14 days for deletion under section 8.5 of the Terms |
| Nature and purpose | Storage, structuring, display, search, transmission over channels, automated assistance, archiving, all exclusively on the controller's instructions. The working-time module calculates indicators for staff (late start and adherence to schedule), which serve only as information for the manager |
| Categories of data subjects | The controller's customers and counterparties; persons who contact the controller through any channel, including visitors to the chat on its website; buyers from the controller's online shops and marketplaces; authors of reviews about the controller; the controller's employees |
| Categories of data | Channels: names, company names, EIK, VAT number, responsible person, addresses, telephone numbers, email, preferred language; message text from email, website chat, Messenger, Instagram, WhatsApp and web form; attachments; the address of the page a chat visitor writes from; internal correspondence between the controller's staff. Telephony: call data (direction, status, duration, operator, contact) and the audio of the recordings, which the Provider keeps on its phone system. Online shops and marketplaces: orders and the products in them; the buyer's name, email and telephone; delivery and billing address; payment and delivery method; the buyer's note; shipments and tracking numbers; buyer messages. Connected services: payments, invoices, CRM data, developer issues, reviews from Trustpilot (author's name, rating, text). Survey: the end customer's rating from 1 to 5 and comment. AI: drafts, summaries and replies created by the assistant. Working time: shifts, leave, sick leave, shift swaps, attendance and activity of staff |
| Special categories | The working-time module records the fact of sick leave (temporary incapacity for work). This is health data under Art. 9 GDPR. Only the dates and the type of absence are recorded, never a diagnosis. The controller, as employer, processes it under Art. 9(2)(b) GDPR in connection with the Bulgarian Labour Code. The controller undertakes not to enter diagnoses or medical documents in free-text fields. Other Art. 9 data is entered only after prior written agreement with the Provider |
2. Instructions
#The processor processes personal data only on documented instructions from the controller, including as regards transfers to third countries, unless required to do otherwise by Union or Member State law; in that case the processor informs the controller before processing, unless that law prohibits such information.
Instructions comprise: the Terms of Service; this Annex; the settings the controller configures in the platform itself, including choice of channels, switching AI features on or off, retention periods and user permissions; the default settings, for as long as the controller leaves them unchanged (for example the satisfaction survey); and written requests submitted through support.
The processor shall immediately inform the controller if, in its opinion, an instruction infringes the GDPR or other data protection provisions.
3. Confidentiality
#Persons authorised to process personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
The Provider's staff access the controller's account only at the controller's request (onboarding, support) or for a security incident. Every such access is recorded, and the controller sees it in its account's audit log.
4. Security (Annex II)
#The processor implements the measures required by Art. 32 GDPR, described in Annex II to this Agreement (section 12 below).
The processor may update the measures in Annex II provided that the level of security is not reduced.
5. Sub-processors
#The controller gives general prior authorisation for the sub-processors listed in Annex III (point 14 below), with country, purpose and transfer mechanism. The processor also provides the list on request at privacy@zyntrail.com.
Where the processor intends to add or replace a sub-processor, it notifies the controller at least 30 days in advance. The controller may object in writing within 14 days. Where a well-founded objection cannot be resolved, either party may terminate without penalty.
The processor imposes the same data protection obligations on each sub-processor and remains fully liable to the controller for its performance.
6. The processor does not use the data for its own purposes
#The processor does not use personal data processed on the controller's behalf for its own purposes: not for product improvement, not for model training, and not for aggregate analytics that are not fully anonymous within the meaning of Recital 26 GDPR.
7. Assistance with data subject rights
#The processor assists the controller in responding to requests under Chapter III GDPR through: the search, export, rectification and deletion functions in the platform; and, where necessary, extraction on written request.
The functions for exporting and deleting the data about one person cover tickets, messages, files, calls and call recordings, as well as orders and shipments from connected online shops.
Assistance deadline: 7 days from written request.
If a data subject request arrives directly with the processor, it does not respond on the merits but forwards it to the controller within 5 business days.
8. Assistance under Arts. 32 – 36
#The processor assists the controller with: ensuring security; notifying breaches; communicating breaches to data subjects; data protection impact assessments; and prior consultation with a supervisory authority.
For the purposes of an impact assessment, the processor supplies a pack containing a system description, data flows, applied measures, the sub-processor list and the available retention options.
9. Personal data breaches
#The processor notifies the controller without undue delay and no later than 24 hours after becoming aware of a breach affecting its data.
The notification states: the nature of the breach; the categories and approximate number of data subjects and records concerned; the likely consequences; the measures taken and proposed; and contact details.
10. Deletion or return
#When the contract ends, the controller chooses whether the data is deleted or returned. Return takes place through the export under section 8.3 of the Terms during the 30 read-only days. After them the data is deleted within 14 days, and the controller receives an email warning 14 days and 3 days before deletion (sections 6 and 8.5 of the Terms).
The processor also deletes existing copies, except where Union or Member State law requires storage. For backups, the cycle in section 8.5 of the Terms applies.
11. Audit
#The processor makes available to the controller all information necessary to demonstrate compliance with Art. 28, and allows for and contributes to audits.
First tier: on written request the processor supplies, within 20 days, a completed security questionnaire, a summary of restore drill results, and written answers to specific questions.
Second tier: if the controller reasonably considers the above insufficient, it may conduct an on-site or remote inspection, at its own cost, no more than once every 12 months (save at the request of a supervisory authority or following a breach), on 30 days' notice, during business hours, by an auditor who is not a competitor of the processor and is bound by confidentiality.
The scope of any inspection excludes other tenants' data and systems whose inspection would compromise their security.
12. Annex II. Technical and organisational measures
#- Transmission: HTTPS only, with automatically renewed certificates.
- Storage: the controller's credentials for external channels are stored encrypted.
- Access control: authentication by session cookies of limited duration; separation by role and by department; revocation of rights takes effect from the next request.
- Tenant separation: verified regularly, including by automated tests.
- Files: delivered only via a signed temporary URL; the directory is not publicly served.
- Traceability: administrative actions on accounts are written to an audit log.
- Backups: every 6 hours; retained up to 7 days on the server and up to 30 days in an offsite copy; restore drill performed and documented.
- Infrastructure: server access by cryptographic key only; firewall enabled; automatic security updates.
- Offsite copy: encrypted with symmetric AES-256 before it leaves the server, with a passphrase the storage provider does not hold; only ciphertext is stored there. Every file is read back before upload, and the export fails with an error if the passphrase is missing.
13. Amendment of this Annex
#This Annex is not amended under the procedure for amending the Terms of Service, because it reflects the controller's instructions.
Material amendments require the controller's express acceptance. Changes to the sub-processor list follow the procedure in section 5. Amendments required by law take effect after written notification stating the reason.
14. Annex III. Sub-processors
#Named list of the sub-processors under point 5, with country, purpose and transfer mechanism.
| Sub-processor | Country | Purpose | Transfer mechanism |
|---|---|---|---|
| Contabo GmbH | Germany; the data centre is in the EU | Hosting of the platform and of the ZynTrail Voice phone system, including call recordings | No transfer |
| Google (Google Cloud Text-to-Speech) | Ireland, with possible onward transfer to the USA | Speech from the text of the phone system's voice menus and greetings entered by the Customer | Adequacy decision (EU–US Data Privacy Framework) |
| Brevo (Sendinblue SAS) | France | Sending email from zyntrail.com addresses, including system notices | No transfer |
| Scaleway SAS | France | Encrypted offsite backups, kept for up to 30 days | No transfer |
| Google Ireland Limited (Google Drive) | Ireland, with onward transfer to the USA | Encrypted offsite backups | Adequacy decision (EU–US Data Privacy Framework); should it lapse, Standard Contractual Clauses under Implementing Decision (EU) 2021/914 |
| Sentry (Functional Software, Inc.) | Germany (Sentry's EU data region); the provider is based in the USA | Reports of errors in the platform; passwords and access keys are removed before sending | Standard Contractual Clauses under Sentry's data processing agreement |
| OpenAI | Ireland, with onward transfer to the USA | AI features, where the plan includes them | Standard Contractual Clauses under the data processing agreement |
| Google Gemini | Ireland | AI features, where the plan includes them; paid tier only, under which data is not used to train models | Standard Contractual Clauses under the data processing agreement |
| Browser push services: Google Firebase Cloud Messaging, Apple Push Notification service, Mozilla | USA | Notifications to users who have switched them on: the technical subscription address and the notification text, encrypted under the Web Push standard | Adequacy decision (EU–US Data Privacy Framework) or Standard Contractual Clauses, depending on the provider |
| Telegram | United Arab Emirates | Team alerts, only when the controller switches the channel on | No adequacy decision. The controller assesses the transfer (section 6.1 of the Privacy Policy) |
Stripe acts as an independent controller for payments. Meta and Microsoft work under accounts the controller connects itself. Google Analytics and the VIES system process only the Provider's own data. For these reasons they are not on the list. The same applies to the services the controller connects in the platform (online shops, marketplaces, couriers, payments, invoices, CRM, Slack, Microsoft Teams, Zapier, Make, n8n and others): they work under the controller's own contract with them.
Version 1.0 · Effective 22 October 2026 · The Bulgarian text is authentic.