Knowledge content (Markdown), conversation history (JSONL), lead-capture records (CSV), audit log (CSV / JSON), tenant configuration (JSON). 30-day notice, 90-day export window, 7-day production-deletion, 35-day backup-purge. Survival of portability rights through bankruptcy, acquisition, solvency events. Pairs with security controls, compliance posture, RFP template.
Every piece of customer data - knowledge content, conversation history, lead-capture records, audit logs, configuration - is exportable on-demand in machine-readable formats and SLAtech-portable formats so customers can switch vendors at any time without re-engineering.
Customer-uploaded knowledge (FAQ pairs, articles, source documents) is stored in Markdown / plain text / JSON - open formats with no vendor-proprietary encoding. Export endpoint: /api/v1/knowledge/export returns a ZIP archive with per-document Markdown + a manifest.json describing the corpus. Re-importable into Chatbase, Tidio Lyro, ManyChat or any platform accepting Markdown / JSON ingest.
Every conversation logged with full context: visitor message, retrieval chunks, LLM response, citation snippets, confidence scores. Export endpoint: /api/v1/conversations/export returns JSONL - one conversation per line. Standard schema documented at /en/api-docs/. Re-importable as a training set, a business intelligence feed, or a compliance audit corpus.
Captured leads export from the admin as CSV (capture time, status, email, name, question, page URL). Each new lead also goes out in real time by webhook as JSON (name, email, phone, question, page, language), so a copy already lives in your own systems. The webhook is a generic JSON POST - to your own endpoint, or through Zapier or Make into HubSpot, Salesforce or Pipedrive - so your CRM connection survives a vendor switch.
13-month audit log of all admin actions (login, role change, configuration change, data export). Exportable as CSV or JSON via /api/v1/audit/export. Schema documented at /en/api-docs/. Compliance-friendly format suitable for SOC 2 evidence collection and GDPR Article 30 records.
Tenant configuration (channels enabled, intent rules, brand colours, system prompts, integrations, eval thresholds) exportable as a single JSON file via /api/v1/config/export. Re-importable to a fresh SLAtech tenant. Cannot directly import to other vendors but serves as a replication blueprint.
Standard MSA includes a continuity clause: SLAtech provides 30-day notice for material price increases. On termination by either party, 90-day data-export window. Survival of customer data-portability rights through bankruptcy, acquisition or solvency events.
Termination for convenience with 30 days notice. No early-termination fees on standard tiers. Enterprise contracts subject to individual MSA terms. Cancellation request via the admin platform's Settings → Account → Cancel or via security@slatech.ai. Confirmation email within 24 hours.
After 90-day export window, all customer data permanently deleted from production within 7 days. Backup purge follows within 35 additional days (per backup-retention policy). Deletion certificate available on request. No customer data persists in archives after the 35-day backup-purge window.
Most SaaS contracts provide a data-export option but encode tenant content in vendor-proprietary formats. Once you switch vendors you face a 3-6 month re-engineering cost. SLAtech ships data in open formats (Markdown / JSON / JSONL / CSV) so the switching cost is incremental, not foundational. Customers should never feel locked-in.
From the admin panel, today: conversations, captured leads and analytics as CSV, and the audit log as CSV or JSON. Each new lead is also delivered in real time by the signed lead webhook (JSON), so a copy already lives in your own systems. For a data-subject request we prepare one person's data as JSON (leads, questions and answers, Telegram subscriptions). Your knowledge sources are the files and pages you gave us: the originals stay with you.
Self-serve export endpoints available via API. Or request human-assisted export via security@slatech.ai.
Theme 4 of vendor due-diligence checklist (Data portability + vendor lock-in) gives you procurement-grade questions to ask any vendor - including SLAtech: