Privacy Policy

Effective Date: August 22, 2026

This Privacy Policy explains how BEE RAD TECH LLC processes personal information in connection with Ruzzler and related services.

1. Scope

This Policy applies to Ruzzler, RuzzChat, RuzzCode, websites, applications, APIs, SDKs, plugins, hosted services, and related services.

Enterprise customers may also be subject to a separate Data Processing Addendum.

2. Roles

Depending on the situation, BEE RAD TECH may process personal information: for its own business purposes; or on behalf of a Customer under that Customer's instructions.

For Customer-controlled business data, the Customer typically determines why and how the information is used, while BEE RAD TECH provides the processing infrastructure.

3. Information We Collect

We may process the following categories.

Account information: name, business contact information, account identifiers, authentication information, organization, role, and account settings.

Customer Content: prompts, outputs, documents, code, files, workflows, instructions, and information submitted through connected systems.

Operational employee context: work role, business function, authorized workflow information, organizational relationships, tool usage, and other job-related information configured by Customer.

Document Vault information: documents and files intentionally placed in a private Vault.

Usage information: feature usage, model routing, execution events, workflow configuration, duration, failure signals, and other operational telemetry.

Device and network information: IP address, browser/device information, operating system, logs, and security telemetry.

Integration information: information necessary to connect authorized third-party services.

Billing information: plan, transaction, billing status, invoice, tax, and payment-related information. Payment-card data may be processed directly by Stripe or another processor.

Support information: communications with support, troubleshooting information, and related correspondence.

4. Sources

Information may come from: users; Customer administrators; connected systems; Customer-configured integrations; AI-generated workflows; Ruzzler system activity; payment providers; or security and authentication systems.

5. How We Use Information

We may use information to: provide Ruzzler; authenticate users; route AI workloads; operate RuzzChat and RuzzCode; store authorized documents; execute workflows and agents; provide verification; operate sanitization; operate Mosaic Mode; perform content-isolated workflow analytics; maintain organizational context; bill Customers; support users; maintain security; detect abuse; troubleshoot systems; comply with law; and improve Ruzzler consistent with contractual commitments.

6. Private Vaults

Personal Memory and private user Vaults are controlled by the individual, including when a Customer purchases, reimburses, provisions, or administers the individual's license. They are not Customer-controlled business data merely because the account is associated with an organization.

Customer administrators, managers, payers, workflow owners, support delegates, and other users cannot read, search, export, retain, place a Customer legal hold on, or direct processing of Personal Memory through their organizational role.

Personal Memory and Customer workspaces use separate authorization and cryptographic boundaries. Company workflows cannot retrieve Personal Memory. Removing a work account or managed-device work container does not transfer the individual's Personal Memory to Customer.

The individual may copy specifically selected material into a named Customer workspace only after reviewing and affirmatively confirming that item. The selected copy becomes Customer Content, but its source, surrounding context, and future memories remain private.

Private Chat may consult the individual's recorded Personal Memory in read-only mode. Private prompts, responses, attachments, browsing activity, corrections, references, inferred facts, recency signals, and derived summaries are not written to chat history, Personal Memory, indexes, caches, or training data unless the individual reviews and expressly promotes selected material. Content-free security and billing events may still be retained where necessary.

Nightly maintenance may organize and refresh recorded Personal Memory and user-approved files using incremental hashing, deduplication, and indexing. It excludes Private Chat and sources the individual has not approved.

7. Workflow Analytics

Ruzzler may analyze workflow metadata to identify effective automation patterns and operational opportunities.

Where private content is not necessary for that purpose, Ruzzler does not intentionally inspect private message bodies, private Vault documents, or similar private content merely to create workflow-efficiency reports.

Workflow analytics may instead use minimized operational signals.

8. Employee Information

Ruzzler's employee-related context is intended for operational and business-assistance purposes.

Ruzzler is not designed to make hiring, firing, compensation, promotion, discipline, or employment-eligibility decisions.

Customers are responsible for applicable employee notices, permissions, agreements, and workplace rules.

9. Sensitive Information and Sanitization

Ruzzler may use automated sanitization tools intended to identify and transform sensitive information before transmission to downstream systems.

The sanitizer may redact, tokenize, mask, substitute, or compartmentalize information.

No automated sanitizer is perfect.

Users should not intentionally submit sensitive information that is unnecessary for the applicable business purpose.

10. AI Providers

When a workflow requires an external model, Ruzzler may transmit necessary information to selected AI providers.

Those providers may include OpenAI, Anthropic, Google, and other providers supported by the platform.

The provider receiving data may vary by: Customer configuration; requested capability; routing; price; availability; verification needs; or technical requirements.

11. Model Training

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

Ruzzler does not intentionally send Customer Content to downstream providers for unrelated generalized training where the applicable Ruzzler service has represented that such training is disabled or excluded.

12. Service Providers and Subprocessors

We may use service providers for: cloud infrastructure; AI processing; authentication; communications; monitoring; support; billing; security; analytics; and related technical functions.

Enterprise Customers may receive additional subprocessor information under the DPA.

13. Payment Processing

Stripe currently processes certain payments for Ruzzler.

BEE RAD TECH may add or replace payment processors.

Payment processors process information according to their own legal terms and privacy practices.

14. Selling Personal Information

BEE RAD TECH does not sell private Customer Content or private employee Vault contents.

BEE RAD TECH does not use such content for cross-context behavioral advertising.

15. Cookies and Similar Technologies

Ruzzler websites may use cookies or similar technologies necessary for: authentication; security; preferences; functionality; performance; and legally permitted analytics.

Where required, Ruzzler will provide appropriate cookie choices.

16. Data Security

Ruzzler uses administrative, technical, and organizational safeguards intended to protect information.

Additional information appears in the Security & Data Protection Policy.

No online service can guarantee absolute security.

17. Retention

Ruzzler retains information according to the Data Retention & Deletion Policy, Customer configuration, contractual requirements, business needs, and applicable law.

For terminated accounts, Customer Content may ordinarily remain recoverable for up to 30 days and then be targeted for deletion from active production systems within 7 additional days.

Backups may require additional time to rotate.

18. International Transfers

Ruzzler is operated by a U.S. company and may process information in the United States or other countries where authorized subprocessors operate.

Where legally required, BEE RAD TECH will use appropriate transfer safeguards.

19. Privacy Rights

Depending on applicable law, individuals may have rights to: access information; correct information; delete information; obtain a copy; restrict certain processing; object to certain processing; withdraw consent; appeal certain privacy decisions; or lodge a complaint with a regulator.

Where Ruzzler processes information on behalf of a Customer, requests concerning Customer-controlled data may need to be directed to that Customer.

20. U.S. State Privacy Rights

Residents of certain U.S. states may have additional rights under applicable state privacy laws.

BEE RAD TECH will honor rights that apply to the relevant processing and individual.

21. EEA, UK, and Similar Jurisdictions

Where GDPR, UK GDPR, or similar laws apply, processing may rely on an appropriate legal basis such as: performance of a contract; legitimate interests; legal obligations; or consent where required.

For Customer-controlled processing, the Customer ordinarily determines the underlying legal basis.

22. Children

Ruzzler is intended for business and professional use and is not directed to children.

Users under the applicable age of digital consent should not independently use Ruzzler unless an authorized and lawful arrangement expressly permits it.

23. Security Incidents

BEE RAD TECH will respond to security incidents in accordance with its contractual and legal obligations.

Enterprise obligations may be further addressed by the DPA.

24. Corporate Transactions

Information may be transferred in connection with a merger, acquisition, financing, reorganization, or sale of relevant business assets, subject to applicable law and confidentiality obligations.

25. Legal Requests

Customer administrators and payers have no special access to Personal Memory for investigations, employment matters, legal holds, or similar organizational purposes.

BEE RAD TECH may preserve or disclose information only when reasonably necessary to comply with binding legal process or applicable law, or to protect users and the Service from fraud, abuse, or security threats. Ruzzler will seek to narrow requests and notify the affected individual before disclosure when legally permitted.

26. Changes

We may update this Policy to reflect changes in law, technology, or the Services.

27. Contact

Privacy requests: privacy@ruzzler.com

Legal: legal@ruzzler.com

BEE RAD TECH LLC

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