Practical guide
How Bulk Image Generator Stores Prompts and Images
Understand today’s database-disabled bootstrap mode and the planned private object-storage, database, session, retention, export, and deletion lifecycle.
The central idea
Privacy guidance must describe production reality, not a target diagram. In the current bootstrap release, provider generation and database-backed session, workspace, asset-metadata, billing, and lead features are disabled. Any future Neon and private R2 lifecycle must be documented only after its bindings, policies, retention rules, and deletion behavior are verified in production.
A repeatable workflow
Follow the request
Explain what the browser sends, which Worker receives it, which provider processes it, and what returns.
Map durable storage
Identify database records, private asset objects, session identifiers, logs, analytics, billing, and optional integrations.
Explain control
Show access boundaries, retention, download/export, account deletion, processor requests, and disabled-feature behavior.
Verify every release
Block publication when production bindings, providers, policies, or feature flags no longer match the explanation.
Worked example
In bootstrap mode, health reports the database as not configured, persistent endpoints return a structured service-unavailable response, and generation never calls a provider. After Neon and generation are enabled, this page can add a verified diagram tracing the frontend Worker, service-bound API Worker, provider, private R2 asset, and Neon metadata.
Review checklist
- The diagram matches production
- Optional and essential processing differ
- Retention and deletion are explicit
- Legal policy remains authoritative
Limitations
- Do not publish the planned Neon flow before it is deployed
- Security-sensitive implementation details may need careful abstraction