A clear account of what we keep.

Request and feedback text

WWJD stores the action and context you submit, and feedback notes, in Cloudflare R2 for 30 days. The text is then deleted. We use it to understand failures and improve WWJD.

Do not submit secrets, passwords, API keys, or personal data. Explain the action and the relevant circumstances without exposing private details.

Metadata

We retain metadata in Cloudflare D1 for analytics and evaluation: request identifiers, verdicts, model and engine versions, token usage, credit charges, timings, and similar operational records. Request text is not stored in D1.

API keys are stored as protected hashes, with a short prefix for support. Rate limiting and key-creation controls use derived IP tags.

Model processing

The action and context are sent to OpenAI to produce the judgment, together with the selected instructions and Scripture. OpenAI may also retain its own abuse-monitoring records for up to 30 days. That retention is separate from WWJD’s 30-day storage.

Release emails and payments

If you join the release list, your email is sent to Klaviyo. Release-list emails are not stored in D1 or R2.

Stripe processes payments and manages subscriptions. WWJD keeps the customer and subscription references needed to connect your plan and credits to your API key.

Examples that help us improve

We may turn an observed failure into an anonymized, rewritten example for our test set. WWJD’s stored raw request text is deleted from R2 after 30 days; an anonymized rewrite is a separate test example.

Request deletion

Email saved@christlab.ai to request deletion or ask about your data. Include a decision ID or your key’s short prefix if it helps identify a request. Never send your full API key.