Privacy Policy
1. Overview
Find & Explain is a privacy-first search and explanation app for sensitive questions. It helps users find public web results, receive a plain-language AI explanation, and wipe the current session when finished.
This Privacy Policy explains what data we use, what we store, what we avoid storing, how credits and purchases work, how local history works, and how users can manage or delete data.
Find & Explain is not a VPN, not a browser, not an anonymity tool, and not a substitute for professional medical, legal, financial, or emergency advice.
2. Who this policy applies to
This Privacy Policy applies to users of the Find & Explain app, website, and related services provided under the Personal.Live brand.
3. Data we use
We use limited data to operate the app and provide its core functionality.
This may include:
- account access data such as username, password authentication data handled by the authentication provider, optional recovery email, and internal user identifier;
- credit balance, free trial counters, purchase status, product identifiers, and safe transaction references;
- app settings such as interface language and selected model mode;
- temporary question text, search source metadata, and explanation content while a request is being processed;
- optional local history stored only on the user’s device when History Mode is turned on;
- limited technical metadata needed to operate, secure, debug, and protect the service, without routine content logging.
4. Account data
Find & Explain uses a minimal account model for access, credits, purchases, and optional recovery. The account is not intended to be an identity profile or a content archive.
This may include:
- username or internal account identifier;
- optional recovery email if the user chooses to add it;
- authentication provider user ID;
- account creation and update timestamps;
- minimal account state required for access, credits, purchases, and recovery.
We do not display the user’s password inside the app. Password handling is performed through the authentication system.
5. Credits, free trial, and purchases
Find & Explain uses prepaid credits rather than a time-based subscription model.
The app may store and process:
- free trial counters such as free credits and free Find limits;
- paid credit balance;
- credit ledger entries;
- product IDs for purchased credit packs;
- safe purchase or transaction references used for verification and idempotency;
- refund, cancellation, or reversal metadata where applicable.
Purchases may be processed through platform stores, RevenueCat, Stripe, Apple, Google, or other payment providers depending on platform and product availability. Payment providers may process payment information under their own privacy policies. We do not intentionally store full payment card details.
The backend wallet is the source of truth for credit balance. Store or RevenueCat purchase state is used as input for backend verification and credit granting, not as the final in-app balance by itself.
6. Settings and preferences
We may store or use limited settings and preferences to operate the app and remember user choices.
This may include:
- interface language;
- selected model mode, such as cloud model or local/private model where available;
- local History Mode state and local history records on the device;
- safe feature flags and availability state;
- basic account recovery preferences.
7. Question, search, and explanation content
7.1 No server-side history by default
The app is designed not to keep a server-side history of the questions you ask, the web results you receive, or the AI answers generated for you.
When you make a request, the content is processed to provide the requested Find, Explain, or Find + Explain result. The product direction is to avoid turning that content into a long-term server-side archive.
7.2 Request processing
For Find, your question is sent to the Personal.Live backend, and the backend requests search results from a search provider. The goal is for the search provider to receive a request from the project backend rather than from your browser cookies, personal search account, or normal browsing profile.
For Explain, your question is processed by an AI model through the backend. Depending on selected mode and availability, this may use a cloud AI provider or a local/private model mode.
For Find + Explain, the backend may send cleaned source metadata, such as title, snippet, source domain, and link, to the AI model so it can produce a source-grounded explanation.
7.3 Provider policies
Cloud AI providers may apply their own safety, abuse, or content policies. This means some requests or outputs may be limited, refused, filtered, or changed according to the provider’s rules. Local/private model modes may have different behavior and availability.
8. Optional local history
History Mode is off by default.
If the user turns History Mode on, the app may store local history on the user’s own device or browser. This local history may include the question, action type, visible explanation, and visible source cards shown to the user.
Local history is not synced to the backend as an account history. The backend does not read local history. The user can manage and delete local history from the See history page in the app.
When deleting the account from within the app, the app first clears local history on that device and then requests account deletion from the backend. Local history on other devices or browsers, if any, must be managed on those devices.
9. What we do not store, or do not store by default
We aim not to store certain categories of data as part of the normal product flow.
This includes:
- server-side query history by default;
- server-side AI answer history by default;
- search-result history linked to the user by default;
- raw user request bodies in routine server logs;
- raw AI prompts in routine server logs;
- generated outputs in routine server logs;
- raw search provider response bodies in routine server logs;
- full billing receipts in client-visible storage;
- device fingerprints used as a primary identity method;
- persistent IP-address identity for ordinary product use.
10. AI-related processing
When you request an AI explanation, the relevant user text, selected model mode, interface language, and necessary context may be sent to the backend and to an AI service provider or Personal.Live-hosted model as needed to generate the requested result.
The service is designed to minimize stored content and avoid unnecessary retention. Internal prompt construction and prompt-protection mechanisms are not exposed to users.
AI-generated answers may be incomplete or incorrect. For medical, legal, financial, employment, immigration, emergency, or similarly high-stakes topics, users should verify information with official sources or qualified professionals.
11. Search-related processing
When you use Find, the backend may request public web search results from a search provider. Returned source metadata may be shown in the app and may be temporarily held in memory to display additional results in the current session.
The app may keep a temporary in-memory batch of results on the user’s device to show additional result pages without immediately requesting the same search provider again. This cache is part of the current session and is cleared or replaced when the session ends, the user signs out, the query changes, or the app clears session state.
The app is not a browser. If the user chooses to copy or open a source link outside the app, the external browser or website may process data under its own policies.
12. Local device storage
The app may store limited data locally on the device or browser for functionality and convenience.
This may include:
- interface language;
- local app preferences;
- temporary session state while the app is open;
- optional local history if History Mode is enabled;
- safe cached state needed to render current results or purchase state.
Where supported by the app, users may clear local data on the device without deleting all backend account or purchase records.
13. Authentication and recovery
Authentication is provided using secure account infrastructure. Users may sign in with the account method supported by the app.
If the user adds an optional recovery email, it is used for access recovery and account-related support. It is not intended to be linked to query content or used to build a content profile.
14. How we use data
We use data to:
- provide the app and its core Find, Explain, Find + Explain, wipe, account, and credit features;
- authenticate users and protect account access;
- maintain credit balance, free trial limits, purchase verification, and abuse controls;
- process search and AI requests requested by the user;
- support optional local history on the user’s device;
- detect errors, abuse, fraud, and service issues without routine content logging;
- comply with legal, tax, billing, and security obligations.
15. Data sharing
We do not sell personal data.
We may share limited data with service providers and processors that help us operate the app, such as:
- authentication providers;
- hosting, database, and cloud infrastructure providers;
- search providers used to return public web results;
- AI model providers used for cloud-mode explanations;
- payment, store, purchase validation, and billing providers;
- security, abuse-prevention, or diagnostics providers, if used.
These providers receive only the data reasonably necessary for their role.
16. International data transfers
Depending on infrastructure, search providers, AI providers, payment providers, and other service providers, data may be processed in countries other than the user’s own country.
Where required, appropriate steps are taken to protect personal data during such transfers.
17. Data retention
We retain data only as long as needed for the purposes described in this Privacy Policy, unless a longer retention period is required by law.
Examples:
- account access data is retained while the account is active;
- credit balance and wallet data are retained while needed to operate credits and purchases;
- limited ledger, purchase, tax, audit, refund, and fraud-prevention records may be retained where legally or operationally required;
- server-side query and answer history is not retained by default;
- local history is retained only on the device or browser until the user deletes it or the app clears it as part of supported flows.
18. User controls
Users may have the ability to:
- change interface language;
- choose model mode where available;
- end session and wipe current app state;
- enable or disable local History Mode;
- view and delete local history entries on the device;
- buy credit packs where purchasing is available;
- sign out;
- delete the account from within the app.
19. Account deletion
If the user deletes the account through the app, the app first attempts to delete local history on that device, then requests backend account deletion.
Backend account deletion may include deleting the authentication user and account records controlled by the app. Certain records may be retained where legally or operationally necessary, such as payment, credit ledger, refund, tax, audit, fraud-prevention, or security records.
Deleting the account does not necessarily erase records held by payment providers, app stores, search providers, AI providers, or other third-party processors. Those providers handle their own records under their own policies.
20. Children
The app is not intended for children under the age required by applicable law for independent use of such services, unless otherwise explicitly stated.
21. Security
Reasonable technical and organizational measures are used to protect personal data, including controls around authentication, transport security, access control, secret handling, and data minimization.
No method of transmission or storage is completely secure, and absolute security cannot be guaranteed.
22. Changes to this Privacy Policy
We may update this Privacy Policy from time to time.
If material changes are made, we may update the in-app policy screen, this page, the effective date, or provide other appropriate notice.
23. Contact
For privacy questions, support requests, or data-related requests, contact:
Website: www.personal.live
Email: findexplain@personal.live