Back to Home
Data Export Register
Version: 2.1-draft · Effective date: [not yet in effect]
This document is a draft under legal review. It is not yet published and not yet in effect.
1. Purpose of This Register
This page is the online register required by Article 26 of Regulation (EU) 2023/2854 (the Data Act). It specifies the categories of data and digital assets that a Customer can export from Sended, the categories exempt as the Provider's internal or proprietary data, and the available formats and known technical restrictions. Under Section 20.4 of the Terms of Service, this register forms part of the Agreement.
Export requests are made in writing to privacy@sended.io (Terms of Service, Section 20.4). Exports are currently fulfilled by the Provider as a manual process, without undue delay, and free of charge (Terms of Service, Section 20.7).
2. Exportable Data and Digital Assets
| Category | Contents | Format |
|---|---|---|
| End Client records | The synchronized client base: name, phone, email, date of birth, gender, notes, tags, custom fields, visit statistics, loyalty data, external (Altegio) identifiers | JSON |
| Appointments | Synchronized appointment records incl. services, staff, times, status, prices, comments | JSON |
| Staff and services | Synchronized staff roster and service catalogue | JSON |
| Conversations | Unified-inbox message history per conversation: message text, timestamps, direction, delivery status, media references, voice-message transcriptions | JSON |
| Received media files | The files (photos, videos, voice messages, documents, stickers) End Clients sent through the unified inbox that the Service stores, each with an index entry linking it to its message | Original files, with a JSON index |
| AI assistant history | The AI assistant's conversation transcripts (retained for up to 90 days by design) | JSON |
| Campaigns | Campaign definitions, audiences, message content per channel, schedules, and per-recipient delivery results (sent / failed / skipped with reason) | JSON |
| Automations | Automation definitions, triggers, message content, and run history | JSON |
| Segments | Segment definitions and current member lists | JSON |
| Opt-out records | The Customer's marketing opt-out register (client, source, timestamp) and WhatsApp permission events incl. recorded evidence | JSON |
| Message templates | Saved templates with their content and variables | JSON |
| Uploaded images | Brand assets and message/campaign images uploaded by the Customer | Original files, or a list of their URLs |
| Account and settings | Workspace settings, branding, sender identity, quiet-hours configuration, member list of Authorized Users | JSON |
| Legal-acceptance records | Which document versions the Customer's users accepted and when | JSON |
3. Exempt Categories (Provider's Internal or Proprietary Data)
- The Provider's application source code, infrastructure configuration, and operational tooling;
- the service-wide email suppression list and per-tenant deliverability (bounce/complaint) statistics, which the Provider maintains in its own controller capacity (Privacy Policy, Section 4.3);
- internal security, audit, and system logs, and fraud-prevention data;
- aggregated or de-identified data that does not relate to the Customer;
- billing records held by Stripe (the Customer retrieves invoices and receipts directly through the Stripe billing portal);
- WhatsApp conversation-pricing evidence derived from Meta's rate cards (a provisional-estimate ledger; the authoritative record is the Customer's own Meta billing).
4. Known Technical Restrictions
- Exports are prepared manually by the Provider; delivery is by secure download link to the Customer's account email.
- The export is a set of JSON files, one per category above, with a manifest that states the number of records in each.
- Data already removed under the retention schedule of the Privacy Policy Section 9.1 is not in the export: for example the text of a message sent more than 180 days earlier is empty, while its delivery result is included.
- The AI assistant history is held in a separate store and is exported from it separately.
- Media files referenced in already-sent messages remain at their public URLs (Terms of Service, Section 14.5); the export lists those URLs rather than re-packaging the files where volumes are large.
- Received media files are exported as originally received, for as long as the Service keeps them with their message (Privacy Policy, Section 9.1). A file the Service did not store, or no longer holds, is not in the export; its message still carries the media reference. Voice-message transcriptions are exported as text.
- Data synchronized from Altegio can also be retrieved by the Customer directly from its Altegio account; the export reflects the Service's mirror at the time of preparation.
- No proprietary formats are used; there are no technical protection measures that would impede re-import of the exported data into another service.
5. Contact
Elephants Production s.r.o. Rybná 716/24, Staré Město, 110 00 Prague 1, Czech Republic Company ID (IČO): 23397292, registered in the Commercial Register maintained by the Municipal Court in Prague, File No. C 426391
Export requests and switching: privacy@sended.io