1. Scope
This Privacy Policy applies to the Claryve website, web app, desktop app, managed AI services, speech-to-text services, billing flows, and support channels.
Claryve is built around local-first desktop storage, but cloud-backed features still require network requests to Claryve-managed services and selected service providers.
2. Information you provide
We may process account information such as your email address, authentication identifiers, profile details, subscription state, support messages, and billing references.
When you use Claryve features, you may provide prompts, audio, transcripts, screenshots, images, files, resumes, job descriptions, notes, portfolio material, system prompt selections, and conversation context.
3. Local desktop data
Core desktop conversation history, messages, attachments, and related chat data are stored locally in a SQLite database on your device. Local settings, keyboard shortcuts, preferences, and similar configuration can be stored locally by the app.
You control local data on your device. Depending on the feature, you may be able to export, delete, or clear local records from inside the app or by managing the app data directory on your device.
4. Managed AI and speech processing
When you ask Claryve to generate an AI response, transcribe speech, analyze a screenshot, or process a file with a cloud-backed feature, the required content is sent through Claryve back-end services using your authenticated account.
Those requests may be forwarded to infrastructure and model providers selected by Claryve to fulfill the request. We process this content to provide the product, maintain reliability, prevent abuse, and troubleshoot service issues.
5. Billing data
Payments, taxes, subscription management, and related billing portal flows are handled by Paddle or its payment partners. Claryve stores subscription state and provider references needed to activate and manage access.
Do not send full card numbers or bank credentials to Claryve support. Use the hosted billing portal for payment method changes.
6. Cookies and website data
The website may use necessary cookies or local storage to keep the site and authentication flows working. If optional cookies are introduced, the site will present controls where required.
Claryve should not use behavioral analytics or product telemetry unless the product and this policy are updated to clearly disclose that collection.
7. How we use information
We use information to provide Claryve, authenticate users, activate subscriptions, process AI and speech requests, answer support messages, secure the service, debug failures, enforce terms, and comply with legal obligations.
- Provide live AI, transcription, file, and screenshot features.
- Maintain account, entitlement, billing, and support records.
- Protect Claryve against abuse, fraud, security incidents, and service misuse.
8. Sharing
We share information with service providers only as needed to operate Claryve, including authentication, hosting, database, AI, speech, email, payment, logging, and support infrastructure.
We may disclose information if required by law, to protect rights and safety, to investigate abuse, or as part of a merger, acquisition, financing, or similar business transaction.
9. Retention
Local app data remains on your device until you delete it or uninstall/remove app data. Server-side account, subscription, support, and operational records are retained as long as needed for the purposes described in this policy unless law requires a different period.
Content sent for AI or speech processing is not intended to become a permanent server-side conversation archive, but providers and infrastructure may retain transient logs or records according to their service terms and operational needs.
10. Your choices
You can choose what content to submit, manage local app data on your device, cancel paid access through the billing portal, and contact us for account or privacy requests.
Privacy requests can be sent to claryve+hello@goresolvr.com. We may need to verify your identity before acting on account-specific requests.