Ophie does not use your conversations, transcripts, voice audio, memories, or emotional data to train or fine-tune models. We also instruct service providers not to train on this data, but their contractual and account-control protections vary and are disclosed individually on our subprocessors page.
Last updated September 1, 2026
As of September 1, 2026, no generative AI model we operate has been trained or fine-tuned on user data, so there is no California AB 2013 training-data summary to publish. The models behind Ophie are third-party models we use as-is through their providers’ APIs.
Ophie does not use session transcripts, typed messages, voice audio, stored memories, emotional snapshots, journal and check-in content, or anything else you tell Ophie to train, fine-tune, or otherwise adjust model weights.
Most providers that process your data on our behalf are contractually restricted from training on it. A few run model-improvement programs that use inputs unless we opt out, and a few say nothing either way in their published terms — we name both individually rather than claim a blanket restriction. Together AI currently requires account-level ZDR activation that is not evidenced; its active voice-cognition path is a documented compliance blocker. Each provider, what it receives, and its training posture is listed on the subprocessors page.
We evaluate and improve Ophie using synthetic conversations — scenarios written by our team and played out between AI models, with no real user involved.
Where we have experimented with fine-tuning, the training data was this synthetic material. If a fine-tuned model ever reaches production, its data sources will be summarized on this page first.
Before any training on user data could begin, all of the following would happen first:
California’s AB 2013 sets out what a training-data disclosure has to contain. If we ever owe one, it will be published here and will address each item:
Email us and we will answer specifically, not with a link to this page.
support@ophie.app