EN
Get started
  1. Home
  2. Legal documents
  3. Data Processing Agreement (DPA)

DATA PROCESSING AGREEMENT (DPA) — Annex to the Sendaro Terms and Conditions

This is a translation. If the language versions differ, the Bulgarian text prevails.

Effective from: 19 November 2026Merchants who registered before this date: in force after the 30-day period under clause 14.2 of the Terms; the date is in the email we sent you.

This document is subject to review by a lawyer.

1. Preamble, parties and roles

This Data Processing Agreement (the ‘Agreement’, the ‘DPA’) is an integral annex to the Sendaro Terms and Conditions of Use (the ‘Terms and Conditions’, the ‘Main Agreement’) and governs the processing of personal data by Sendaro on behalf of the Merchant under Article 28(3) of Regulation (EU) 2016/679 (General Data Protection Regulation, ‘GDPR’).

The parties are: (1) the Merchant – a natural or legal person who uses the Sendaro service for their own online shop, hereinafter the ‘Controller’; and (2) Vladov Komers EOOD, UIC 203224076, VAT No. BG203224076, Byala, Ruse Province, Bulgaria, email support@sendaro.bg, tel. +359 884 963 484, operator of the Sendaro platform (sendaro.bg, app.sendaro.bg), hereinafter the ‘Processor’ or ‘Sendaro’.

The Agreement is deemed concluded when the Merchant accepts the Terms and Conditions (click-through acceptance on sign-up or use of the service). Under Article 28(9) GDPR, the requirement for written form is met, including in electronic form.

With regard to the personal data of the Merchant’s end customers (the recipients of parcels), the Merchant is the Controller and Sendaro is the Processor. This Agreement governs only that processing. Processing for which Sendaro itself determines the purposes and means (managing the Merchant’s subscription, platform security, the ‘COD Trust’ register – see section 15) is governed by the Sendaro Privacy Policy, under which Sendaro is an independent controller.

In the event of any conflict between the Agreement and the Terms and Conditions on data protection matters, the Agreement prevails.

2. Definitions

‘GDPR’ – Regulation (EU) 2016/679. The terms ‘personal data’, ‘processing’, ‘controller’, ‘processor’, ‘data subject’, ‘personal data breach’ and ‘supervisory authority’ have the meaning given in Article 4 GDPR.

‘Applicable data protection law’ – the GDPR, the Bulgarian Personal Data Protection Act (PDPA) and the secondary legislation implementing them, as well as the relevant guidelines of the Commission for Personal Data Protection (CPDP) and the European Data Protection Board (EDPB).

‘End customer’ – a natural person who is a customer/recipient of the Merchant and whose data is processed when an order or delivery is fulfilled through the service.

‘Sub-processor’ – a third party engaged by Sendaro to process personal data on behalf of the Controller in providing the service.

‘Standard Contractual Clauses’ (‘SCCs’) – the clauses under Commission Implementing Decision (EU) 2021/914 for the transfer of data to third countries. ‘EEA’ – the European Economic Area.

3. Subject matter and scope

Sendaro processes the personal data of the Merchant’s end customers solely to provide the service requested and configured by the Merchant – creating waybills, calculating delivery prices, tracking, notifications (SMS/email), a returns portal, label printing, picking/packing, cash on delivery reports and the related functions under the Terms and Conditions.

A full description of the processing (subject matter, nature, purpose, type of data, categories of data subjects) is set out in Annex I, which forms an integral part of the Agreement.

Sendaro does not use the end customers’ personal data for its own purposes, does not sell it, does not use it for advertising and does not use it to train models.

4. Duration of the processing

Processing continues for the term of the Main Agreement (while the Merchant has an active account/subscription and a connected shop), unless a longer period is required by EU law or the law of the Republic of Bulgaria (e.g. accounting/tax retention periods – see section 11).

After termination of the Main Agreement, the procedure for the return and deletion of data under section 11 applies.

5. Controller’s instructions (Article 28(3)(a))

Sendaro processes personal data only on documented instructions from the Controller, including with regard to transfers to third countries, unless EU or Member State law requires Sendaro to process the data otherwise; in that case, Sendaro informs the Controller of that legal requirement before processing, unless that law prohibits this on important grounds of public interest.

The following are deemed documented instructions: (i) this Agreement and the Terms and Conditions; (ii) the settings and functions the Merchant selects and activates in the dashboard and in the checkout (which courier, which notifications, returns); (iii) the Merchant’s actions through the service (creating waybills, editing orders); (iv) additional written instructions sent through the contact procedure.

If Sendaro considers that an instruction infringes the GDPR or other applicable data protection law, it will inform the Controller immediately.

6. Confidentiality of personnel (point (b))

Sendaro ensures that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.

Access to personal data is granted only to employees/contractors who need it to provide the service (the ‘need to know’ principle) and is revoked once that need ceases.

7. Security of processing – Article 32 (point (c))

Sendaro implements appropriate technical and organisational measures to ensure a level of security appropriate to the risk, taking into account the scope, context and purposes of the processing. The measures are described in Annex II and are subject to periodic review.

The measures currently include, among others: encryption at rest (AES-256-GCM) of sensitive credentials and tokens (‘*Enc’ fields); encryption of traffic in transit (TLS/HTTPS); HMAC-SHA256 state signing in OAuth-like flows; logical isolation of each Merchant’s data by tenant identifier (tenantId); role-based access control; access and activity logs; hosting with Railway in the USA, with the safeguards described in section 13.

Sendaro does not store end customers’ payment card numbers.

8. Sub-processors (Article 28(2) and (4); point (d))

The Controller gives Sendaro general prior authorisation to engage sub-processors to provide the service. The current list is in Annex III and is kept publicly available at /legal/privacy.html.

Before adding or replacing a sub-processor, Sendaro will notify the Controller (by email and/or via the dashboard) at least 15 days in advance, giving it the opportunity to object.

The Controller may object to a new sub-processor on reasonable grounds relating to data protection within that period. The parties will make good-faith efforts to find a solution; if none is reached, the Controller may terminate the affected service in accordance with the Terms and Conditions. Failure to object within the period is deemed to be consent.

Sendaro enters into a written contract with each sub-processor that imposes data protection obligations no less strict than those under this Agreement (Article 28(4)). Sendaro remains fully liable to the Controller for the performance of its sub-processors’ obligations.

9. Assistance with data subject rights (point (e))

Taking into account the nature of the processing, Sendaro assists the Controller by appropriate technical and organisational measures, insofar as this is possible, in fulfilling its obligation to respond to data subjects’ requests under Chapter III GDPR (access, rectification, erasure, restriction, portability, objection).

If a data subject makes a request directly to Sendaro, Sendaro will not decide on its merits itself but will forward the request to the relevant Controller without undue delay.

For platforms that require mandatory data protection channels (e.g. Shopify webhooks customers/data_request, customers/redact, shop/redact), Sendaro provides the corresponding functionality to support the fulfilment of requests.

10. Security breaches, DPIA and prior consultation (point (f); Articles 32–36)

Sendaro assists the Controller in complying with its obligations under Articles 32–36 GDPR, taking into account the nature of the processing and the information available to Sendaro.

On becoming aware of a personal data breach affecting data processed for the Controller, Sendaro will notify the Controller without undue delay and no later than 48 hours after becoming aware of it, so that the Controller can meet its own 72-hour deadline for notifying the supervisory authority under Article 33 GDPR. The notification contains the available information on the nature of the breach, the categories and approximate number of data subjects/records concerned, the likely consequences and the measures taken/proposed.

On request, Sendaro provides reasonable assistance with data protection impact assessments (DPIA, Article 35) and prior consultations with the supervisory authority (Article 36), insofar as they relate to the processing under this Agreement.

11. Return and deletion of data (point (g))

When the provision of the services ends, Sendaro will, at the Controller’s choice, return or delete all personal data processed on the Controller’s behalf and delete existing copies, unless EU law or the law of the Republic of Bulgaria requires the data to be stored (e.g. accounting/tax obligations – in which case the data is kept only for the necessary period and only for that purpose).

Sendaro provides a 30-day window after termination for exporting/recovering data, after which it proceeds to full deletion. On written request, Sendaro issues a confirmation of deletion.

Deletion from active systems is carried out without undue delay. Backups are deleted when the usual rotation cycle expires (no longer than 90 days); until then, the data is not returned to active processing. Where immediate deletion is technically impossible, Sendaro blocks the data from further processing until it is deleted.

12. Audits and demonstrating compliance (point (h))

Sendaro makes available to the Controller the information reasonably necessary to demonstrate compliance with the obligations under Article 28 GDPR.

Compliance is demonstrated primarily by providing available independent reports/certifications (e.g. SOC 2 / ISO), including those of sub-processors.

An on-site audit or inspection by the Controller (or by an auditor authorised by it and bound by confidentiality) is permitted only where there is reasonable suspicion of non-compliance or at the express request of a supervisory authority, with the scope and timing agreed in advance, during working hours, without compromising the security of other customers’ data, no more than once every 12 months and at the Controller’s expense (unless the audit reveals a material breach or follows a security breach).

13. International data transfers

Data is stored and processed with Railway in the USA, and certain features also use other sub-processors outside the EEA (see Annex III). Such transfers take place only on an appropriate basis under Chapter V of the GDPR.

Transfers are based on: (i) an adequacy decision, including the EU-US Data Privacy Framework, insofar as the recipient is currently certified under it; and/or (ii) the Standard Contractual Clauses under Decision (EU) 2021/914 – Module 2 (controller → processor) and Module 3 (processor → sub-processor), which are deemed to be concluded between the relevant parties by this Agreement, together with the applicable addenda for the United Kingdom and Switzerland, where relevant.

Sendaro does not rely solely on the EU-US Framework. If an adequacy decision is withdrawn or suspended, the SCCs remain in effect as an independent basis. Sendaro maintains a Transfer Impact Assessment and updates it when material changes occur.

14. Recipients – independent controllers (couriers)

Courier companies (e.g. Econt, Speedy, Sameday, BOX NOW, Pigeon Express, euShipments) to which recipient data is passed for delivery act as independent controllers under their own legal obligations as carriers, not as Sendaro’s sub-processors. Each of them processes the data under its own responsibility and in accordance with its own privacy policy.

Data is passed to a courier on the Controller’s instructions (when a waybill is created) and is necessary to perform the requested service.

15. Special case – the ‘COD Trust’ register

‘COD Trust’ is a platform register of anonymised reports between Merchants about recipients with uncollected parcels (cash on delivery). The public view shows only aggregated information (‘N shops’), without revealing the identity of the reporting Merchants; the person concerned can raise a dispute on a dedicated page.

For this register, Sendaro determines the purposes and means of the processing (preventing fraud/uncollected parcels for the benefit of the whole platform) and therefore acts as an independent controller, not as a processor. Consequently, the register does NOT fall within the scope of this Agreement; it is governed by Sendaro’s Privacy Policy on a separate legal basis (legitimate interest under Article 6(1)(f) GDPR).

16. Liability

The parties’ liability is governed by Article 82 GDPR and the Main Agreement. The limitations of liability in the Terms and Conditions also apply to this Agreement to the extent permitted by mandatory law.

Each party is liable for damage caused by processing that infringes its obligations under the GDPR. The processor is liable for damage only where it has not complied with obligations specifically directed to processors or has acted outside or contrary to the Controller’s lawful instructions.

Nothing in this Agreement limits any liability that cannot be limited under applicable law.

17. Term, amendments and final provisions

This Agreement takes effect on acceptance of the Terms and Conditions and remains in force for as long as Sendaro processes personal data on the Controller’s behalf.

Sendaro may update this Agreement to reflect changes in the law or in the service, with notice via the dashboard/email; material changes take effect in accordance with the Terms and Conditions. Amendments that reduce the level of protection below the requirements of the GDPR may not be made unilaterally.

Matters not covered here are governed by the Terms and Conditions, the Privacy Policy, the GDPR and Bulgarian law. The governing law is Bulgarian law; disputes fall within the jurisdiction of the competent Bulgarian courts, in accordance with the Terms and Conditions.

Annexes I–III form an integral part of this Agreement. This document is published and kept available at https://www.sendaro.bg/legal/dpa.html, with a link in the footer next to the Terms and Conditions and the Privacy Policy. Effective date/version: 19 November 2026, version 1.1.

Annex I – Description of the processing

Subject matter: processing of personal data of the Merchant’s end customers to provide the Sendaro service.

Nature of the processing: collection, storage, structuring, use, transmission (to couriers and notification providers on the Controller’s instructions) and erasure.

Purpose: creating and managing waybills; calculating delivery prices; tracking; notifications to end customers (SMS/email); returns portal; label printing; picking/packing; cash on delivery reports; related functions.

Categories of data subjects: the Merchant’s end customers/recipients (natural persons).

Categories of personal data: name; phone number; email address; delivery address or chosen courier office/parcel locker; order contents and value; cash on delivery amount; order/waybill identifiers; tracking/status data. Sendaro also processes internal notes on an order or customer when the Merchant adds them. No special categories of data under Article 9 GDPR are processed, nor are payment card numbers.

Duration: the term of the Main Agreement plus the periods set out in section 11.

Annex II – Technical and organisational measures (TOMs)

Encryption: sensitive credentials/tokens are stored encrypted with AES-256-GCM (‘*Enc’ fields); traffic is transmitted over TLS/HTTPS; HMAC-SHA256 state signing in OAuth-like flows.

Isolation and access: logical isolation of data per Merchant (tenantId) with tenant filtering; role-based access control; the ‘need to know’ principle.

Traceability: access and activity logs.

Resilience and recovery: backups with a rotation cycle of up to 90 days; hosting with Railway (USA).

Organisational measures: confidentiality obligations for staff; sub-processor management; a security breach procedure; two-factor authentication (TOTP) with backup codes; encrypted storage of third-party keys and tokens; access and activity logs; a limited number of people with access; regular dependency updates.

Annex III – List of sub-processors

Railway (hosting and PostgreSQL database) – USA; transfer mechanism: the EU-US Data Privacy Framework (Railway is certified, including the extensions for the UK and Switzerland) and SCCs; sub-sub-processors published at trust.railway.com.

Anthropic (automated processing of messages and description of photos, Claude API) – USA; transfer mechanism: SCCs (Modules 2 and 3); main sub-sub-processor: AWS. Inputs/outputs are not used for training; operational logs are deleted after 7 days by default.

SMSAPI (sending SMS notifications) – Poland (EU); processes phone numbers and message content.

JetHost (email hosting for the domain) – EU location; processes email addresses and message content.

Revolut – processes payment data for the Merchant’s subscription (not end customers’ data) as a payment service provider. For this data, Sendaro is the controller and Revolut acts as an independent controller under its own legal obligations – see the Privacy Policy. Listed here for transparency.

Note: courier companies are NOT sub-processors but independent controllers (see section 14).