COMMERCIAL & OPERATING POLICIES
Public checkout is not active. Access and funding are operator-approved. These product policies do not replace a signed order, data-processing addendum or negotiated enterprise agreement. Legal entity details, governing law and a formal notices address must be approved before self-service general availability.
LAUNCH TERMS
Binah provides an OpenAI-compatible gateway to the exact models listed as callable in the live catalogue. Catalogue presence is configuration, not a promise of permanent availability. Models, providers and rates may change prospectively; the recorded tariff version governs completed usage.
binah/auto remains intentionally disabled. Binah will not present automatic model choice as available, benchmark-backed or production-qualified until its evidence and operating gates pass.
Customers must have authority to submit their inputs and may not use the service to violate law, intellectual-property rights, provider rules or security controls; distribute malware; evade safeguards; or make prohibited automated high-impact decisions. Binah may restrict access to contain abuse, fraud or a credible security risk.
Requests are processed by the selected upstream provider under the applicable provider terms. Model output can be incomplete or inaccurate. Customers remain responsible for review, downstream use and any professional or regulated decision made from an output.
PRIVACY & DATA
Binah processes API inputs, outputs and request metadata to authenticate, route, stream, meter, secure and support the service. Content is sent to the selected upstream provider. The catalogue’s data-boundary label and the customer’s signed terms—not a marketing label—determine the permitted route.
Binah records tenant identity, model, provider, token usage, timing, cost, request state and security events for billing, reliability and abuse prevention. API-key secrets are not returned after creation. Customers should not submit regulated or highly sensitive data unless an appropriate written agreement and eligible route are in place.
Zero-retention or no-training claims apply only where provider terms and endpoint configuration have been verified for that route. Binah does not convert an unverified provider endpoint into a zero-retention endpoint by relabeling it.
Tenant-isolated keys, hard prepaid limits, request history and key revocation are available in the customer portal. Security or privacy incidents should be reported through the designated onboarding support channel.
REFUNDS & BILLING CORRECTIONS
If a request fails before Binah records supported output delivery, the prepaid reservation is released or reconciled to the supported provider cost. Duplicate charges and confirmed metering errors are corrected as account credit.
Valid usage for a completed request is not refundable merely because a model answer was unsatisfactory. Model quality varies, so customers should validate outputs and use hard budgets while evaluating a model.
A stream cancelled after upstream commitment may remain reserved while provider evidence is reconciled. Any amount above confirmed billable usage is returned to the customer balance when reconciliation completes.
Public card checkout and cash refunds are not active. Current corrections are ledger credits. Promotional grants are not redeemable for cash. A cash-refund window and payment-processor terms must be published before self-service purchases begin.
Use the account’s designated onboarding support channel and include the Binah request ID, approximate time and disputed amount. Do not send API-key secrets.
SUPPORT COMMITMENTS
Support is provided through the designated channel supplied during onboarding. Coverage is Monday–Friday, 9:00 a.m.–5:00 p.m. Eastern Time, excluding U.S. federal holidays. Targets measure acknowledgement, not resolution, and pause while required customer or upstream-provider information is unavailable.
Authenticated production access is unavailable for the account, or a security event requires immediate containment.
4 business hoursA live feature is materially degraded but an exact-model request path remains available.
1 business dayBilling questions, access changes, documentation requests and non-blocking defects.
2 business daysSERVICE LEVELS
The current service has no contractual availability percentage, recovery-time guarantee or service-credit schedule.
Catalogue sample sizes and measured request outcomes may describe observed behavior. They are not an SLA and do not prove future availability.
Any future uptime target, incident notification window, support coverage or service credits apply only when written into a signed order.