No query history by design
The app should not keep a searchable archive of the questions you ask or the answers you receive.
Find & Explain privacy
A question should not automatically become a permanent profile.
Find & Explain is designed as a privacy capsule: a place to ask, search, understand, and end the session. The product is built around no persistent query history, no content logging, no normal account profile for the core experience, and clear session controls.
This page describes the intended privacy model for the app. Some operational details may change before public release, but the product direction is simple: keep the useful parts of search and explanation while reducing unnecessary identity links and stored content.
Privacy approach
The app is designed around temporary use, not long-term memory.
No content logs
Routine server logs should not include the text of your Find or Explain requests, generated answers, or search-result content.
No identity-first account
The account is for access, credits, purchases, and optional recovery. It is not meant to become an identity profile, personalization profile, or content history for your questions and answers.
Session wipe
Ending a session clears temporary local state. Saved local history, if you turned History Mode on, is managed separately from the See history page.
What is used to provide the feature
Privacy does not mean nothing is processed. It means processing should be limited and understandable.
When you use Find, the app sends your query to the Personal.Live backend, and the backend requests search results from a search provider. The goal is that the provider sees the project server request, not your browser cookies, search account, or normal browsing profile. The app shows source cards and copyable links instead of embedding a browser.
When you use Explain, the app sends your question to the backend so an AI model can produce an answer. You can use the cloud model or the local/private model mode in the app. Cloud mode sends the request through the Personal.Live backend to a cloud AI provider, which may apply its own safety and content policies. Local/private model mode uses a Personal.Live-controlled local model path instead of the cloud provider.
Access and credits require a minimal account record, wallet balance, purchase references, optional recovery data, and quota counters. These are used to unlock access, process prepaid credits, prevent basic abuse, and keep the service sustainable — not to build a content profile from your questions.
What we aim not to store
The strongest privacy feature is often the data that never becomes a database record.
Question text
Your Find and Explain request text should not be stored as history or routine logs.
Answer history
Answers are meant for the current session, not a long-term chat archive. Optional History Mode saves only to the local device when you turn it on.
Browsing identity
Find results should not rely on your normal browser cookies, logged-in search account, or browser history.
Raw purchase data
Payments use store or RevenueCat flows. The backend keeps minimal purchase references and credit ledger records, not raw receipts in the client-visible app state.
Device fingerprint
The product direction avoids building access around persistent device fingerprinting.
Manual content review
Support should not read your questions by default. Only information you deliberately send to support is visible to staff.
Permanent sessions
Session state should be short-lived and cleared when the user ends the session.
Honest boundaries
No app can make every network, device, or provider risk disappear.
Find & Explain is not a VPN, not a legal or medical professional, and not a guarantee that a compromised device or monitored network is safe. The app can reduce unnecessary history and identity links inside its own flow, but it cannot control everything outside the app, such as screenshots, keyboard software, operating-system telemetry, or the behavior of websites opened outside the app after you copy or open a link.
For highly sensitive situations, users should avoid including unnecessary personal details and should seek qualified professional help when needed. The app is for understanding and exploration, not for emergency advice or final professional decisions.