Privacy Policy

1. Shared Responsibility Model

• Customers are generally responsible for the business data they place into Nexus, the purposes for which they use Nexus, and the legal basis for that use.
• Marcoby is generally responsible for the Nexus software, security of the services Marcoby operates, support operations, billing, and legal compliance for Marcoby's own business records.
• When Nexus is deployed in a customer-controlled environment, Marcoby aims to minimize direct access to customer content and to act only on documented customer instructions where applicable.

2. Information Marcoby Collects Directly

• Website and account information, such as names, email addresses, company names, billing contacts, and account metadata.
• Support and communications data, including emails, meeting notes, support tickets, and implementation requests.
• Operational and security data, such as logs, device/browser details, IP addresses, authentication events, and service health telemetry for Marcoby-operated systems.
• Payment, invoicing, and commercial records needed to sell, provision, and support Nexus.

3. Customer Environment Data

• Customer content stored and processed inside a customer-controlled deployment is generally controlled by the customer, not Marcoby.
• If Marcoby does not receive or access that content, Marcoby may have no direct role in processing that specific data.
• If Marcoby provides hosting, managed services, support access, troubleshooting, backups, or AI routing that involve customer content, Marcoby may process that content on the customer's behalf under applicable contractual terms.

4. How Marcoby Uses Information

• Operate and secure the Nexus website, customer accounts, and Marcoby-managed services.
• Provide onboarding, implementation, technical support, customer success, and service communications.
• Prevent abuse, investigate incidents, enforce agreements, and comply with legal obligations.
• Invoice customers, maintain business records, and administer commercial relationships.

5. AI Processing and Deployment Choices

• Nexus may use AI-assisted features for drafting, summarization, workflow assistance, and business analysis.
• Where Nexus is configured to run inside a customer environment, the customer is responsible for deciding what information is submitted to those features and which model providers or infrastructure are used.
• Nexus uses an AI gateway (OpenClaw) to route requests to AI model providers configured by the customer or deployment administrator. Marcoby does not own or operate AI model infrastructure and does not intermediate the processing of prompts or responses. Customers should review the terms and privacy policies of their configured model providers.
• AI outputs can be inaccurate, incomplete, or unsuitable for a particular use, and should be reviewed before reliance.
• Additional details about our disclosure approach are available in the AI Transparency Notice.

6. Knowledge & Memory

Nexus is designed to build a persistent understanding of your business over time. As part of its core function, Nexus may automatically extract and store structured information from your conversations — including facts, named entities (such as people, projects, goals, and decisions), summaries, and synthesized insights — within your deployment environment. This stored knowledge is used to provide continuity and context in future sessions. This data remains within your controlled environment and is not accessed by Marcoby.

7. Legal Roles

• For customer-controlled business data, the customer is typically the primary controller or business, and Marcoby's role depends on the specific services Marcoby provides.
• For billing, support, security, contract administration, and Marcoby's own website/account records, Marcoby generally acts as an independent controller or business.
• Role allocation may be further described in an order form, data processing addendum, managed services agreement, or other written contract.

8. Sharing of Information

• With infrastructure, communications, support, payment, analytics, and security providers used to run Marcoby's own operations.
• With subprocessors or service providers involved in managed Nexus deployments or support engagements, subject to applicable contracts and safeguards.
• With integrations and providers selected or authorized by the customer.
• When required by law, valid legal process, or to protect rights, safety, property, or service integrity.

9. Cookies, Analytics, and Logs

Marcoby uses essential cookies and similar technologies for authentication, security, and core website functions. Marcoby may also use analytics and diagnostic tools for the Nexus website and Marcoby-operated services. Customers remain responsible for analytics, logging, and retention decisions inside their own deployments unless Marcoby separately manages those functions.

10. Data Retention

Marcoby retains information for as long as reasonably necessary to provide services, comply with law, resolve disputes, maintain security, and support legitimate business records. Retention periods differ between Marcoby-controlled commercial/support data and customer-controlled operational data. Customers are generally responsible for retention choices inside customer-controlled deployments.

11. Security

Marcoby uses administrative, technical, and organizational safeguards designed to protect the systems and information Marcoby controls, including access controls, encrypted transport, logging, and operational monitoring. Customers remain responsible for securing their own environments, administrators, and connected third-party services unless Marcoby expressly agrees to manage those controls.

12. Regional Rights

Depending on your location and the specific processing activity, you may have rights to access, correct, delete, export, restrict, or object to the processing of personal information. Requests relating to Marcoby-controlled data may be sent to the contacts below. Requests relating to customer-controlled Nexus deployments should usually be directed to the customer that controls that deployment.

13. Cross-Border Processing

Marcoby and its providers may operate from the United States and other countries. If Marcoby processes information across borders, Marcoby will use appropriate contractual or legal safeguards where required. Customers remain responsible for cross-border processing choices inside customer-controlled deployments unless Marcoby separately manages that infrastructure.

14. Changes to This Policy

We may update this Privacy Policy from time to time. We will post the revised version on this page and update the effective date above. If a change is material, we may provide additional notice through the service or by email.

15. Third-Party Platform Data and OAuth (Google, Microsoft, GitHub, Slack, etc.)

Nexus uses OAuth to access data from your authorized third-party accounts (such as Google Workspace, Microsoft 365, GitHub, HubSpot, or Slack) solely to provide the personalized AI coordination and automation features described on our website.

• Limited Use: We only access, store, or use third-party user data for the purpose of fulfilling your explicit requests via the Nexus interface.
• No Transfers for Advertising: We do not transfer third-party user data to other entities for the purpose of serving ads or building profiles for advertising.
• No Foundation Model Training: Your private third-party data is not used to train foundation models or improve non-Nexus-specific AI services.
• Compliance: Our use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
• AI Processing: When you direct Nexus to use data from your connected accounts, that data may be included in prompts sent to your configured AI model provider to fulfill your request. This occurs at your direction and is governed by that provider's terms. Marcoby does not retain copies of this data beyond what is stored in your deployment environment.

16. Contact

• Email: [email protected]
• Legal: [email protected]
• We will respond to verified requests relating to Marcoby-controlled data as required by applicable law.