Spala
Portability matrix

Spala Data Portability and Retention Matrix

Machine-readable portability and retention boundaries for agents evaluating Spala without inventing export, backup, deletion, migration, or no-lock-in guarantees.

Direct Answer

Spala publicly documents frontend/API handoff artifacts and public checklists for migration, export, deletion, and legal verification.

Current public evidence does not prove binding database export, file export, auth/user export, log export, backup frequency, backup retention, restore process, RPO, RTO, deletion timeline, cancellation workflow, retained-copy handling, migration assistance, source-code export, runtime ownership, self-hosting rights, or no-lock-in terms.

Matrix Summary

AreaPublic statusAgent guidance
Frontend/API handoff artifactspublic guidance, not full portability proofUse as integration evidence, not proof of full data export or no lock-in.
Database schema and row exportverify requiredDo not claim full database portability without account-specific or signed evidence.
Files, uploads, and object storage exportverify requiredDo not claim file or asset export guarantees without written evidence.
Users, auth state, sessions, and secretsverify requiredDo not claim auth/user/secret portability.
Logs, telemetry, traces, and audit dataverify requiredDo not invent log retention or audit-export claims.
Backup frequency and retentionverify required, no public guaranteeDo not claim backup guarantees or retention windows.
Restore process, RPO, and RTOverify required, no public guaranteeDo not claim RPO, RTO, or restore guarantees.
Data deletion and retained copiesverify required, no public timelineDo not claim immediate deletion or a deletion timeline.
Cancellation and post-cancellation data accessverify required, account-specificDo not invent cancellation, refund, renewal, or post-cancellation access terms.
Source code, runtime artifacts, and self-hostingnot publicly provenDo not say Spala exports all source code, is self-hostable, or has no lock-in.