Private sessions and Challenge content
Your private browser session is valid for up to seven days after it is created. Access can end earlier if the session cookie is lost or cleared. Each saved Challenge expires seven days after that Challenge is created; follow-ups do not extend its expiry. Session expiry can end access to a Challenge sooner. Export anything you wish to keep while you still have access.
Expired session identifiers and expired Challenge records are removed by scheduled hourly cleanup. Session-owned request/retry records are removed after their session has been cleaned up. Deletion is scheduled after expiry, not promised at an exact instant. Infrastructure backups may persist longer.
History and exports are private to the browser session that created the Challenge. This is not an email/password account or cross-device history login. Use History to export or delete an accessible Challenge. Cancellation alone does not delete history; the same expiry rules still apply.
Purchase accounts, recovery and allowances
A purchase account uses an identifier and a hashed private recovery code. Purchase-account links, entitlement records and recovery information are kept separately from private Challenge content; they are not deleted by the seven-day session cleanup.
Unused purchased Challenge Pack credits have no seven-day expiry. Refunds, disputes and use can adjust the associated allowance. Pro allowance belongs to its paid billing period, expires at the period end, and does not roll over.
A recovery code restores your purchase balance in a new browser session. It does not restore another session’s private decisions or expired history, and does not grant another free Challenge. Keep it private.
Payment and operational records
Payment references, purchase amounts/statuses, subscriptions, entitlement consumption and non-sensitive AI usage/cost records are retained separately for purchase recovery, billing reconciliation, security and operational audit. No fixed automatic deletion period is configured for these records; the seven-day private-content expiry does not apply to them.
Card details are entered on Stripe-hosted Checkout, not in Devil’s Advocate’s forms. Stripe processes payment and customer details under its own policies. Contact support about payment or privacy requests; do not send card details, private recovery codes or decision narratives.
AI processing and limits
When you submit a Challenge, its material text and context are sent to OpenAI for processing. Generation uses store:false. Input-token preflight also sends that request context to the same provider for counting; it creates no model response. Provider abuse-monitoring and infrastructure retention may still apply. store:false does not establish zero retention.
Ordinary application analytics omit raw private narratives. No submission or report is public by default. You control downloaded exports. Avoid confidential information and identifying details about yourself or others.
AI criticism is not external verification, professional approval or a diagnosis. Knowledge principles may be research drafts and are not claimed to be expert validated. Threats, violence and coercion interrupt adversarial analysis; safety is not an upsell.
