Terms of Service

Effective Date: August 22, 2026

Last Updated: August 22, 2026

These Terms of Service ("Terms") govern access to and use of Ruzzler, RuzzChat, RuzzCode, APIs, SDKs, plugins, agents, integrations, workflow systems, developer tools, self-hosted components, and related products and services operated by BEE RAD TECH LLC, a Florida limited liability company ("BEE RAD TECH," "Ruzzler," "we," "us," or "our").

1. Acceptance

By accessing or using the Services, creating an account, executing an order form, or allowing an Authorized User to access the Services, you agree to these Terms.

If you use Ruzzler on behalf of a company or other organization ("Customer"), you represent that you have authority to bind that Customer.

If you do not agree, do not use the Services.

2. Intended Customers

Ruzzler is primarily designed for businesses, organizations, developers, and their Authorized Users.

Individual access may be permitted where authorized by the applicable organization or otherwise approved by BEE RAD TECH.

Ruzzler is not intended primarily as a consumer service.

3. Services

Ruzzler provides an AI orchestration and operational-support environment that may include:

• model aggregation and routing;

• RuzzChat and RuzzCode;

• AI model evaluation and verification;

• workflow and automation tools;

• autonomous or semi-autonomous agents;

• APIs and headless integrations;

• SDKs and plugins;

• developer tooling;

• organizational knowledge systems;

• private document vaults;

• workflow analytics;

• sanitization controls;

• Mosaic Mode;

• self-hosting assistance; and

• related AI infrastructure and services.

Features may evolve over time.

4. AI Routing

Ruzzler may select, evaluate, route, divide, or otherwise process workloads through independent AI models, systems, tools, and providers.

Routing decisions may consider capability, availability, cost, performance, privacy configuration, verification results, Customer preferences, technical requirements, or other relevant factors.

Third-party AI providers may include providers such as OpenAI, Anthropic, Google, and others.

Customers authorize Ruzzler to send information reasonably required to complete a requested operation to the applicable downstream provider, subject to Customer settings and Ruzzler's privacy and security controls.

5. Third-Party AI Providers

Third-party models are independently operated.

BEE RAD TECH does not control their: availability; underlying models; outputs; infrastructure; pricing; policies; retention practices; or future changes.

Ruzzler may stop supporting or replace a provider where reasonably necessary.

6. Ruzzler-Managed and Customer-Provided Model Access

Ruzzler may provide access to models under arrangements managed by Ruzzler.

Where supported, Customers may instead connect their own provider credentials or API keys.

Customers using their own credentials remain responsible for their provider accounts, provider terms, charges, security, configuration, and permissions.

7. Customer Content

"Customer Content" includes information submitted, uploaded, stored, generated, transmitted, or configured through the Services, including: prompts; files; documents; code; business information; instructions; workflows; configurations; knowledge-base materials; and other Customer-provided information.

As between BEE RAD TECH and Customer, Customer retains its rights in Customer Content.

Customer grants BEE RAD TECH a limited right to process Customer Content as reasonably necessary to provide, secure, maintain, support, and improve the Services consistent with these Terms and the Privacy Policy.

8. AI Outputs

Subject to applicable law and third-party rights, BEE RAD TECH does not claim ownership merely because an output was generated through Ruzzler.

AI output may: be inaccurate; contain errors; be incomplete; be outdated; resemble output provided to others; incorporate unexpected material; or fail to qualify for intellectual-property protection.

Customers are responsible for reviewing output before relying upon it.

9. Generalized Model Training

BEE RAD TECH will not intentionally use private Customer Content to train generalized Ruzzler models for unrelated customers unless Customer expressly authorizes that use.

Ruzzler will not intentionally submit private Customer Content to third-party AI providers for unrelated generalized model training where the applicable Ruzzler service has represented that such training is excluded.

This does not prevent processing reasonably required to deliver the requested service, maintain security, investigate failures, comply with law, or use appropriately de-identified or aggregated operational information where permitted.

10. Sanitizer

Ruzzler may provide a sanitization system designed to detect and reduce unnecessary transmission of sensitive information.

Depending on configuration, sensitive information may be: masked; tokenized; replaced; redacted; compartmentalized; or otherwise transformed before transmission to an external system.

Where technically appropriate, Ruzzler may reconstruct authorized context after the external processing step.

The sanitizer is a risk-reduction control, not a guarantee that all sensitive information will always be detected or prevented from leaving a system.

11. Mosaic Mode

Mosaic Mode may divide a project, request, codebase, workflow, or other context among multiple AI systems so that a single downstream provider need not receive the entire context.

Mosaic Mode is designed to reduce unnecessary concentrated exposure.

It does not guarantee: confidentiality; prevention of reconstruction; trade-secret protection; immunity from data leakage; prevention of independent reproduction; or intellectual-property security.

12. Verification

Ruzzler may compare, score, cross-check, test, or verify AI outputs in an effort to reduce hallucinations and errors.

Verification does not guarantee correctness.

Customers remain responsible for human review when output may affect material business, financial, safety, legal, technical, security, or other consequential decisions.

13. Employee and Business Operational Profiles

Ruzzler may maintain work-related profiles or context concerning a Customer, its teams, roles, personnel, systems, workflows, and operations.

These features are intended to support: organizational knowledge; workflow optimization; automation; technical architecture; operations; productivity; knowledge retrieval; and business decision support.

They are not intended for hiring, firing, promotion, discipline, compensation, employment eligibility, or other employment-status decisions.

Customers must not intentionally populate work profiles with unrelated personal information.

14. Customer Responsibility for Workforce Use

Customers determine their internal workplace policies.

Customers are responsible for: employee notices; permissions; agreements; access policies; lawful workplace monitoring; labor-law compliance; and other obligations arising from their use of Ruzzler.

Ruzzler provides technology and controls but does not determine whether a Customer's specific workplace use is lawful.

15. Private Document Vaults

Ruzzler may provide an individual-owned Personal Memory and private Document Center or Vault for an Authorized User. Personal Memory includes the individual's permanent personal conversation, derived memories, personal files, preferences, timeline, and related indexes.

Personal Memory is not Customer Content merely because a Customer purchases, reimburses, provisions, or administers the user's Ruzzler license. The individual retains control of Personal Memory.

Customer administrators, managers, payers, workflow owners, support delegates, and other Authorized Users receive no right to read, search, export, retain, place a legal hold on, or direct processing of Personal Memory by virtue of their organizational role or payment relationship.

Personal Memory and Customer-controlled workspaces use separate authorization and cryptographic boundaries. Company workflows may not retrieve from Personal Memory. Offboarding or mobile-device management may remove a work container but must not transfer or expose the individual's Personal Memory to Customer.

An individual may deliberately copy selected material from Personal Memory into a named organizational workspace after reviewing the exact material and confirming the transfer. Only the confirmed copy becomes Customer Content; the transfer does not grant continuing access to the source, surrounding context, or future memories.

Private Chat may read the individual's recorded Personal Memory in a read-only manner when the individual requests it. Private Chat prompts, responses, corrections, references, attachments, browsing activity, entity mentions, and inferred facts are not added to history or Personal Memory unless the individual expressly promotes selected material after reviewing it.

16. Workflow Intelligence

Ruzzler may analyze operational metadata to identify useful workflows, bottlenecks, automation opportunities, and successful configurations.

For example, Ruzzler may detect that a particular combination of agents improves an email-processing workflow.

Where content inspection is unnecessary, Ruzzler will not intentionally search private email bodies, private documents, or private Vault contents merely to generate workflow-efficiency reports.

Operational reporting may use appropriately minimized information such as: workflow type; sequence; tool usage; execution duration; success/failure signals; aggregate usage; model choice; configuration; and similar metadata.

17. APIs, Plugins, Agents, and Headless Use

Ruzzler may be connected to other software, services, devices, developer tools, or systems through APIs, plugins, SDKs, agents, or other interfaces.

Customers are responsible for authorizing connected systems and configuring appropriate permissions.

Automated agents may take unintended actions.

Customers should apply appropriate: scopes; approval requirements; access controls; rate limits; credential controls; and human review.

18. Self-Hosted Systems

Ruzzler may assist Customers in deploying self-hosted systems.

Unless otherwise agreed in writing, Customer remains responsible for Customer-controlled infrastructure, including: networks; operating systems; identity systems; backups; patching; credentials; physical security; connected services; and deployment configuration.

Self-hosting does not itself guarantee security, regulatory compliance, or elimination of all third-party costs.

19. Open-Source Components

Certain Ruzzler components may be offered under separate open-source or source-available licenses.

Where a specific component includes a separate license, that license governs that component to the extent of any conflict with these Terms.

Third-party open-source software remains subject to its applicable license.

20. Fees

Ruzzler may offer: negotiated contracts; subscriptions; prepaid plans; credits; usage-based billing; pay-as-you-go ("PAYG") billing; or combinations of these models.

Billing units may include model usage, tokens, API requests, compute, storage, tools, agents, workflow executions, bandwidth, or other disclosed units.

21. Payment Processing

Ruzzler currently uses Stripe for certain payment processing.

BEE RAD TECH may add, replace, or use additional payment processors.

Payment processors may process payment information under their own terms and privacy policies.

22. Refunds

Used or consumed portions of the Services are non-refundable except where applicable law requires otherwise.

Unused prepaid portions may be eligible for a prorated refund under the Billing, Cancellation & Refund Policy.

PAYG usage that has already been consumed is non-refundable.

23. AI Output and Refunds

The following do not by themselves create a right to a refund for consumed Services: dissatisfaction with AI output; disagreement with an answer; failure to obtain a desired result; insufficient prompting skill; workflow-design choices; failure to follow instructions; model limitations; or subjective usefulness.

Mandatory rights that cannot legally be waived remain unaffected.

24. Taxes

Customer is responsible for applicable taxes except taxes imposed on BEE RAD TECH's net income.

25. Account Security

Customers and users must safeguard: passwords; authentication methods; API keys; access tokens; model credentials; and connected-system credentials.

Unauthorized access should be reported promptly.

26. Acceptable Use

Customers and users must comply with the Ruzzler Acceptable Use Policy.

27. Suspension

BEE RAD TECH may suspend access where reasonably necessary because of: nonpayment; abuse; security threats; unlawful conduct; material breach; provider restrictions; risk to third parties; or threats to Ruzzler infrastructure.

Where practical, BEE RAD TECH may provide notice before suspension.

28. Termination

Customers may terminate Services in accordance with their plan, contract, order form, or account controls.

Termination does not cancel charges for Services already consumed.

29. Data After Termination

Unless otherwise required by law or contract, Customer Content associated with a terminated account may remain recoverable for up to 30 days.

After the recovery period expires, Ruzzler will target deletion from active production systems within 7 additional days, subject to technical limitations and lawful retention requirements.

Residual copies may remain in backups until scheduled rotation.

Further details appear in the Data Retention & Deletion Policy.

30. Privacy

Processing of personal information is governed by the Ruzzler Privacy Policy and, where applicable, the Enterprise Data Processing Addendum.

A Customer's commercial agreement, order form, payment, administrative role, or workplace policy cannot expand Customer access to an individual's Personal Memory beyond a specific individual-directed copy described in Section 15.

31. Confidentiality

BEE RAD TECH will apply reasonable safeguards to Customer confidential information consistent with applicable agreements.

Confidentiality obligations do not apply to information that: is lawfully public; was already lawfully known; is independently developed; is lawfully obtained from another source; or must legally be disclosed.

32. Intellectual Property

Except for Customer Content and third-party materials, BEE RAD TECH and its licensors retain rights in Ruzzler and its proprietary technology.

No ownership rights are transferred except as expressly stated.

33. Feedback

BEE RAD TECH may use voluntary suggestions and feedback to improve Ruzzler without compensation, provided doing so does not transfer ownership of Customer confidential information or independently developed Customer intellectual property.

34. Beta Features

Beta, preview, experimental, or research features may be incomplete, unstable, changed, or discontinued.

Customers should not rely on experimental functionality for critical operations without accepting that risk.

35. No Professional Advice

Ruzzler provides technical and operational assistance.

Unless a particular service expressly states otherwise, AI output is not a substitute for legal, medical, financial, accounting, engineering, cybersecurity, or other licensed professional judgment.

36. Disclaimer of Warranties

TO THE MAXIMUM EXTENT PERMITTED BY LAW, THE SERVICES ARE PROVIDED "AS IS" AND "AS AVAILABLE."

BEE RAD TECH DOES NOT WARRANT THAT: THE SERVICES WILL BE UNINTERRUPTED; AI OUTPUT WILL BE CORRECT; ALL SENSITIVE INFORMATION WILL BE DETECTED; MOSAIC MODE WILL PREVENT RECONSTRUCTION; VERIFICATION WILL ELIMINATE HALLUCINATIONS; OR THE SERVICES WILL MEET EVERY CUSTOMER OBJECTIVE.

37. Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW, BEE RAD TECH WILL NOT BE LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR LOST PROFITS, LOST REVENUE, LOSS OF GOODWILL, OR BUSINESS INTERRUPTION.

TO THE MAXIMUM EXTENT PERMITTED BY LAW, BEE RAD TECH'S AGGREGATE LIABILITY ARISING FROM THE SERVICES WILL NOT EXCEED AMOUNTS PAID OR PAYABLE BY CUSTOMER FOR THE AFFECTED SERVICES DURING THE TWELVE MONTHS BEFORE THE EVENT GIVING RISE TO THE CLAIM.

This limitation does not apply where applicable law prohibits it.

38. Indemnification

To the extent permitted by law, Customer will defend and indemnify BEE RAD TECH against third-party claims arising from: unlawful Customer use; Customer Content; infringement caused by Customer Content; unauthorized Customer-directed processing; or Customer's material breach of these Terms.

Negotiated enterprise terms control where inconsistent.

39. Governing Law

These Terms are governed by Florida law, without regard to conflict-of-law rules, except where mandatory law requires otherwise.

Unless otherwise agreed in writing, disputes will be heard in a court of competent jurisdiction located in Pasco County, Florida.

40. International Use

Customers are responsible for compliance with laws applicable to their jurisdiction, users, industry, and data.

Availability of Ruzzler in a jurisdiction does not mean every possible use is lawful there.

41. Export Controls and Sanctions

Ruzzler may not be used in violation of applicable export-control, sanctions, or trade laws.

42. Changes

BEE RAD TECH may update these Terms.

Material changes will be communicated as appropriate.

43. Order of Precedence

If these Terms conflict with a signed enterprise agreement, order form, or DPA, the specifically negotiated document controls for that subject matter.

44. Contact

BEE RAD TECH LLC

1936 Bruce B Downs Blvd, Suite 449, Wesley Chapel, FL 33543

Legal: legal@ruzzler.com

Support: support@ruzzler.com