Core: Cloud account suspend, retention, and deletion lifecycle

[ReBoticsAI]

Summary

Define and implement what happens to GodMode Cloud accounts and tenant workspaces when:

• Subscription lapses / payment fails
• Account is suspended for ToS / security
• User requests deletion (email support@godmode.software today; no self-serve flow)

Today paywall and entitlements gate signup/access. There is no clear, automated lifecycle for suspended tenants, retention windows, or hard deletion / export.

Why

Terms of Service need to describe deletion/cleanup honestly. Operator intent: users may email to request deletion; otherwise data may be removed during cleanup. Product needs a real mechanism so Terms are not aspirational.

Scope (proposal)

In

• Document intended states: active → past_due / suspended → deleted (and operator-exempt admins)
• Decide retention before hard delete (or “cleanup without fixed SLA” if that remains policy)
• Implement or stub: suspend access, soft-delete markers, hard-delete tenant workspace + core user rows, audit log
• Support intake for deletion requests (email → staff Support ticket or Admin action)
• Align MarketingTerms / Privacy / Refund copy with shipped behavior

Out (unless justified)

• Full GDPR tooling suite
• Self-serve “delete my account” UI (can be follow-up)
• Marketplace seller payout legal entity changes

Acceptance criteria

• Written policy: what we promise in Terms vs what code does
• Admin (or scripted) path to suspend and to fulfill deletion requests
• Tenant data hard-delete or documented retention + job
• Tests or runbook for cleanup
• Marketing Terms/Privacy updated to match

Notes

Backlog behind launch P0 / dogfood unless Terms launch requires a minimum “request deletion via support” ops runbook only.