Legal

    Privacy Policy

    Last updated: April 4, 2026

    Document Assumptions

    This document assumes the following product structure. If the product or license model changes before launch, update these sections before publication.

    Product surfaceDefault data flowCommercial / license position
    MartinLoop CoreRuns locally by default and does not send data to MartinLoop servers unless you connect it to the managed product or separately enable an optional hosted service or integration.Open-source component released under the Apache License 2.0.
    Managed MartinLoop productProcesses account, workspace, runtime, billing, analytics, and optional consent-governed intelligence data as described in this document.Proprietary hosted service with subscription-based features and optional paid tiers.
    Website and waitlistCollects website, cookie, contact, and marketing information as described below.Proprietary website and commercial operations surface.

    1. Scope and Who This Policy Applies To

    This Privacy Policy describes how MartinLoop collects, uses, discloses, stores, secures, and otherwise processes information when you use the MartinLoop website, waitlist, open-source MartinLoop Core, hosted MartinLoop services, dashboards, APIs, support channels, pilot programs, or related commercial offerings (collectively, the "Services").

    This policy is intended to cover three different contexts: (a) the MartinLoop website and marketing surfaces, (b) the managed MartinLoop hosted product, and (c) the MartinLoop Core open-source component when it is distributed, downloaded, or connected to hosted services. The Core may run locally without transmitting data to MartinLoop unless you connect it to hosted services, enable integrations, or otherwise choose to send data to us.

    Additional notices, product settings, enterprise agreements, pilot terms, data processing addenda, or benchmarking disclosures may apply to specific products, environments, customers, or regions. Where those documents conflict with this policy for a specific deployment or customer relationship, the more specific document will control to the extent of that conflict.

    2. Information We Collect

    We may collect the following categories of information, depending on how you use the Services and the choices you make in your settings.

    • Account and contact information, such as name, work email address, company name, billing contact details, account credentials, team and workspace configuration, and communications preferences.
    • Website and marketing information, such as information you submit through waitlist forms, demo requests, newsletter signups, surveys, or event registrations, as well as technical information collected through standard website logs and cookies.
    • Customer runtime and workspace information, such as workspace identifiers, project metadata, service configuration, run and attempt metadata, budget envelopes, routing selections, rollback outcomes, grounding artifacts, safety or policy artifacts, audit records, feature-gate settings, and related service-operation telemetry for the managed product.
    • Customer content and operational artifacts you choose to process through the managed product or support channels, which may include prompts, outputs, code, logs, documents, run artifacts, support files, or other data necessary to operate the Service, diagnose incidents, or provide agreed functionality. We do not use raw customer content for cross-customer aggregate intelligence by default; see Sections 5 and 6 below.
    • Billing and commercial information, such as subscription plan, invoices, payment status, transaction records, and commercial relationship data. Payment card information is typically processed by our payment processors and not stored by MartinLoop except for limited billing metadata.
    • Support and diagnostics information, such as support tickets, crash reports, troubleshooting notes, temporary diagnostic captures, and incident-response materials. Where offered, enhanced support diagnostics should be separately enabled, time-bounded, and auditable.
    • Optional product-intelligence, benchmarking, or contribution data, but only to the extent you separately enable relevant settings, grant consent where required, or otherwise agree to participate. These optional uses are described in Sections 5 and 6.

    3. Sources of Information

    We collect information directly from you, from your users or administrators acting on your behalf, from your use of the Services, from devices and browsers interacting with the website or managed product, from service providers and subprocessors that help us operate the Services, and from integrations or APIs you connect to MartinLoop.

    If you use the open-source Core entirely locally and do not connect it to a MartinLoop hosted service or other data-sharing path, MartinLoop may not receive any runtime data from that local use.

    4. How We Use Information

    We use information to provide, operate, secure, maintain, support, bill for, and improve the Services; to authenticate users and manage accounts; to provide dashboards, analytics, and read-model outputs; to investigate incidents, fraud, misuse, and safety issues; to comply with law and enforce our agreements; and to communicate with you about the Services.

    Where permitted and appropriate, we may also use information for product analytics, service reliability, customer support, service planning, and internal business operations. When we rely on consent for a particular use, you can withdraw that consent as described below.

    5. Optional Product Intelligence, Benchmarking, and Data Contribution

    The managed MartinLoop product may offer optional settings that allow a customer to contribute certain information to cross-customer product intelligence, benchmarking, or other advanced programs. These optional paths should be separately controlled in product settings and are not required to use the core hosted product.

    By default, MartinLoop should rely on service-operation data needed to run the product for your own workspace. Optional cross-customer intelligence paths should be treated as separate scopes, for example: aggregate product intelligence, benchmarking participation, advanced artifact contribution, support diagnostics grants, and any future model-improvement contribution program.

    Unless we clearly disclose otherwise and obtain any required consent, our aggregate product-intelligence use should be limited to normalized, scrubbed metadata and outcomes such as task class, route or model selected, cost and token bands, timing bands, failure families, and rollback rates.

    6. Consent, Legal Bases, and Your Choices

    Depending on your location and the nature of the processing, we may rely on one or more lawful bases or legal grounds such as performance of a contract, legitimate interests, legal obligations, or consent. Where we rely on consent, we intend that consent requests be specific, understandable, and reasonably easy to withdraw.

    Within the managed product, we may provide settings and controls for service-operation analytics, aggregate product intelligence, benchmarking participation, advanced artifact contribution, model-improvement contribution, support diagnostics, and related data uses. Those settings should show the current state, the effective date, and, where appropriate, the actor who changed the setting.

    Withdrawing consent or disabling a setting should apply prospectively to the affected processing path, subject to technical feasibility, applicable law, contractual commitments, legal retention requirements, and our need to preserve records of consent, billing, security, and service operation.

    7. Cookies and Similar Technologies

    We may use essential cookies and similar technologies necessary to operate the website or hosted Services, remember basic preferences, authenticate sessions, secure the Services, and measure service performance. Where required by law, we will seek consent for non-essential cookies or similar technologies.

    We do not use third-party advertising cookies for cross-context behavioral advertising as part of the core MartinLoop product experience. If that position changes, we will update this policy and any related consent flows before such processing begins.

    8. How We Share Information

    We may disclose information to service providers and subprocessors that help us operate the Services, including providers for cloud infrastructure, authentication, payment processing, customer communications, support, error monitoring, analytics, logging, and security operations, subject to appropriate contractual and security controls.

    We may also disclose information to professional advisors, auditors, financing or transaction counterparties, or competent authorities where required to comply with law, defend legal claims, or protect our rights or the rights of others.

    9. International Transfers

    Your information may be processed in countries other than the country where you reside, including in countries that may have different data-protection standards. Where required by law, we will implement appropriate transfer mechanisms or safeguards for such transfers.

    10. Data Security

    We use reasonable and appropriate technical, organizational, and administrative safeguards designed to protect information against unauthorized access, loss, misuse, alteration, or disclosure. These safeguards may include encryption in transit and at rest where appropriate, access controls, logging, segmentation, secret-management practices, secure development practices, and incident-response procedures.

    No system is perfectly secure, and we cannot guarantee absolute security. You are also responsible for securing your accounts, credentials, environments, and deployment choices.

    11. Data Retention

    We retain information for as long as reasonably necessary to provide the Services, maintain security and business records, resolve disputes, enforce agreements, comply with law, honor retention settings or enterprise commitments where applicable, and support legitimate operational needs.

    Retention periods may vary by category. For example, account and billing records may be retained longer than transient service logs, pilot diagnostics may be time-bounded, and consent history may need to be preserved to demonstrate what choices were made and when. If we offer configurable retention settings, those settings may affect certain categories but not all categories of data.

    12. Your Rights and Choices

    Depending on your location and applicable law, you may have rights to access, know, correct, update, delete, restrict, object to, or export certain personal information; to withdraw consent where processing is based on consent; to opt out of certain disclosures or uses; and to appeal or complain to a regulator. We will consider and respond to requests in accordance with applicable law.

    You may also opt out of marketing emails by using the unsubscribe link in those messages or by contacting us. Service-related and transactional communications may still be sent where necessary.

    13. Children

    The Services are not directed to children, and we do not knowingly collect personal information from children in violation of applicable law. If you believe a child has provided personal information in connection with the Services, contact us so we can take appropriate action.

    14. Changes to This Policy

    We may update this Privacy Policy from time to time. If we make material changes, we will post the updated policy with a revised "Last updated" date and, where required by law or appropriate for the nature of the change, provide additional notice through the Services or by email.

    15. Contact Us

    For privacy questions, requests, or complaints, contact: help@martinloop.com.

    Optional Managed-Product Data-Use Controls

    Draft product model

    Setting / scopeRecommended defaultWhat it covers
    Service operation analyticsOnData needed to operate the hosted product for the customer's own workspace and account.
    Aggregate product intelligenceOffScrubbed, normalized metadata and outcome facts used to improve routing, failure handling, and product recommendations.
    Benchmark participationOffInclusion of eligible scrubbed metrics in cohort-based comparisons and benchmark views.
    Advanced artifact contributionOffAny deeper artifact-derived analytics beyond default normalized metadata and outcomes.
    Model improvement contributionOffAny future training or model-improvement contribution program; separate from benchmarking and product analytics.
    Support diagnostics grantOff / time-boundedTemporary expanded diagnostics for support or incident investigation, recorded and auditable.