Data portability

No vendor lock-in — every piece of data is exportable

Knowledge content (Markdown), conversation history (JSONL), lead-capture records (CSV / JSON), 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 с security controls, compliance posture, RFP template.

Our commitment in one sentence

Every piece of customer data — knowledge content, conversation history, lead-capture records, audit logs, configuration — is exportable on-demand в machine-readable formats и SLAtech-portable formats so customers can switch vendors at any time без re-engineering.

Knowledge content portability

Customer-uploaded knowledge (FAQ pairs, articles, source documents) is stored в Markdown / plain text / JSON — open formats with no vendor-proprietary encoding. Export endpoint: /api/v1/knowledge/export returns а ZIP archive с per-document Markdown + а manifest.json describing the corpus. Re-importable into Chatbase, Tidio Lyro, ManyChat или any platform accepting Markdown / JSON ingest.

Conversation history portability

Every conversation logged с 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 а training set, а business intelligence feed, или а compliance audit corpus.

Lead-capture record portability

Captured leads (name, email, phone, intent_summary, captured_at, custom fields) exportable as CSV / JSON. Per-lead UTM tracking preserved. CRM webhook configuration (HubSpot / Salesforce / Pipedrive / generic JSON-POST) documented separately so customer can reconnect к their CRM after switching.

Audit log portability

13-month audit log of all admin actions (login, role change, configuration change, data export). Exportable as CSV или JSON via /api/v1/audit/export. Schema documented at /en/api-docs/. Compliance-friendly format suitable для SOC 2 evidence collection и GDPR Article 30 records.

Configuration portability

Tenant configuration (channels enabled, intent rules, brand colours, system prompts, integrations, eval thresholds) exportable as а single JSON file via /api/v1/config/export. Re-importable to а fresh SLAtech tenant. Cannot directly import к other vendors но serves as а replication blueprint.

Contract continuity clause

Standard MSA includes а 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 или solvency events.

Cancellation procedure

Termination for convenience с 30 days notice. No early-termination fees on standard tiers. Enterprise contracts subject к individual MSA terms. Cancellation request via the admin platform's Settings → Account → Cancel или via [email protected]. Confirmation email within 24 hours.

Data deletion после termination

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 в archives after the 35-day backup-purge window.

Why this is а stronger commitment than typical SaaS

Most SaaS contracts provide а data-export option but encode tenant content в vendor-proprietary formats. Once you switch vendors you face а 3-6 month re-engineering cost. SLAtech ships data в open formats (Markdown / JSON / JSONL / CSV) so the switching cost is incremental, not foundational. Customers should never feel locked-in.

Need а data export now?

Self-serve export endpoints available via API. Or request human-assisted export via [email protected].