How your conversations are handled
When AI is involved, relevant content is sent to OpenAI
IdentityOS uses OpenAI to build your reflection, generate your character options, and run rehearsal conversations. Whatever that specific step actually needs — your selected statements, your onboarding context, the current conversation — is sent to OpenAI to produce the response. We send only what a given step needs, not your whole account history indiscriminately: for example, your desired identity is deliberately withheld from the call that reflects your current patterns back to you, because it isn’t evidence for that.
OpenAI model-training settings
IdentityOS uses OpenAI's API, not a public AI chat account. At our last documented account check in August 2026, we had not opted in to use API requests for model training. OpenAI's standard API terms allow temporary retention for safety and abuse checks (up to 30 days under the terms checked then). Processing, training, and retention are different things. Provider terms and account settings can change, so these past checks are not a promise about every future request.
Conversation history is stored for continuity
IdentityOS stores the messages you exchange with your mentor. They are part of your conversation history. They stay saved even if you delete long-term mentor memory. When memory is on, your mentor may also use important details from earlier conversations. With memory off, it cannot use long-term mentor memory to build on those talks. You cannot yet delete one transcript by itself. You can remove conversation history by deleting your account.
Mentor memory starts on and works in the background
Long-term mentor memory is a standard part of IdentityOS for new members. We do not ask you to switch it on again before your first conversation.
While memory is on, background workers can process eligible saved conversations. One takes out useful details, another updates the mentor's long-term understanding, and another looks for real examples of confirmed Discovery patterns. These checks may happen after you leave the conversation. They work only with the account's allowed records.
Factual conversation history adds two AI steps. When a conversation ends, it is sent to OpenAI to write a short factual summary. While you talk, what you have said so far and your own earlier summaries may be sent to OpenAI to see whether this is the same situation as an earlier one. Your mentor asks you before treating them as the same, and conversations are linked only if you confirm.
You can delete mentor memory without deleting your chats
In Account, choose Delete saved mentor memory. After you confirm, long-term memory turns off and the stored memory records, summaries, factual conversation summaries, situation links and your confirmation answers, related search data, and My Discovery Results are removed from the live product. Your transcripts and original Discovery stay saved. Separately saved goal-related Case Files are not removed by this action.
Without long-term memory, the mentor cannot use those stored notes and advanced features like My Discovery Results will stop. You can turn memory on again later. That starts new long-term memory, but it does not restore what you deleted. This does not cancel your membership.
Deleting memory from the live service does not immediately erase temporary provider backups or copies already sent for AI processing. Those follow the provider's own retention rules. Deleting your full account is a different, broader action.
Other members can never see your data
Every table that holds your information is protected by database-level row security tied to your own signed-in account. Another member’s app session simply cannot query your rows — this isn’t a setting that could be toggled off by mistake in the product; it’s enforced by the database itself on every request.
Authorized backend operators can technically access stored data
IdentityOS runs on a hosted database (Supabase) and hosting platform (Vercel). The small number of people who operate IdentityOS and hold the credentials for those systems can, like any operator of a hosted service, technically access what’s stored there — this is true of the database directly, not just through IdentityOS’s own admin tools. We’re stating this plainly rather than implying otherwise: “private from other members” is a real, enforced guarantee; “private from everyone who could ever run the service” is not a claim any hosted product can honestly make.
Application logs don’t contain your content
IdentityOS is designed to record operational events such as whether a worker ran and whether a request succeeded, rather than save your conversation text in its application logs. Providers may also keep their own service and security records. We do not use runtime logs as a separate copy of your mentor memory.
Deleting your account, and what temporary copies may remain
Deleting your account (from your account page) removes your account and linked personal records from the live product. It does not reach copies already held in provider backups or AI processing systems. At our last recorded provider review in August 2026, Supabase kept daily backups for seven days, and OpenAI used its standard API retention terms. Those were point-in-time findings, not guaranteed current settings. Such copies may remain until the provider's retention period ends. IdentityOS does not use them as live memory.
At the same August 2026 review, Vercel runtime logs were available for about one hour, with no extra log export configured. Log retention settings may change. These logs are for service operation, not a second member-memory system.
For what’s stored and why, see what we keep & why. You can manage mentor memory or permanently delete your account from your account page.