Privacy Policy

Your Privacy Matters to Us

Your Privacy Matters to Us

Your Privacy Matters to Us

We process your debugging data securely and never store logs, traces, or code.

We process your debugging data securely and never store logs, traces, or code.

We process your debugging data securely and never store logs, traces, or code.

We process your debugging data securely and never store logs, traces, or code.

Effective Date: December 01, 2025
Last Updated: December 29, 2025

This Privacy Policy explains how Boundless91, Inc. (“Boundless91,” “we,” “our,” or “us”) collects, uses, and protects personal information when you use OnCall, our AI-powered debugging product, service, and software platform.

By accessing OnCall, you agree to this Privacy Policy. If you do not agree, please discontinue use.

1. Who We Are

OnCall is a subsidiary product of Boundless91, Inc., located at:

30 Oakwood Avenue
Norwalk, CT 06850
United States

You can contact us at: support@oncall.build

2. Information We Collect

OnCall collects minimal personal information, and only what is required to operate your account and process logs for debugging.

2.1. Information You Provide

  • Account Information: email address, OAuth profile data, or access key information used for authentication.

  • Billing & Payment Information: If you subscribe to a paid plan, we use third-party payment processors, such as Stripe, to handle payments. These processors may collect and process your personal information, including your payment card details, billing address, and device usage data for fraud prevention and security purposes. We do not store your payment card information directly. You can read more about how Stripe handles your data in their Privacy Policy.

2.2. Automatically Processed Technical Data

OnCall processes debugging inputs such as:

  • Logs

  • Stacktraces

  • Error messages

  • Runtime signals

  • Code fragments included in logs

Important:

  • These inputs are processed temporarily to generate results.

  • We do not store logs, error traces, runtime signals, or code.

  • Once the debugging operation is complete, the data is discarded immediately.

2.3. Cloud Processing for AI

To provide debugging insights, OnCall sends your runtime data to:

  • Industry-leading large language model (LLM) providers such as Anthropic, OpenAI, or others.

These providers may use the data solely to generate responses, in accordance with their own privacy policies. OnCall does not permit providers to retain or train on user data.

2.4. Device & Usage Information

To ensure security and performance, we may collect:

  • Device type

  • Operating system

  • Browser or CLI version

  • IP-based region (not exact location)

  • Usage metrics (e.g., session duration, error rates)

2. Information We Collect

OnCall collects minimal personal information, and only what is required to operate your account and process logs for debugging.

2.1. Information You Provide

  • Account Information: email address, OAuth profile data, or access key information used for authentication.

  • Billing & Payment Information: If you subscribe to a paid plan, we use third-party payment processors, such as Stripe, to handle payments. These processors may collect and process your personal information, including your payment card details, billing address, and device usage data for fraud prevention and security purposes. We do not store your payment card information directly. You can read more about how Stripe handles your data in their Privacy Policy.

2.2. Automatically Processed Technical Data

OnCall processes debugging inputs such as:

  • Logs

  • Stacktraces

  • Error messages

  • Runtime signals

  • Code fragments included in logs

Important:

  • These inputs are processed temporarily to generate results.

  • We do not store logs, error traces, runtime signals, or code.

  • Once the debugging operation is complete, the data is discarded immediately.

2.3. Cloud Processing for AI

To provide debugging insights, OnCall sends your runtime data to:

  • Industry-leading large language model (LLM) providers such as Anthropic, OpenAI, or others.

These providers may use the data solely to generate responses, in accordance with their own privacy policies. OnCall does not permit providers to retain or train on user data.

2.4. Device & Usage Information

To ensure security and performance, we may collect:

  • Device type

  • Operating system

  • Browser or CLI version

  • IP-based region (not exact location)

  • Usage metrics (e.g., session duration, error rates)

2. Information We Collect

OnCall collects minimal personal information, and only what is required to operate your account and process logs for debugging.

2.1. Information You Provide

  • Account Information: email address, OAuth profile data, or access key information used for authentication.

  • Billing & Payment Information: If you subscribe to a paid plan, we use third-party payment processors, such as Stripe, to handle payments. These processors may collect and process your personal information, including your payment card details, billing address, and device usage data for fraud prevention and security purposes. We do not store your payment card information directly. You can read more about how Stripe handles your data in their Privacy Policy.

2.2. Automatically Processed Technical Data

OnCall processes debugging inputs such as:

  • Logs

  • Stacktraces

  • Error messages

  • Runtime signals

  • Code fragments included in logs

Important:

  • These inputs are processed temporarily to generate results.

  • We do not store logs, error traces, runtime signals, or code.

  • Once the debugging operation is complete, the data is discarded immediately.

2.3. Cloud Processing for AI

To provide debugging insights, OnCall sends your runtime data to:

  • Industry-leading large language model (LLM) providers such as Anthropic, OpenAI, or others.

These providers may use the data solely to generate responses, in accordance with their own privacy policies. OnCall does not permit providers to retain or train on user data.

2.4. Device & Usage Information

To ensure security and performance, we may collect:

  • Device type

  • Operating system

  • Browser or CLI version

  • IP-based region (not exact location)

  • Usage metrics (e.g., session duration, error rates)

2. Information We Collect

OnCall collects minimal personal information, and only what is required to operate your account and process logs for debugging.

2.1. Information You Provide

  • Account Information: email address, OAuth profile data, or access key information used for authentication.

  • Billing & Payment Information: If you subscribe to a paid plan, we use third-party payment processors, such as Stripe, to handle payments. These processors may collect and process your personal information, including your payment card details, billing address, and device usage data for fraud prevention and security purposes. We do not store your payment card information directly. You can read more about how Stripe handles your data in their Privacy Policy.

2.2. Automatically Processed Technical Data

OnCall processes debugging inputs such as:

  • Logs

  • Stacktraces

  • Error messages

  • Runtime signals

  • Code fragments included in logs

Important:

  • These inputs are processed temporarily to generate results.

  • We do not store logs, error traces, runtime signals, or code.

  • Once the debugging operation is complete, the data is discarded immediately.

2.3. Cloud Processing for AI

To provide debugging insights, OnCall sends your runtime data to:

  • Industry-leading large language model (LLM) providers such as Anthropic, OpenAI, or others.

These providers may use the data solely to generate responses, in accordance with their own privacy policies. OnCall does not permit providers to retain or train on user data.

2.4. Device & Usage Information

To ensure security and performance, we may collect:

  • Device type

  • Operating system

  • Browser or CLI version

  • IP-based region (not exact location)

  • Usage metrics (e.g., session duration, error rates)

3. What We Do Not Collect or Store

OnCall does not:

  • Store logs, code, or debugging content

  • Collect or store full datasets of user interactions

  • Build training data from your logs

  • Sell your data

  • Track your personal activity within your application or infrastructure

We collect the bare minimum required to operate the service safely and effectively.

4. How We Use Your Information

We use collected information only for:

4.1. Service Operation

  • Authenticating user accounts

  • Processing debugging requests

  • Displaying results to you

  • Managing subscriptions and billing

4.2. Service Improvement

  • Identifying performance issues

  • Ensuring platform reliability

  • Preventing misuse or illegal activities

4.3. Communication

  • Sending important product updates

  • Notifying you about changes to Terms or Privacy Policy

  • Providing support

We do not use your logs or code for marketing, profiling, or analytics.

  1. How Your Data Is Processed

Local-First Processing

When possible, logs and signals are handled locally on your machine.

Cloud-Based Processing

Certain investigations require sending data to OnCall’s servers and/or third-party LLMs.
In these cases:

  • Data is transmitted securely

  • Data is processed momentarily

  • Data is deleted immediately after processing

We maintain no long-term storage of logs or debugging content.

6. Sharing Your Information

We share information only with:

6.1. Third-Party Service Providers

  • LLM providers

  • Authentication providers

  • Payment processors

  • Cloud infrastructure partners

6.2. Legal Requirements

We may share minimal necessary information if required by law or if we detect illegal activity.
However, since logs are not stored, we typically have no access to your debugging content.

We do not sell or rent personal information to any third party.

7. Security

We use industry-standard measures to protect your information, including:

  • Encryption in transit (HTTPS/TLS)

  • Credential hashing

  • Strict access control

  • Cloud security best practices

  • Zero-retention log processing

Despite our efforts, no system is 100% secure. Use OnCall at your discretion.

8. Data Retention

We retain:

  • Account and billing details as long as your account is active

We do not retain:

  • Logs

  • Stacktraces

  • Error messages

  • Debugging data

  • Any uploaded or streamed code

All debugging data is processed ephemerally.

9. Your Rights

Depending on your region (e.g., GDPR, CCPA), you may have rights to:

  • Access the data we hold about you

  • Request correction or deletion

  • Request a copy of your account details

  • Object to certain processing

Email support@oncall.build to make a request.

10. Children’s Privacy

OnCall is not intended for anyone under age 18, and we do not knowingly collect data from minors.

11. International Data Transfers

OnCall and its third-party providers may process data in the United States or other countries.
By using OnCall, you consent to such transfers.

12. Changes to This Policy

We may update this Privacy Policy from time to time.
When updated, we will revise the “Last Updated” date.
Continued use of OnCall constitutes acceptance of the updated policy.

13. Contact Us

For questions, support, or legal concerns:
📧 support@oncall.build
📍 Boundless91, Inc.
30 Oakwood Avenue
Norwalk, CT 06850

Ready to install?

Turn your logs into answers

Turn your logs into answers

Install OnCall, run your next command, and ask one question. Then try cluster mode when the bug crosses services.

© 2025 OnCall (A Boundless91, Inc. Company)

Go back up!

ONCALL

optimized
realtime
solved
terminal-native
auto-detect
no-context-switch
zero-config

ONCALL

optimized
realtime
solved
terminal-native
auto-detect
no-context-switch
zero-config