Privacy Policy

• Your chats, files, settings, and your own API keys stay on your device unless you use a feature that needs a network service.
• We do not sell your data, show ads, or use your content to train AI models.
• Google user data is used only to provide the features you ask for in Enconvo, and is handled according to Google's Limited Use requirements (see Google user data).
• You can turn off product analytics at any time in Enconvo Settings.

Your conversation history, chat sessions, plugin settings, knowledge base, and the API keys you enter for AI providers are stored locally on your device. We do not upload them to our servers. When you use your own API key, Enconvo sends your request directly from your device to that provider.

Enconvo asks for system permissions only for the features that need them, and only when you use those features:

• Accessibility. Reads the text you have selected and lets agents operate apps when you ask them to.
• Clipboard. Reads or writes text when you run a command that uses the clipboard. Clipboard History, which is on by default, keeps the text, images, and files you copy on your device for the period you choose (three months by default). It skips password managers and content that apps mark as confidential, and you can turn it off or clear it at any time.
• Microphone. Records audio for dictation, transcription, and voice conversations.
• Screen recording and camera. Captures the screen or camera when you share it with an agent.
• Calendars, reminders, contacts, and automation. Lets agents read and update your Apple apps when you ask them to.
• Location. Shows local weather. Your location is not stored on our servers.

You need an Enconvo account for Enconvo's cloud features, subscriptions, and the iPhone app. When you sign up with an email and password, or with Google Sign-In, we store:

• Profile. Your email address, your name, and your profile picture if you sign in with Google.
• Devices. An identifier derived from your computer's hardware (we store a one-way hash, not the serial number itself), the device model and system version, and the IP address and approximate city of the device when it signs in. We use this to apply your plan to your devices and to prevent abuse.
• Plan and usage. Your plan, your points balance, and a usage record for each cloud request: the model or feature used, the command, token counts, and the points charged. Usage records do not contain your prompts or the responses.
• Email preferences. Whether you want product update emails.

Payments are processed by Stripe. We receive and store the plan you bought, the amount, the currency, the purchase and refund dates, and Stripe's reference identifiers. We never receive or store your full card number.

When you choose one of Enconvo's built-in cloud models, or a cloud feature such as web search, image or video generation, speech recognition, or text-to-speech, your request passes through our servers to the provider that performs it (for example OpenAI, Anthropic, Google, or the other providers listed in the model picker). The request can include your prompt, the files or context you attach, and any data an agent has gathered for the task.

We use this content only to return the result you asked for and, from November 14, 2026, to run the check described below. We do not store prompts or responses in our databases. Our servers keep short-lived operational logs, which can include parts of a request, to diagnose failures and prevent abuse. These logs are deleted automatically after at most 7 days. Providers process your request under their own terms for API customers.

Starting November 14, 2026, before a message reaches an Enconvo Cloud model, we send the text you just wrote to OpenAI's moderation model to check it against our usage policy. If a message is refused or flagged, we keep the account, time, model and scores for up to 90 days, and never the words. Repeated refusals can pause Cloud AI on the account.

So that a provider's safety action applies to one account instead of everyone, we send OpenAI and Anthropic a stable identifier made from your account with each request. It is a one-way hash, not your email address. We delete our record of it with your account; providers keep their own safety records under their terms.

Enconvo can run extensions written by other developers, including Raycast-compatible extensions that you import from Raycast, install from a folder, or install from GitHub. These extensions are third-party code. They run on your device in a sandbox that limits them to their own files and the internet. If you give an extension full access, it can also use your files, run programs, and connect to apps and devices on your network. Extensions can send data to services their developers chose. Their developers, not Enconvo, are responsible for how they handle your data, under their own terms and privacy policies.

• Installing from GitHub. When you choose Install in Enconvo on an extension's page on raycast.com, the Enconvo browser extension passes only the extension's name to the Enconvo app on your device. Enconvo then downloads the extension's source code from the public Raycast extensions repository on GitHub and the packages it needs from the npm registry, and builds it on your device without running any of its scripts. Checking for updates downloads the same way. These requests go from your device directly to GitHub and npm and include the names of the extension and its packages, but not your Enconvo account or your files. GitHub and npm handle them under their own privacy policies.
• Removal checks. About twice a day, Enconvo checks the public Raycast extensions repository on GitHub to see whether the extensions you imported from Raycast or installed from GitHub are still listed there. These requests go from your device directly to GitHub and include the names of those extensions, but not your Enconvo account or your files. GitHub handles them under its own privacy policy. Enconvo does not contact Raycast's servers, and does not check extensions you installed from a folder.
• Safeguards. Enconvo asks you to confirm before it imports or installs an extension. An extension must ask before it uses AI, reads your clipboard history, or runs with full access, and you can change these choices under Permissions in Raycast-compatible Extensions. Enconvo turns off extensions that are removed from the public Raycast extensions repository.
• AI requests. When you allow an extension to use AI, its prompts go to the AI model chosen in Enconvo's settings and are handled as described in Enconvo cloud models and services, or by your own provider if you use your own API key.
• Analytics. Product analytics record actions such as installing or running an extension and the permission choices you make, but never the names of your extensions or what they do.

Raycast is a trademark of Raycast Technologies Ltd. Enconvo is not affiliated with, endorsed by, or sponsored by Raycast.

• Connection to your computer. When the iPhone app controls Enconvo on your computer, the connection passes through our relay server end-to-end encrypted. The relay can see only routing information, not the content.
• Phone chats. Chats you have in the iPhone app itself, their attachments, and your personal instructions are synced through Enconvo's servers so they are available on your devices. They are encrypted at rest but not end-to-end encrypted. You can delete them in the app, or by deleting your account.
• Notifications. We store your iPhone's push notification token to deliver notifications from your computer.
• API keys. Any provider API keys you enter in the iPhone app are kept in the iOS Keychain on your phone.

Enconvo accesses Google user data only when you choose to connect a Google account.

• Google Sign-In. We receive your name, email address, and profile picture to create and identify your Enconvo account.
• Gmail. If you connect Gmail, Enconvo can read, search, and organize your messages and labels, create drafts, and send email on your behalf, but only when you or an agent you are using asks it to.
• Google Calendar. If you connect Google Calendar, Enconvo can read your calendars and events, find free time, and create, change, or delete events on your behalf, but only when you or an agent you are using asks it to.

How we use it. We use Google user data only to provide the features you use in Enconvo. For example, we show your emails to you, summarize them, draft replies, or send a message you asked an agent to send, or add an event you asked for. We do not use it for advertising, and we do not use it to create, train, or improve any AI or machine learning model.

Where it goes and where it is stored. Gmail and Google Calendar connections currently run through Composio, a service provider that holds the Google authorization for your Enconvo account. Composio knows your account only by an anonymous account id, not by your email address. Each request goes from your device through our servers to Composio and on to Google, and the result comes back the same way. Our servers pass it through without storing its content. Composio does not store the content either; it keeps a record of which action ran, when, and whether it worked. We do not copy your email or events to our servers. If you set up the older Gmail plugin in an earlier version of Enconvo, its requests go directly from your device to Google, and its authorization token is kept encrypted on your device. Messages and events an agent reads may be saved in your local chat history on your device, and you can delete that history at any time.

Who we share it with. When a task needs email or calendar content, Enconvo includes only the content that task needs in the request to the AI model you selected. If you use one of Enconvo's built-in cloud models, that request passes through our servers as described above. We do not sell Google user data or share it with advertising platforms, data brokers, or information resellers. Apart from Composio, which runs your Gmail and Google Calendar requests as described above, we share it with others only when you ask us to, when it is needed for security, or when the law requires it.

Human access. No person at Enconvo reads your Google user data unless you give us explicit permission for a specific message (for example, in a support request), it is needed to investigate abuse or a security incident, or the law requires it.

Removing access. You can disconnect Gmail or Google Calendar in Enconvo at any time, which revokes the authorization and deletes it from Composio; for the older Gmail plugin, it deletes the token from your device. You can also revoke access at myaccount.google.com/permissions, where a Gmail or Google Calendar connection is listed under Composio and the older Gmail plugin under Enconvo.

Enconvo's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

The desktop app sends product analytics to PostHog to help us understand which features work and where they fail. This is on by default, and you can turn it off in Settings > General. Events include the app version, system version, device identifier, plugin and command identifiers, status, and duration. If you are signed in, we link these events to your Enconvo account. Analytics never include your prompts, selected text, clipboard contents, files, emails, API keys, or model responses.

The website enconvo.com uses Google Analytics to measure visits. The iPhone and Android apps use PostHog only when you turn on Settings > Share usage data. It is off by default for new installations. Events use a device identifier and include feature identifiers, app and system versions, status, counts and duration, never your chat content, files, API keys or email address. You can turn this off at any time.

On enconvo.com, Google Analytics and the marketing cookies that credit a campaign or partner run only after you allow them in the cookie banner. Our Cookie Policy lists every cookie the website uses and how to change your choice.

While product analytics is on in the desktop app, or Settings > Share usage data is on in the iPhone and Android apps, the apps also send crash and freeze reports to Sentry so we can find and fix problems. A report contains the stack trace, the app version, device and system details such as the model, system version and memory, the device identifier and the country of your region setting. We do not attach your prompts, chat content, files, API keys or email address to reports. Error messages are shortened, your home folder is removed from file paths, and Sentry is set not to store IP addresses. Our API servers also report errors to Sentry, with the request's route but not its content.

We rely on these providers to operate Enconvo. Each processes data only on our behalf:

• Supabase. Account sign-in and account records.
• Cloudflare. Our API servers, the iPhone relay, Phone chat sync storage, and operational logs.
• Stripe. Payments.
• PostHog. Product analytics.
• Sentry. Crash, freeze and error reports.
• Google Analytics. Website analytics.
• Resend. Account and product update emails.
• Composio. Holding the authorization for your Gmail and Google Calendar connections and running those requests with Google.
• AI, speech, and search providers. Processing the cloud requests you make, as described above.
• Apple. Push notifications to the iPhone app.

Enconvo for Android handles Phone chats, attachments, personal instructions and AI requests as described for the iPhone app. Push notifications use Google's Firebase Cloud Messaging. In Android Settings > Delete account, you can permanently delete your Enconvo account under the retention terms below. When you use Report AI content, only the content you confirm and the reason you select are sent to Enconvo for private safety review. Reports are kept for up to 30 days and removed when you delete your account.

On iPhone, use Settings > Delete account to permanently delete your Enconvo account, synced Phone and desktop chats and files, and connected-service authorizations. Active Cloud subscriptions are cancelled, and purchased plans and unused points are lost. We retain payment and legally required financial records; publicly licensed work may remain available under its licence. Local data on your other devices is not remotely erased. AI data sharing requires your permission before sending content, and you can withdraw it in Settings > Allow AI data sharing.

We keep account, plan, and usage records while your account is active. Operational logs are deleted after at most 7 days. To delete your account and the data tied to it, including synced Phone chats, email us at support@enconvo.com from the address on your account. We complete deletion within 30 days, except for payment records that we must keep by law.

Data stored only on your device, such as local chat history, is removed when you delete it in Enconvo or uninstall the app and remove its data folder.

Connections to our servers use TLS. Stored data is encrypted at rest by our infrastructure providers. Tokens for connected accounts are encrypted on your device, and access to production systems is limited to the people who operate Enconvo.

Enconvo is not directed to children under 13, and we do not knowingly collect personal data from them.

Creating an account asks for your month and year of birth. We keep only the fact that you met the minimum age, not your date of birth. If someone below the minimum age tries to sign up, we delete the account at once. If you believe a child has given us personal data, email support@enconvo.com and we will delete it.

We may update this policy as Enconvo changes. We will post the new version on this page and update the date at the top. If a change materially affects how we handle Google user data or other personal data, we will also notify you in the app or by email before it takes effect.

If you have questions about this policy or want to exercise your privacy rights, contact us at support@enconvo.com.