Privacy policy
Effective date:
Who we are and what this covers
Morf operates trymorf.com and the Morf desktop application. This policy covers information processed to provide our website, accounts, subscriptions, support, and desktop features. Contact support@trymorf.com with privacy questions or requests.
Account, device, and billing information
- Account information: your name, email address, optional profile image, account timestamps, and a password hash if you use a password. If you choose an available third-party sign-in option, we receive the identity and profile information needed to sign you in.
- Sign-in and device information: session records, device names, app versions, session activity and revocation timestamps, and hashed desktop access tokens.
- Billing information: Paddle customer and subscription identifiers, purchased plan items, subscription status, billing-period dates, and payment-event records. Paddle collects payment details; our application does not receive or store your full card number.
- Support information: messages and any attachments you choose to send us.
- Technical information: IP addresses, request and error information, browser or device information, and approximate country used for security, service operation, and local pricing.
Projects, AI, and connected accounts
Projects are normally stored on your computer and in accounts you control. Working locally does not mean every feature stays offline. Prompts, relevant files, code, selected images, and other task context may be sent to the AI provider or service involved in your request. For example, Claude Code and Codex process information under their providers' terms and privacy policies, and conversational features can use Cerebras.
When you connect services such as GitHub, Fly.io, Neon, or PostHog, Morf uses the permissions you grant to read information or perform your requested work. These services process information under their own policies. Integration credentials are stored locally using the operating system's secure-storage facilities and are used to authenticate the relevant requests.
Only provide content you are authorized to share. Review the permissions and privacy settings of connected providers, including their retention and AI-training settings.
Voice, screen, and camera features
Features using your microphone, camera, or screen require the relevant device permissions. Voice services can send recorded audio for transcription and response text for speech generation. ElevenLabs is used for Morf's online voice; other configured transcription providers can include OpenAI or Deepgram. Local transcription paths are also available in supported configurations.
Screen questions and visual tasks can include captured screen content in the context sent to an AI provider. Camera-based hand controls process frames locally for gesture detection. Other camera or visual features may send the content you provide to their configured provider. Avoid capturing sensitive information you do not intend to share. You can revoke device permissions through macOS settings.
Desktop analytics, diagnostics, and local history
Desktop usage analytics are enabled by default and can be disabled in Settings → Privacy. When configured, PostHog receives a random installation identifier, app version, platform, architecture, release channel, and limited feature and build events. These analytics events do not contain your prompts, source code, project names, or account profile fields. The installation identifier means this information is not treated as fully anonymous.
Crash reporting is off by default. Crash dumps may be stored locally; uploading them requires both the crash-reporting setting and a configured reporting service. Diagnostic reports can contain technical details about a failure.
The optional local typed-instruction log is off by default, excludes voice text, and applies redaction and storage limits. Displayed and exported history is limited to the most recent 90 days. New log writes prune older entries and cap the saved log at 5,000 entries or 1 MB; an inactive log can remain on disk until cleared. Clearing local data removes the categories identified in the app; it does not delete your online account, project files, saved integration credentials, or all settings.
Cookies and browser storage
We use cookies for sign-in, session security, and authentication flows. Browser session storage can remember the plan you selected while you sign in. Paddle checkout may use its own cookies and similar technologies for payments and fraud prevention. Blocking these can prevent sign-in or checkout from working.
Why we use information
We use information to provide the service you request, authenticate accounts, manage subscriptions, deliver account emails, answer support requests, prevent abuse, investigate failures, and improve product reliability. Where data-protection law requires a legal basis, we rely on performing our agreement with you, legitimate interests in operating and securing the service, compliance with legal obligations, or consent where required. You may withdraw consent for optional processing without affecting earlier lawful processing.
Providers and other disclosures
Service providers process information needed for their role: Railway for website and database hosting, Paddle for payments, Resend or Hostinger for configured email delivery, and PostHog for configured desktop analytics. AI, voice, sign-in, and connected-service providers receive information when you use the relevant features. Paddle's Privacy Notice describes its handling of buyer information.
We may disclose information to comply with legal obligations, protect people or systems, investigate abuse, or handle a business transfer with appropriate protections. We do not sell your personal information or use it for targeted advertising.
Storage, retention, and security
We retain account and service records for as long as needed to provide the service and to meet legal, accounting, security, or dispute-resolution needs. Retention depends on the record and purpose; backups and records we must legally keep may remain after an account request. Providers apply their own retention rules to information they control. Files in your local projects and connected accounts remain under your control.
Providers may process information in countries other than yours. Where required, applicable data-transfer safeguards govern those transfers. We use access controls, protected credentials, password hashing, and encrypted network connections, but no system can guarantee absolute security.
Your choices and rights
You can sign out, disable desktop analytics, and revoke connected-service or device permissions. To request access, correction, deletion, or a copy of personal information, email support@trymorf.com. We may need to verify your identity. Account deletion is a support request, not the same as clearing local data or canceling billing.
Depending on your location, you may also have rights to restrict or object to processing, withdraw consent, or complain to your data-protection authority. We handle requests under the law that applies to you, including any required response period and exceptions.
Children and policy updates
Morf is intended for people able to enter the service agreement and is not directed to children. Contact us if you believe a child has provided personal information without appropriate authorization.
We will post policy updates here with their effective date and provide additional notice of material changes where required.
Contact
Questions go to support@trymorf.com.