Data lifecycle

Last updated: March 09, 2026

Note: If these Terms, Policies, or Agreements are available in multiple languages, and any discrepancies exist between translations, the English version shall prevail.

---

​

1. Data categories covered by retention controls

BabySea applies plan-based retention rules to multiple operational record categories in the current product, including:

• generation records;
• API request logs;
• webhook delivery logs;
• account activity records; and
• credit-ledger records.

Output-file retention is also plan-aware and is handled separately from the log-retention categories. The credit system and ledger events are described further in Billing and credit.

​

2. Current plan-based retention windows

The current self-serve retention configuration is: These windows describe the current product behavior and may change over time.

​

3. Output-file retention

Generated output files are retained according to the plan-based windows in Section 2. Customers should not treat BabySea as permanent storage for generated media unless BabySea separately agrees to that in writing. Customers are responsible for downloading or archiving outputs they need to keep beyond their plan’s retention window. BabySea may delete expired output files without additional notice.

​

4. Data export

BabySea currently provides a user-level export control in My Profile through the Download my data action. In the current product, that export is designed to include user-attributed personal data such as consent records, API keys without raw secrets, API usage logs, webhooks, webhook delivery logs, bug reports, and activity records directly attributable to the requesting user. Shared team records that are not attributable to one specific user may not appear in the same personal export. The My Profile area and its role in the account model are described further in Account and workspace.

​

5. Deletion and account closure

Customers may request or trigger account deletion through the current product flows where available. Deletion may remove access to associated dashboard data, API credentials, domains, and stored outputs subject to BabySea’s operational cleanup schedule and legal-retention requirements. Certain records may be retained for audit, security, fraud prevention, billing, or legal compliance purposes even after account closure when BabySea is legally permitted or required to do so.

​

6. Customer responsibility for backups

Customers are responsible for retaining their own operational records, exports, generated outputs, webhook receipts, and billing evidence if they need them beyond the service’s current retention windows.

​

7. Changes to retention behavior

BabySea may adjust retention periods, archive flows, and deletion processes over time. If BabySea separately agrees to custom retention or compliance requirements with an enterprise customer in writing, that written agreement will control for that customer.