Trust Center

SOC 2 is in progress. No Type I month, no Type II observation start, and no compliance platform are published yet. The report is not available.

Not started. No test is booked, and there is no letter of attestation.

Not started. No incident response plan is published.

Not started. No access control policy is published.

Not started. No business continuity plan is published.

security.txt is published. Reports go to [email protected]. The file expires 2027-03-01.

The CLI, gdb, and the tools run on your machine. On the cloud path, the model request leaves for OpenAI, Anthropic, or Google. On the Enterprise on-prem path, the ByteAsk gateway and self-hosted models stay in your network.

To answer a request, our gateway forwards your prompt and the repository context the CLI sends to the provider serving the model you selected: OpenAI, Anthropic, or Google. If you bring your own key or point ByteAsk at your own model server, that traffic goes directly from your machine to your provider or server and does not pass through us.

Not started. No hosting region is published. The website names Cloudflare as its infrastructure provider.

byteask.ai is served over HTTPS. HSTS is enabled at the Cloudflare zone.

Not started. No at-rest encryption statement is published.

The prompts you type and the repository content the CLI sends are processed in memory to answer your request and are then dropped. We operate with zero data retention for prompts and code.

We keep your account email while your account is active. You can request access to or deletion of your data at any time by writing to [email protected], and we will act on the request promptly.

Your code and prompts are not used to train any model. Ours or anyone’s.

Not started. The no-training commitment is in the privacy policy. It is not shown here as a clause of the data processing agreement.

Not started. Agreements that put OpenAI, Anthropic, or Google on zero data retention are not published.

It joins your debugger. When your program crashes or hangs, ByteAsk joins the gdb session you already have open, breakpoints and state intact, shows every command, and asks before changing anything.

Not started. No least-privilege or scoped-permission model for the agent is published.

Not started. No kill switch is published.

Every session and tool call on record, with spend limits per user and per organization.

Not started. Replay of agent actions is not published.

Use your own OpenAI, Anthropic or Gemini key. Traffic goes straight to the provider, not through ByteAsk.

Run ByteAsk inside your network, including networks with no route to the internet.

Not started. No synthetic-data sandbox is published.

SAML single sign-on, SCIM provisioning and role-based access control.

Not started. There is no public status page.

Security and privacy questions go to [email protected]. Vulnerability reports go to [email protected].

Not started. No shared Slack Connect channel is published.

Not started. No standard MSA is published.

Data processing agreement, uptime SLA, invoicing and purchase orders.

Not started. No one-page pilot template is published.

Not started. No cyber, tech E&O, or general liability certificate is published.

ByteAsk, Inc.

Not posted on this page.

Not started. No reference customer is published for a buyer call.

Not started. No week-by-week security review is published.

To answer a request, our gateway forwards your prompt and the repository context the CLI sends to the provider serving the model you selected: OpenAI, Anthropic, or Google. If you bring your own key or point ByteAsk at your own model server, that traffic goes directly from your machine to your provider or server and does not pass through us.

To answer a request, our gateway forwards your prompt and the repository context the CLI sends to the provider serving the model you selected: OpenAI, Anthropic, or Google. If you bring your own key or point ByteAsk at your own model server, that traffic goes directly from your machine to your provider or server and does not pass through us.

To answer a request, our gateway forwards your prompt and the repository context the CLI sends to the provider serving the model you selected: OpenAI, Anthropic, or Google. If you bring your own key or point ByteAsk at your own model server, that traffic goes directly from your machine to your provider or server and does not pass through us.

byteask.ai sets no advertising cookies and does no cross-site tracking. Our infrastructure provider (Cloudflare) may process connection data such as IP addresses to serve and protect the site.

We use PostHog (hosted in the United States) to understand how the site is used. It records which pages you view, how long you stay, what you click, how far you scroll, how quickly the page loaded, the referring site, and the browser type. It does not record your location. These requests go through our own domain rather than a third-party address. Your identity is a code generated on PostHog's servers, not stored on your device. No cookie is set and nothing about you is kept in your browser for this, so we do not ask for consent.

Paid plans are billed through Razorpay, our payment processor. Razorpay handles your card details under its own privacy policy; we receive confirmation of payment and the plan purchased, not your card number.

Sign-in links are delivered through a transactional email provider. Your email address is shared with that provider only to deliver the message.