Your context. Your controls.

Prajna stores your account, consultations and Board responses; scratchpad entries you explicitly submit; and one approved Board Read containing the context you want carried across consultations. Every proposed Board Read update is shown in full before you save it.

The Board uses your consultation history and approved Board Read to advise you. Prajna does not take an external business action on your behalf without explicit approval. It does not sell your data or train a Prajna-owned model on your content.

One authorized operator can inspect account state, consultation content and product activity when needed to operate the beta, investigate a support request, or recover a failed turn. The operator console is access-controlled and backed by an audit history.

Google provides sign-in. Vercel serves the website. Neon stores durable product data. OpenAI Codex processes Board requests through the operator account. Langfuse receives content-redacted operational telemetry. When specialist web research is available and commissioned, Exa or Linkup may process a bounded research query.

Whether OpenAI may use model inputs to improve its services depends on the controls and plan attached to the operator account. That setting has not been independently verified for this disclosure. During the beta, do not enter highly sensitive personal, legal, medical, financial or trade-secret information.

Consultations, scratchpad entries and your Board Read remain until you delete them. Privacy-safe product events record that an action occurred, never the decision or scratchpad text, and expire after 90 days.

From Settings and data you can download a JSON export, delete one consultation or scratchpad entry, clear your Board Read and scratchpad while keeping consultation history, or delete your account and associated data. Every deletion returns a receipt describing what was removed.

Your export contains your product data. It excludes system prompts, internal tool traces and specialist working notes because they are runtime implementation records rather than customer-authored content.

Signed-in account holders can send a report from Settings. If you cannot sign in, follow the instructions in your invitation or visit Report a problem.