Privacy Policy · helping.io

This Privacy Policy describes how IMNS LLC, a Wyoming limited liability company (doing business as “Helping.io”) (“we,” “us,” “our”) collects, uses, and shares information when you use Helping.io and related services (the “Service”).

1. Information We Collect

1.1 Account Information

When you create an account, we collect information such as your name, email address, password (stored hashed), and account identifiers. We record your IP address and browser details when you sign in and on security records. We also keep a record of the API keys you create.

1.2 Billing Information

Payments are processed by Stripe. We receive billing-related metadata (such as plan, subscription status, and payment confirmations). We do not store full payment card numbers.

1.3 Service Data You Provide

You may provide content such as messages, prompts, code snippets, tool inputs and outputs, and conversation history. You control what you submit.

If you send a bug report from the VS Code extension, we store the report.

1.4 Workspace Paths and File Content

When using the VS Code extension, the Service may include file paths as context. Paths inside your workspace (the folders you have open in VS Code) are converted to workspace-relative form.

The Service may access file contents through user-initiated tools (for example, a “read file” tool). We do not store entire projects on our servers. We process only the content necessary to fulfill your request, which is typically limited excerpts.

1.5 Logs and Security Events

We use Axiom for application logs and error monitoring. These logs include request metadata and error information. As configured, our production logs do not contain prompt content or tool outputs. This is a configuration control rather than a technical impossibility, so we describe it as our practice rather than as an absolute guarantee.

We also maintain authentication and security audit logs in our database for security purposes.

1.6 Email Communications

We use Google Workspace for operational email and Resend for transactional email only (for example, password resets, email verification, and invitations).

1.7 Analytics

We currently do not use third-party analytics tools.

2. How We Use Information

We use information to provide and operate the Service, authenticate users, secure accounts, process billing, provide support, prevent abuse, and maintain and improve the Service.

3. AI Processing and Third-Party Model Providers

The Service can send user-provided content to third-party large language model providers to generate responses. Content sent may include chat messages, code snippets, file paths, and error logs or stack traces.

We do not send personal identifiers (such as your name or email address) to model providers as part of normal operation. Paths inside your workspace are converted to workspace-relative form before they are sent. Paths outside your workspace may be sent unchanged. That includes paths you type into a message and paths that show up in the output of commands the extension runs, such as a compiler error that names a file elsewhere on your computer.

Current providers: Anthropic, OpenAI, and Google (Gemini).

Third-party model providers process content to provide responses. Their handling of data is governed by their own terms and privacy policies.

We share information with service providers that help us operate the Service, including Render (hosting of the API), Neon (managed Postgres database), Cloudflare (edge network, hosting of the web app and sites, and object storage), Stripe (billing), Resend (transactional email), Google Workspace (operational email), GitHub (issue tracking), Axiom (logging), and AI model providers (Anthropic, OpenAI, and Google). Our Subprocessors page is the authoritative list.

We may also share information to comply with legal obligations, enforce our terms, protect the Service and users, or in connection with a corporate transaction.

5. Data Retention

No retention period is applied today to account data or service data. What you send us (messages, the model requests and responses they produce, tool inputs and outputs, and the conversation record built from them) is kept until something deletes it. We do not state a retention period we do not enforce. Our security audit log, which records authentication and administrative events (not conversation content), is kept for as long as needed for security and fraud prevention.

You can delete your own conversations in the VS Code extension, and conversations and responses created through our /v1 API through the API. A delete works the same way everywhere: the conversation or response is hidden from every read at once and can no longer be continued, and its content (the messages, the model requests and responses they produced, tool inputs and outputs, stored outputs and attached files) is erased 30 days after the delete. We keep the record that each request was made and what it cost, which holds no conversation content, as part of our billing records. A conversation attached to an evaluation experiment cannot be deleted while that experiment exists.

There is no self-service deletion of an entire account or organization. To request deletion of your account, contact us at support@helping.io. We handle these requests manually. Within 30 days of your request, we delete or anonymize your personal data. We keep billing records and the security audit log, as the law and security require.

Axiom log retention depends on our plan.

6. Security

We use reasonable measures to protect information. No method of transmission or storage is completely secure.

7. Your Choices

You can delete your own conversations in the VS Code extension and through the /v1 API, as described in Section 5, and you can request account deletion by emailing support@helping.io. You can opt out of marketing emails using unsubscribe links where provided.

8. Children’s Privacy

The Service is not intended for individuals under 18.

9. International Users

If you access the Service from outside the United States, you understand that information may be processed and stored in the United States and other locations where our service providers operate.

10. Changes to This Policy

We may update this Privacy Policy from time to time. We will post the updated version and change the “Last updated” date.

12. Contact

Privacy questions or requests: support@helping.io