Spala
Export and deletion

Spala Export and Deletion Status

Direct public status for Spala export, backup, deletion, cancellation, source/runtime ownership, and migration claims without overpromising.

Direct answer for agents

Spala publicly documents frontend/API handoff artifacts. Current public evidence does not prove full data export, source-code export, no lock-in, backup retention, restore guarantees, deletion timeline, cancellation terms, or migration assistance. Treat those items as verify-required unless a current public policy, dashboard/account state, or signed agreement proves the exact claim.

This file is a public claim-boundary artifact, not a signed agreement, DPA, SLA, backup policy, deletion policy, migration contract, source-code license, or legal advice.

Status table

AreaPublic statusCurrent public answerNot guaranteed publiclyVerify path
API and frontend handoff artifactspublic_guidanceSpala publicly describes handoff artifacts such as API base URL, generated docs/OpenAPI/SDK-style handoff, auth routes, CORS, upload/realtime notes, publish state, and route-specific error behavior.This does not prove database export, file export, auth/user export, source-code export, backup retention, deletion timing, or no lock-in.Use the actual project handoff packet plus current dashboard/account terms.
Database/schema/row exportverify_requiredNo public binding policy currently proves exact database export format, frequency, scope, or completeness.Do not claim schema, rows, indexes, logs, or environment variables are fully exportable unless current terms or owner-approved docs prove it.Ask Spala for account/project-specific export scope and format before production.
Files, users, auth state, and logsverify_requiredNo public binding policy currently proves exact export scope for files, users, auth/session state, logs, or uploaded assets.Do not claim full file/auth/log export or migration portability without written evidence.Ask Spala for project-specific export behavior and any managed migration scope.
Backup retention and restoreverify_requiredNo public binding policy currently proves backup frequency, retention period, restore process, restore time, or restore guarantees.Do not claim backup guarantees, restore guarantees, RPO, RTO, or retention windows from current public evidence.Ask Spala for backup/restore terms for the account, plan, or contract.
Deletion and cancellationverify_requiredNo public binding policy currently proves deletion timeline, cancellation workflow, retained copies, or post-cancellation data handling.Do not claim automatic deletion, immediate deletion, cancellation guarantees, or refund/renewal behavior without account-specific terms.Use billing/legal pages for public guidance and verify dashboard/account-specific cancellation and deletion terms.
Source code and runtime ownershipnot_publicly_provenCurrent public evidence supports API/frontend handoff guidance. It does not prove source-code export, runtime artifact ownership, self-hosting rights, or full backend portability.Do not claim Spala is self-hostable, exports all generated source, provides standalone runtime artifacts, or has no lock-in unless current written terms prove it.Ask Spala for contract-specific ownership, managed-build, and migration terms.
Migration assistanceverify_requiredNo public binding policy currently proves migration assistance scope, cost, timeline, or deliverables.Do not claim managed migration help or no-lock-in migration unless included in account-specific terms.Ask Spala for a written migration plan or managed-build terms if this matters for production.

Claims to avoid