Data lifecycle

Last updated: May 8, 2026

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

---

BabySea operates as an execution control plane for generative media workloads. This page explains how BabySea handles retention, deletion, export, and lifecycle behavior for account data, generated outputs, operational logs, credit records, webhooks, and derived execution data.

BabySea is not intended to be permanent storage for generated media. Customers are responsible for downloading, archiving, or otherwise preserving any outputs, logs, webhook receipts, or billing records they need beyond the retention windows described below.

1. Data categories covered by retention controls

BabySea applies plan-based retention rules to multiple operational categories, including:

• Output files.
• Generation records.
• API request logs.
• Webhook delivery logs.
• Account activity records.
• Credit ledger records.

BabySea may also maintain derived operational data in analytics, event streaming, routing-intelligence, cache, and monitoring systems. These derived systems are used to operate, secure, observe, and improve the service, but they do not replace Supabase as the regional source of truth.

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 custom retention 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.

When an output file expires, BabySea may retain the related generation record until that record's retention window expires. This allows customers to review generation status, timing, model, provider, cost, or audit metadata even after the file itself has been removed, subject to plan limits.

4. Generation records

Generation records describe the lifecycle of a submitted workload. They may include:

• Generation ID.
• Account ID.
• Model identifier.
• Media type.
• Generation status.
• Provider metadata.
• Timing metadata.
• Credit and cost metadata.
• Error category or failure state.
• Output references where available.

Generation records are retained according to the plan-based windows in Section 2. Once the retention window expires, BabySea may delete or anonymize the record according to operational cleanup processes.

5. API request logs

API request logs help BabySea provide security, debugging, rate limiting, billing support, abuse prevention, and operational observability.

API request logs may include:

• Endpoint and HTTP method.
• Request timestamp.
• Response status code.
• Request duration.
• API key prefix or key metadata.
• Account ID.
• Pseudonymized IP address where implemented.
• User-agent metadata.
• Error category.

Raw API keys are never stored in logs. API request logs are retained according to the plan-based windows in Section 2.

6. Webhook delivery logs

Webhook delivery logs help customers and BabySea debug event delivery. They may include:

• Webhook ID.
• Delivery ID.
• Event type.
• Generation ID.
• Delivery status.
• HTTP response status code.
• Attempt count.
• Error category.
• Delivery timestamp.

Webhook endpoint URLs and decrypted webhook secrets are not intentionally streamed through the realtime event backbone. Webhook signing secrets are encrypted at rest.

Webhook delivery logs are retained according to the plan-based windows in Section 2.

7. Activity records

Activity records describe account-level and operational changes, such as:

• API key creation, update, rotation, or deletion.
• Webhook configuration changes.
• Billing or credit-pack events.
• Team membership changes.
• Domain configuration changes.
• Privacy, consent, or account settings changes.

Activity records are retained according to the plan-based windows in Section 2, unless longer retention is required or permitted for security, fraud prevention, audit, legal, or billing reasons.

8. Credit ledger

The credit ledger records dollar-denominated execution credit movement. It may include:

• Credit additions.
• Credit reservations.
• Credit charges.
• Credit refunds.
• Credit-pack purchases.
• Subscription credit grants.
• Failed-generation refunds.
• Balance-after values.
• Generation references where applicable.

The credit ledger is retained longer than most operational logs because it supports billing reconciliation, customer support, fraud prevention, financial review, and auditability.

Failed generations are refunded automatically through the credit ledger where applicable.

9. Event outbox and event streaming data

BabySea may use a regional transactional event outbox and event streaming infrastructure to process operational events such as:

• Generation lifecycle events.
• Provider attempt events.
• Provider latency observations.
• Credit ledger events.
• Webhook delivery events.
• Webhook dead-letter events.
• Realtime provider-health signals.
• Routing-hint events.
• System observability events.

These events are derived operational records used to improve reliability, observability, replayability, analytics, routing intelligence, and incident response.

BabySea's event streaming design follows these rules:

• Supabase remains the source of truth.
• Event streaming is fail-open and does not block generation, billing, credit, or webhook transactions.
• Replaying events may update derived systems such as analytics tables, dashboards, provider-health aggregates, and routing hints.
• Replaying events must not mutate source-of-truth generation state, double-charge credits, double-refund credits, or re-dispatch customer webhooks unless explicitly part of a controlled recovery workflow.
• Event payloads are designed to avoid unnecessary Personal Data.
• BabySea does not intentionally stream raw prompts, decrypted webhook secrets, raw API keys, customer emails, raw uploaded file URLs, webhook endpoint URLs, or unnecessary personal data through the realtime event backbone.

Event outbox records and event streaming data may have separate operational retention from customer-facing logs. Retention may depend on system configuration, topic retention, connector configuration, analytics retention, cache TTL, and operational requirements.

10. Cache and routing-hint lifecycle

BabySea uses cache and routing-hint systems to support rate limiting, idempotency, concurrency controls, provider rankings, and realtime provider-health hints.

Cached data is generally transient. Examples include:

• Rate limit counters.
• Idempotency keys.
• Concurrency counters.
• Cached provider rankings.
• Circuit breaker state.
• Realtime provider-health hints.
• Short-TTL routing overlays.

Cache entries may expire automatically according to their TTL or be replaced by newer operational data. Cache expiration does not delete the underlying source-of-truth records stored in the regional database.

11. Analytics and derived datasets

BabySea may process operational data into analytics and derived datasets for:

• Provider performance analysis.
• Routing ranking computation.
• Cost and usage reporting.
• Latency and error monitoring.
• Product analytics where consent applies.
• Security and abuse detection.
• Reliability and incident review.
• System optimization.

Derived datasets may be stored in regional analytics or lakehouse systems. They are designed to support BabySea's execution intelligence and operational reliability while minimizing unnecessary Personal Data.

12. Data export

BabySea provides a user-level export control in My profile through the Download my data action where available.

The export is designed to include user-attributed personal data such as:

• Account profile data.
• Consent records.
• Generation history.
• API key metadata without raw secrets.
• API usage logs.
• Webhook metadata and delivery information.
• Billing and credit metadata where attributable.
• Activity records where attributable.

Shared team records that are not attributable to one specific user may not appear in the same personal export. Customers requiring broader account-level export support should contact BabySea through Support.

13. Deletion and account closure

Customers may request or trigger account deletion through available product flows. Deletion may remove access to associated dashboard data, API credentials, webhooks, domains, stored outputs, generation records, and account settings.

Upon account closure, BabySea will delete or disable account-associated data according to operational cleanup processes, subject to:

• Legal obligations.
• Billing and financial record retention.
• Security and fraud-prevention needs.
• Dispute resolution.
• Audit requirements.
• Backup and disaster recovery retention.
• Technical limitations of derived or aggregated systems.

Deletion typically completes within the operational cleanup schedule, generally within 30 days of account closure, subject to the exceptions above.

14. Customer responsibility for backups

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

Customers should not rely on BabySea as the only copy of generated media, webhook receipts, or compliance records.

15. Changes to retention behavior

BabySea may adjust retention periods, archive flows, deletion processes, event streaming retention, analytics retention, and cache TTLs over time.

If BabySea separately agrees to custom retention or compliance requirements with an enterprise customer in writing, those written terms control for that customer to the extent they conflict with this page.

For questions about data lifecycle, deletion, export, or retention, please contact us.