Terms of Service

Operating terms for Beacon's current product surface.

Effective May 4, 2026. These terms are written to match the current Beacon implementation and its real operational limits. They are stronger than the prior placeholder, but they should still be reviewed by counsel before broader production or enterprise use.

Search docs, support, and public pages
search
Acceptance

Using Beacon means you accept these terms

Agreement to terms

By accessing or using Beacon, you agree to these Terms of Service and the related Privacy Policy and Disclaimer. If you use Beacon on behalf of a company or team, you represent that you have authority to bind that organization to these terms.

Current maturity

Beacon is an evolving AI research product. Features, limits, integrations, retention behavior, and security controls may change as the product matures. Continued use after changes means you accept the updated terms unless a different notice requirement applies by law.

Use

Permitted and prohibited use

Permitted use

Beacon may be used for research, synthesis, monitoring, analyst workflows, and internal decision support, provided the user has the right to submit the input data and independently reviews the resulting output.

No unlawful or abusive use

You may not use Beacon to violate law, infringe rights, evade safeguards, disrupt the service, scrape or probe the infrastructure without authorization, or submit material that you do not have the right to process.

No regulated-decision outsourcing

You may not use Beacon as the sole basis for automated or quasi-automated decisions involving employment, credit, insurance, housing, education, medical treatment, legal rights, safety outcomes, or other similarly high-risk determinations.

No unsupported sensitive data use

Do not submit special-category personal data, health records, government IDs, biometric data, highly confidential material, or regulated client matter data unless you have explicit approval and a deployment posture that is actually designed for that use.

Responsibility

What users are responsible for

Input responsibility

You are responsible for the topics, prompts, source material references, and credentials you submit. That includes making sure you have a lawful basis and any needed permissions to process personal or confidential data through Beacon.

Account and key security

You are responsible for protecting your account access, saved provider keys, and connected integrations. Notify the operator if you believe your account, session, or API credentials have been exposed.

Verification duty

You are responsible for reviewing reports, checking source quality, and validating conclusions before using them in any consequential workflow. Beacon reduces research effort; it does not transfer judgment or accountability away from the user.

Third-party terms

Use of Beacon may also depend on third-party services such as Clerk, Upstash, Groq, SerpAPI, Vercel, Slack, GitHub, or Discord. You are responsible for complying with any third-party terms that apply to your use of those connected services.

AI Limits

Beacon output is assistive, not guaranteed

No warranty of correctness

Beacon output may be incomplete, outdated, biased, misleading, or wrong. Search results can omit relevant sources, retrieved snippets can lack context, and model-generated summaries can reflect reasoning errors or source inaccuracies.

No professional advice

Beacon does not provide legal, medical, financial, accounting, employment, compliance, or other regulated professional advice. Any content that touches those subjects is informational only and must be independently reviewed by a qualified person.

Source-first interpretation

Where Beacon provides URLs, snippets, or source ledgers, those materials should be treated as the primary audit trail. If the synthesized narrative and the cited source conflict, the user should trust the source and not the model summary.

Availability

Service availability and operator controls

No uptime guarantee

Beacon is provided on an as-available basis. The operator does not guarantee uninterrupted operation, permanent feature stability, or that workflow runs, memory retention, chat integrations, or API surfaces will always remain available.

Suspension and limits

The operator may suspend, rate-limit, disable, or remove access where reasonably necessary for security, legal compliance, abuse prevention, infrastructure protection, or product maintenance.

Changes to the service

The operator may add, remove, or modify features, model providers, retention behavior, authentication rules, or integrations at any time, especially where required for security, cost control, or legal compliance.

Risk Allocation

Warranty disclaimer and liability limits

Warranty disclaimer

To the maximum extent permitted by law, Beacon is provided on an 'as is' and 'as available' basis, without warranties of accuracy, merchantability, fitness for a particular purpose, non-infringement, or uninterrupted availability.

Limitation of liability

To the maximum extent permitted by law, the operator will not be liable for indirect, incidental, special, consequential, exemplary, or similar damages, or for loss of profits, business, goodwill, data, or decision quality arising from use of Beacon or reliance on its outputs.

Practical reading of these terms

These terms are intended to make the product's legal posture materially more credible for review today, not to replace a full enterprise contracting package. If Beacon is going to be sold, deployed in regulated settings, or used on sensitive workloads, further contractual and governance work is still required.