# Privacy Policy

> What 1Helm collects, how it's used, who handles it, how long it's kept, and your choices.

Last updated: October 10, 2026 · Questions and requests: [support@1helm.com](mailto:support@1helm.com)

> **Optional diagnostic-sharing terms — October 12, 2026.** The diagnostic-sharing permission below applies only when you separately enable it and confirm by email. Sharing remains off unless you make that choice.

## The short version

We run a personal AI helper for you, so we store your account and what you and your helper work on to run it for you. Optional diagnostic access lets 1Helm inspect filtered, retained account information only after you enable it and confirm by email; it is off by default. That separate permission includes evaluation using support and AI tools chosen by 1Helm, including non-ZDR tools under their own terms, as explained below. We never sell your information or use it for advertising, and 1Helm does not train AI models on your chats or files.

## What we collect

- **Your account:** your email address, your name, your 1Helm address, your plan, and the name and look you picked for your helper.
- **Your workspace:** your messages with your helper, files you add and files it makes (and the text, summaries and indexes it prepares from them), its Notebook and memory, your contacts, tasks, schedules and meeting notes, and what it does on its computers.
- **Saved logins and keys:** stored encrypted, apart from everything else. They can't be shown again, not to you and not to your helper.
- **Billing:** your plan, payments, credits and usage. Card details go straight to Stripe; we never see your full card number.
- **Location, only if you allow it:** your device's location. We keep only the latest one, with its town or city name, and no history.
- **Your voice, only when you tap the microphone:** for dictation or Live notes. Recordings are turned into text and not stored as audio.
- **If you set them up:** your phone number for texting; conversations, transcripts and facts from your Bee; and your devices' notification addresses.
- **Issue reports you send:** your note, any screenshot, the app's version, your device and window size, and recent error lines.
- **Technical logs:** IP address, device and browser type, pages requested, errors and timestamps, used to run, debug and secure the service.

The app uses one cookie, to keep you signed in. It lasts 30 days, or until you log out. There are no advertising or tracking cookies, and this website sets none.

## How we use it

To run your helper and your account, bill you, send sign-in codes and important account emails, keep the service secure, fix problems and improve 1Helm. Your helper uses your information for what you ask it to do, and shares it with an outside service only as that task needs. The optional diagnostic access described below is a separate, email-confirmed choice. We don't sell your information, share it for advertising, or train AI models on your chats or files.

## Optional diagnostic access

**Settings → Advanced → Share diagnostic data** is off by default. To enable it, the account owner must enter a separate six-digit confirmation code sent to their account email. Pending confirmation gives no access. Each diagnostic read requires both 1Helm's internal authentication and your currently confirmed permission.

When investigating a problem, 1Helm can request specific retained account, channel or chat records through a read-only internal API. These may include conversations and model context, tool instructions and results, activity and errors, timing and usage, task and workflow state, approvals and pauses, current settings, connection metadata, Notebook and memory records, file metadata and already-prepared attachment text. Records may predate enabling the setting. The permission remains active until you disable it; it is not approval of only one chat or one incident.

The API filters the requested information in memory before returning it. Saved credential stores and credential fields are excluded; detected secrets are removed and recognized personal identifiers are replaced with placeholders. Original attachment binaries are not exposed. **This is redacted access, not guaranteed anonymity:** filtering may miss identifying details, and context can identify you or other people.

Enabling this setting does not start continuous recording or create a separate store of redacted conversations. The diagnostic API does not save its response bodies, impersonate you, execute tools or contact connected apps. It can only read information still retained by 1Helm; deleted or unrecorded history, unsaved past settings and processing limits can prevent a complete explanation.

You can disable sharing in Advanced settings at any time. This stops subsequent diagnostic reads and cancels pending confirmation; it does not undo information already returned or delete the original workspace records. Those records remain subject to their ordinary retention and deletion rules.

We retain consent and access metadata, such as consent status and confirmation/update times, the type of record requested, a non-content scope reference and the result of the request. These records do not contain the diagnostic response body. They can remain after sharing is disabled or a chat is deleted; deleting the account removes its diagnostic consent and access records.

**Support and AI evaluation tools.** By confirming sharing, you also authorize 1Helm to evaluate returned diagnostic information using support and AI tools selected at 1Helm's discretion, including tools without zero data retention (non-ZDR). This is separate from your in-app AI data privacy setting: that setting does not restrict these tools. Their terms and practices govern their processing, retention and deletion of received information, including any permitted use for model improvement or training. There is no fixed retention period promised for those copies, and disabling sharing or deleting your 1Helm account does not by itself recall or erase them.

The diagnostic API itself does not call AI providers or save its response bodies. That describes the API, not the practices of separate support tools that receive its output. See the [diagnostic-sharing guide](https://1helm.com/docs/privacy/diagnostics/) for the steps and limitations, or contact [support@1helm.com](mailto:support@1helm.com) about information already shared.

## AI providers

Your messages, and the files, memory and app information needed to answer them, are sent to AI providers to produce each reply. Which providers may handle them follows your AI data privacy choice in Settings: **Zero Data Retention** (only providers with verified zero-data-retention coverage; the default), **No Training** (providers that don't train on your requests but may keep them for a limited time under their own policies), or **Unrestricted** (also providers that may keep requests or use them to improve and train their models, under their own terms). The check that picks a model and background chores always use zero-data-retention providers. Speech-to-text first uses 1Helm's own speech models on 1Helm's own servers, where the audio isn't sent to an outside AI provider, and the audio pieces kept for speaker labels are deleted right after the final labeling pass of a meeting. When a hosted speech model has to answer instead, it is always a zero-data-retention provider. If you use your own AI key, what the AI reads goes to that provider under its terms.

## Who else handles it

Each of these only gets what it needs for its job:

- **Cloudflare** hosts 1Helm: the app, your conversations, your helper's computers, files, the database and this website. It also sends our emails.
- **Web search** goes to DuckDuckGo through Cloudflare, so the search engine sees Cloudflare, never your device. When it's busy, a backup search goes to a zero-data-retention search service.
- **Stripe** processes payments. Purchases your helper makes go through your Link wallet (by Stripe), approved by you each time.
- **Connected apps:** app sign-ins and the actions your helper takes in them go through Composio, on 1Helm's Composio account or, if you choose Self-managed, your own. Composio holds sign-in tokens to act for you and, on our plan, keeps copies of app requests and responses for up to a year; never used for ads, selling or AI training.
- **Live search** (flights, hotels, places, shopping and the like) also runs through Composio, with your search terms only.
- **Texting** goes through Photon, using your own Photon account, and Apple or your carrier to reach your phone.
- **Notifications** go through your device's push service (Apple's, Google's, Mozilla's or Microsoft's), encrypted so the push service can't read them.
- **Place names:** to name your town, only the rounded spot (no name, account or address) goes to OpenStreetMap's place-name service (Nominatim), and only when it changes.
- **Bee**, if you connect it: we read your Bee data with the access you grant, and changes you make to Bee facts in 1Helm go back to Bee.
- **OpenRouter**, if you sign in with it for your own AI key.
- **Logos:** company logos in the app (next to saved logins, purchases and work contacts, for example) load in your browser from logo.dev.
- **Websites your helper visits for you** receive what any visitor sends, plus anything you've asked it to enter.

We may also share information if the law requires it, to protect someone's safety, or as part of a sale or merger of 1Helm (in which case this policy keeps applying to your information).

## How long we keep it

- While your account is open, we keep your workspace so your helper can keep working for you. You can delete chats, channels, notes, contacts and files yourself at any time, and deleted means gone for good, everywhere we keep it.
- Deleting your account deletes your workspace right away. When a plan ends after you cancel, your account and workspace data are permanently deleted at the end of the period you paid for. After a failed payment, data is kept until the end of the paid period plus 7 days, then permanently deleted. We don't keep a recoverable workspace copy. Information already received by diagnostic support or AI tools follows their own terms and retention/deletion practices; account deletion does not by itself erase those copies.
- Billing and tax records are kept as long as the law requires. Technical logs are kept only as long as needed to run and secure the service.

For optional diagnostic access, there is no separate API response-body archive. Consent and content-free access metadata have the lifecycle described above; turning sharing off or deleting a chat does not itself erase those account-level records. Turning off access cannot recall information already returned.

## Your choices and rights

You can read and edit your Notebook, contacts and files, download your files, disconnect any app, remove any saved login or key, turn off texting, location or your Bee, choose how often your helper asks first, choose which AI providers may handle your requests, and delete your account, all in Settings. You can also email [support@1helm.com](mailto:support@1helm.com) to ask for a copy of your information, a correction or deletion. We'll answer within 30 days, and we won't treat you differently for asking. Depending on where you live (for example California or the EU/UK), you may have extra rights under local law; we honor them.

Your data is stored and processed by Cloudflare and the providers above, which may do so in the United States and other countries.

## Security and age

Your 1Helm workspace data is encrypted in transit and at rest. The hosted app redirects HTTP page requests to HTTPS and rejects HTTP writes without replaying them. Every external web request from your helper's computer must use HTTPS; Sentinel blocks plain HTTP before it looks up a saved key, asks for approval or forwards the request. Redirects back to HTTP are blocked too. The computer's internal controller uses a runtime binding, while direct SSH and managed Tailscale have separate permissions.

Cloudflare encrypts stored conversations, files and account data. Saved logins and keys are encrypted separately from chats and files, and each channel's computer is separate from everyone else's. Encryption does not prevent the services you choose from processing data needed to fulfill your requests. No system is perfectly secure; if a breach affects your information, we'll tell you as the law requires. 1Helm is only for people 18 and older, and we don't knowingly collect information from children.

## This website

1helm.com has no sign-ups of its own and sets no cookies. Like most web servers, it keeps standard operational logs (IP address, user agent, requested pages, timestamps), used only to run and secure it. App logos on the Apps page load from app.1helm.com.

## Changes and contact

If this policy changes, the date above will be updated, and we'll email you about material changes before they apply. Questions or requests: [support@1helm.com](mailto:support@1helm.com).

---
Web page: https://1helm.com/privacy/