Legal

MATHILDE Master Terms of Service

Draft status: template for Swiss counsel review and factual completion.

These Master Terms of Service (Terms) govern the provision of the MATHILDE services by Mathilde Sagl, a company organized under the laws of Switzerland with its registered seat at [Registered Seat] (Company), to the customer identified in the applicable Order Form (Customer).

These Terms are drafted for business-to-business use only.

1. Contract Structure

1.1 Contract Stack

The agreement between Company and Customer consists of:

  1. the applicable Order Form
  2. the applicable Product Schedule
  3. these Terms
  4. the Acceptable Use Policy
  5. the Data Processing Addendum, if applicable
  6. the Support or SLA document, if expressly incorporated

1.2 Order Of Precedence

In the event of a conflict, the following order applies:

  1. Order Form
  2. Product Schedule
  3. Data Processing Addendum, for personal-data-processing issues only
  4. Support or SLA document, for support issues only
  5. these Terms
  6. Acceptable Use Policy

Marketing materials, demos, presentations, and informal correspondence are descriptive only and do not create independent warranties unless expressly incorporated in an Order Form.

2. Definitions

For purposes of these Terms:

  • Affiliate means an entity that directly or indirectly controls, is controlled by, or is under common control with a party.
  • Authorized User means an employee or individual contractor of Customer or an approved Affiliate who is authorized by Customer to access the Services within the licensed scope.
  • Customer Data means data, materials, and content provided by Customer to the Company for account administration, support, integration, or another expressly authorized purpose. Customer Data does not include Outputs.
  • Derived Data means any dataset, calculation, transformation, enrichment, score, benchmark, model artifact, or other output generated from or using the Services, Outputs, or Documentation.
  • Documentation means the materials that Company expressly designates as part of the contractual service documentation in the applicable Order Form or Product Schedule.
  • Internal Work Product means internal reports, memoranda, dashboards, notes, analyses, and internal decision-support materials created by Customer using the Services or Outputs, provided they are used only internally and do not enable third parties to reconstruct or economically substitute for the Services or Outputs.
  • Order Form means the ordering document or other written commercial document executed or accepted by the parties that references these Terms.
  • Outputs means the data, measurements, files, documents, results, or other service outputs made available by Company through the licensed Services.
  • Product Schedule means the product-specific annex describing the measured object, interfaces, supported constraints, and other product-specific contractual semantics.
  • Services means the MATHILDE services identified in the applicable Order Form and Product Schedule.

3. B2B-Only Eligibility

3.1 Business Use Only

The Services are offered only to businesses, professional users, institutions, funds, corporates, family offices, research organizations, and other non-consumer customers acting in a professional capacity.

3.2 Authority

The individual accepting or signing the Order Form represents that they have the authority to bind Customer to the Agreement.

4. Nature Of The Services

4.1 Measurement And Technology Service

The Services are information, measurement, documentation, and technology services.

The Services are not:

  • investment advice
  • discretionary portfolio management
  • brokerage
  • execution advice
  • a trading venue
  • a solicitation or recommendation to buy, sell, or hold any asset
  • a fiduciary service

4.2 Measurement, Not Prediction

MATHILDE measures market structure and market state. It does not predict future market outcomes and does not assume responsibility for Customer decisions based on the Services or Outputs.

4.3 Product Semantics

Customer acknowledges that the Services may include:

  • stable-boundary rules
  • correction, recompute, and restatement rules
  • product-specific constraints on timeframes, selectors, or delivery methods

Those rules are part of the product contract and are described in the applicable Product Schedule and Documentation.

5. License Grant

5.1 Limited License

Subject to Customer’s compliance with the Agreement and payment of all applicable fees, Company grants Customer a limited, non-exclusive, non-transferable, non-sublicensable right during the applicable term to access and use the Services, Outputs, and Documentation solely:

  1. within the scope stated in the Order Form
  2. for Customer’s own internal business purposes
  3. through Authorized Users

5.2 No Implied Rights

All rights not expressly granted are reserved by Company and its licensors.

6. Use Restrictions

6.1 General Restrictions

Customer must not, and must not permit any third party to:

  1. sell, resell, license, sublicense, lease, rent, assign, distribute, publish, display, transmit, outsource, white-label, or otherwise make the Services, Outputs, Documentation, or credentials available to any third party
  2. use the Services, Outputs, or Documentation to create, power, support, verify, improve, or commercialize any external-facing or third-party-facing product or service that materially incorporates, depends on, reproduces, or economically substitutes for MATHILDE
  3. expose raw Outputs, bulk Outputs, or substantially similar derived outputs in any form that allows a third party to reconstruct, replicate, or economically substitute for MATHILDE
  4. create, publish, license, or commercialize any benchmark, index, ranking, pricing feed, signal feed, model service, or data service derived from MATHILDE unless expressly licensed
  5. use the Services as a substitute license for any affiliate, client, counterparty, vendor, or other third party not expressly covered by the Order Form
  6. reverse engineer, decompile, disassemble, or otherwise attempt to derive source code, hidden methodology, private operational rules, or non-public system behavior except to the extent such restriction is prohibited by mandatory law
  7. bypass or attempt to bypass service boundaries, access controls, rate limits, watermark gates, or other technical restrictions
  8. use the Services in violation of law, regulation, sanctions, or court order

6.2 AI And Model Restrictions

Unless expressly licensed in the Order Form or Product Schedule, Customer must not use the Services, Outputs, or Documentation to:

  1. train, pre-train, fine-tune, or improve any general-purpose model, foundation model, or external-facing model
  2. benchmark models for external commercialization
  3. create or improve any third-party-facing model, agent, or automated system that materially incorporates or substitutes for the Services

Internal analytical use that does not violate the restrictions above may be permitted only within the licensed scope.

For clarity, authorized internal use through Company-provided machine-readable access layers, including MCP, APIs, SDKs, and licensed files workflows, is part of permitted internal analytical use and does not by itself constitute training, pre-training, fine-tuning, or model improvement.

6.3 Contractual Penalties For High-Value Misuse

Customer acknowledges that breaches of the restricted-use, confidentiality, trade-secret, redistribution, and anti-substitution obligations may cause harm that is difficult to quantify precisely in ordinary damages.

Accordingly, subject to applicable Swiss law, Customer agrees to pay the following contractual penalties (Konventionalstrafen) to Company for each separate breach:

  1. CHF 150,000 per critical commercialization breach, including:
    • resale
    • redistribution
    • sublicensing
    • white-labeling
    • commercial publication or external exposure of Outputs in breach of the Agreement
    • creation, sale, or external operation of a substitutive API, benchmark, index, analytics, signal, model, or similar product materially based on MATHILDE
  2. CHF 100,000 per prohibited AI or model-training breach, including use of the Services, Outputs, or Documentation to train, fine-tune, improve, or commercialize an external-facing model, agent, or model service in breach of the Agreement
  3. CHF 50,000 per access, scope, or circumvention breach, including:
    • credential sharing
    • unauthorized affiliate use
    • unauthorized third-party access
    • unauthorized entity-scope expansion
    • quota, rate-limit, watermark, or access-control circumvention
  4. CHF 150,000 per confidentiality or trade-secret misuse involving non-public MATHILDE technical, commercial, product, methodology, or security information

For continuing breaches that remain uncured after written notice from Company, Customer will also owe CHF 10,000 per day for each day the breach continues, in addition to the applicable one-time penalty above.

Each separate prohibited act, third-party enablement, deployment, external publication, commercial offering, or other commercially distinct misuse event may constitute a separate breach.

Unless mandatory law requires otherwise, payment of a contractual penalty does not release Customer from:

  1. its obligation to cease the breaching conduct immediately
  2. its obligation to perform any remaining contractual duties
  3. Company’s right to suspend or terminate access
  4. Company’s right to seek injunctive or other equitable relief
  5. Company’s right to claim larger provable damages where the Agreement and applicable law permit such recovery

7. Derived Data And Internal Work Product

7.1 Internal Work Product

Subject to the Agreement, Customer may create Internal Work Product for its own internal business purposes.

7.2 Ownership Boundary

As between the parties:

  1. Customer owns its Customer Data and Internal Work Product
  2. Company owns the Services, Outputs, Documentation, and all Company intellectual property embodied in them

7.3 No External Commercialization Of Substitutive Derivatives

Customer may not commercialize, publish, license, or otherwise make available to third parties any Derived Data or Internal Work Product that:

  1. materially reproduces or exposes Outputs
  2. allows third parties to reconstruct Outputs
  3. functions as a substitute for the Services
  4. is marketed as a benchmark, index, dataset, analytics feed, or similar product based on MATHILDE

unless such rights are expressly granted in the Order Form.

8. Accounts, Credentials, And Users

Customer is responsible for:

  1. all activities conducted through its accounts and credentials
  2. ensuring that only Authorized Users access the Services
  3. maintaining the confidentiality and security of credentials
  4. promptly revoking access when no longer needed
  5. notifying Company without undue delay of any suspected unauthorized access or credential compromise

Customer is responsible for ensuring that its Authorized Users and contractors comply with the Agreement.

9. Customer Responsibilities

Customer is solely responsible for:

  1. its business decisions, investment decisions, trading decisions, treasury decisions, risk decisions, and operational decisions
  2. assessing whether the Services are suitable for its intended use
  3. validating the appropriateness of any downstream use in its own environment
  4. compliance with laws applicable to Customer’s own activities

Customer must not represent that Company is responsible for Customer’s financial or commercial decisions.

10. Product Changes, Methodology Changes, And Corrections

10.1 Product Evolution

Company may modify the Services, interfaces, schemas, methodologies, documentation, and operational processes from time to time.

If a change is materially adverse and breaking, Company will provide the notice stated in the applicable Product Schedule or Order Form, unless earlier change is reasonably required for security, legality, integrity, or urgent operational reasons.

10.2 Corrections And Restatements

Customer acknowledges that the product contract may lawfully permit:

  • corrections
  • recomputes
  • restatements
  • withdrawals
  • file republishes
  • metadata or diagnostics changes

where the product methodology or upstream truth contract so requires.

10.3 No Finality Assumption Beyond The Product Contract

Unless the applicable Product Schedule expressly states otherwise, row existence or payload existence does not by itself represent the strongest possible finality state under the product methodology.

11. Fees, Invoicing, And Payment

11.1 Fees

Customer will pay all fees stated in the applicable Order Form.

11.2 Taxes

Fees are exclusive of VAT, sales tax, withholding tax, or similar taxes unless the Order Form expressly states otherwise. Customer is responsible for all such taxes except taxes based on Company’s net income.

11.3 Invoicing And Payment Terms

Unless the Order Form expressly states otherwise:

  1. the initial commercial commitment for paid plans is 12 months
  2. paid plans are billed monthly in advance by credit card or another supported payment method through the customer account page
  3. recurring charges are due immediately on the applicable billing date
  4. Customer may change plan or tier during the term through the customer billing interface or another Company-approved process
  5. if Customer remains on the same subscribed tier during the current annual term, Company price increases for that tier do not apply until the next renewal term
  6. if Company lowers the then-current price for the same subscribed tier during the current annual term, the lower price applies prospectively from the next billing cycle after the reduction takes effect
  7. if Customer changes tier during the term, the then-current price for the new tier applies from the effective date of the change and system proration or credit adjustments may apply
  8. except where mandatory law requires otherwise or Company expressly agrees in writing, fees are non-cancelable and non-refundable, including in cases of non-use, late non-renewal notice, or voluntary termination after the applicable renewal deadline

If Company agrees to invoice outside the self-serve recurring card flow, the invoice due date and payment window will be stated in the applicable Order Form.

11.4 Late Payment

Without prejudice to other remedies, overdue amounts may accrue default interest at 5% per annum or, if mandatory applicable law requires another rate, that mandatory rate.

11.5 Suspension For Non-Payment

Company may suspend access for material non-payment after reasonable notice, unless the relevant invoice is disputed in good faith and Customer is cooperating to resolve that dispute.

12. Intellectual Property

12.1 Company IP

Company and its licensors retain all right, title, and interest in and to the Services, Outputs, Documentation, methodologies, software, schemas, branding, and related intellectual property, including all improvements and modifications.

12.2 Feedback

If Customer provides feedback, suggestions, or proposed improvements, Company may use them without restriction or compensation, provided Company does not thereby acquire rights in Customer Confidential Information beyond what is necessary to use such feedback.

13. Confidentiality

13.1 Confidential Information

Each party (Receiving Party) must protect the other party’s (Disclosing Party) Confidential Information using at least reasonable care and must use it only for purposes of the Agreement.

Confidential Information includes:

  • non-public commercial terms
  • credentials
  • security information
  • non-public technical information
  • non-public product information
  • customer data
  • trade secrets

13.2 Exclusions

Confidential Information does not include information that the Receiving Party can prove:

  1. is or becomes public through no breach of the Agreement
  2. was lawfully known to it without confidentiality obligation
  3. is lawfully received from a third party without confidentiality obligation
  4. is independently developed without use of the Disclosing Party’s Confidential Information

13.3 Required Disclosure

The Receiving Party may disclose Confidential Information where required by law, regulation, or court order, provided it gives advance notice where legally permitted and reasonably cooperates on protective measures.

13.4 Confidentiality Misuse And Contractual Penalties

Unauthorized disclosure, exploitation, or external use of Confidential Information may also trigger the contractual penalties stated in Section 6.3 where the relevant conduct falls within that section.

14. Data Protection

14.1 Independent Controller Processing

Company may process personal data as an independent controller for:

  • account administration
  • entitlement management
  • billing
  • security
  • abuse detection
  • compliance
  • support operations
  • business continuity

as described in the Privacy Notice.

14.2 Processor Scenarios

If Company processes personal data on behalf of Customer in a processor role, the Data Processing Addendum applies.

14.3 Privacy Notice

Customer acknowledges that Company’s independent-controller processing is described in the Privacy Notice.

15. Support And Security

Company will provide the support and service commitments, if any, expressly stated in the Order Form or applicable support schedule.

Unless expressly stated otherwise:

  • no particular uptime percentage is promised
  • no particular recovery objective is promised
  • no service credits apply

16. Warranties

16.1 Limited Service Warranty

Company warrants that during the applicable term the Services will materially conform to the binding Documentation identified in the Agreement.

16.2 Exclusive Remedy

If Company breaches the warranty above and Customer gives reasonably detailed notice within 30 days after Customer discovers the issue and, in any event, no later than 60 days after the relevant event, Company will, as Customer’s sole and exclusive remedy:

  1. use commercially reasonable efforts to correct or reperform the affected Services
  2. if correction or reperformance is not reasonably achievable, provide the remedy expressly stated in the Order Form or SLA, if any
  3. if no such remedy exists and the breach is material and uncured, permit Customer to terminate the affected Order Form and receive a pro rata refund of prepaid unused fees for the terminated remainder

17. Disclaimers

Except as expressly stated in the Agreement, the Services, Outputs, and Documentation are provided as is and as available.

To the maximum extent permitted by applicable law, Company disclaims all other warranties, whether express, implied, statutory, or otherwise, including warranties of merchantability, fitness for a particular purpose, non-infringement, uninterrupted availability, and error-free operation.

Without limiting the foregoing, Company does not warrant that:

  1. the Services are suitable for Customer’s strategy, business model, or use case
  2. any Output will be complete, uninterrupted, or never corrected
  3. any Output will lead to any financial or commercial outcome
  4. the Services constitute advice, recommendation, or a regulated financial service

18. Indemnities

18.1 Customer Indemnity

Customer will defend, indemnify, and hold harmless Company and its officers, directors, employees, and agents against third-party claims arising from:

  1. Customer’s breach of the Agreement
  2. Customer’s unlawful use of the Services
  3. Customer’s external commercialization, redistribution, or substitution use in breach of the Agreement
  4. Customer’s downstream products, decisions, publications, or services based on the Services or Outputs

18.2 No Company Indemnity Unless Expressly Granted

Company does not grant any indemnity to Customer, including any intellectual property infringement indemnity, unless such indemnity is expressly stated in the applicable Order Form or another document expressly incorporated there.

19. Limitation Of Liability

19.1 Excluded Losses

To the maximum extent permitted by applicable law, neither party will be liable for any:

  • indirect loss
  • consequential loss
  • incidental loss
  • punitive loss
  • exemplary loss
  • loss of profits
  • loss of revenue
  • loss of business opportunity
  • loss of anticipated savings
  • loss resulting from Customer trading, investment, or treasury decisions

whether based in contract, tort, statute, or otherwise, even if advised of the possibility.

19.2 Liability Cap

To the maximum extent permitted by applicable law, each party’s aggregate liability arising out of or in connection with the Agreement will not exceed:

  • the fees paid or payable by Customer under the affected Order Form during the 12 months preceding the first event giving rise to liability

19.3 Carve-Outs

The exclusions and cap above do not apply to the extent prohibited by mandatory law and do not limit liability for:

  1. unlawful intent
  2. gross negligence, to the extent exclusion or limitation is prohibited by mandatory applicable law, including Article 100 CO where applicable
  3. unpaid fees owed by Customer
  4. breach of confidentiality or misuse of intellectual property, if the final negotiated position provides a separate cap or carve-out
  5. contractual penalties owed by Customer under Section 6.3

[Confirm final carve-outs with Swiss counsel.]

20. Suspension

Company may suspend or restrict access immediately, in whole or in part, if it reasonably believes that:

  1. Customer is breaching the Agreement
  2. Customer use presents security, legal, regulatory, or operational risk
  3. continued service may expose Company, other customers, or third parties to material harm
  4. Customer has materially failed to pay undisputed fees

Where reasonably practicable, Company will provide notice.

21. Term And Termination

21.1 Term

The Agreement starts on the effective date of the applicable Order Form and continues for the term stated there unless terminated earlier.

Unless the Order Form expressly states otherwise:

  1. the initial term is 12 months
  2. each Order Form renews automatically for successive 12-month periods
  3. Customer must give written non-renewal notice at least 3 months before the end of the then-current term to prevent renewal

21.2 Termination For Cause

Either party may terminate an affected Order Form or the Agreement for cause if the other party materially breaches the Agreement and:

  1. for non-payment of undisputed fees, fails to cure within 10 days after notice
  2. for any other material breach, fails to cure within 20 days after notice unless the breach is incapable of cure

Nothing in this section limits Company’s immediate suspension or other remedies for security abuse, redistribution, confidentiality misuse, unlawful use, or other high-risk breaches under the Agreement.

21.3 Termination For Insolvency

Either party may terminate if the other party becomes insolvent, enters bankruptcy, or ceases business, subject to mandatory law.

21.4 Effects Of Termination

Upon termination or expiry:

  1. Customer’s license ends immediately
  2. Customer must cease all use of the Services except as expressly permitted for post-termination wind-down
  3. accrued payment obligations survive
  4. each party must return or destroy the other party’s Confidential Information, subject to lawful retention and backup copies
  5. Company may disable credentials and access

22. Audit And Compliance Verification

Upon reasonable prior notice and during normal business hours, Company may request information reasonably necessary to verify Customer’s compliance with licensed scope, user counts, affiliate scope, redistribution restrictions, and other material use restrictions.

If Company reasonably suspects a material breach, Company may require additional documentary confirmation. Any audit or verification must be proportionate and subject to confidentiality protections.

23. Export, Sanctions, And Compliance

Customer represents and warrants that neither Customer nor its use of the Services will violate applicable sanctions, export controls, anti-money laundering rules, or other applicable laws.

Customer may not use the Services for prohibited jurisdictions, persons, or purposes where such use is unlawful.

24. Publicity

Neither party may use the other party’s name, trademarks, or logos in public statements, case studies, or customer lists without prior written consent, except as required by law or expressly permitted in the Order Form.

25. Governing Law And Disputes

The Agreement is governed by the laws of Switzerland, excluding conflict-of-laws rules and excluding the United Nations Convention on Contracts for the International Sale of Goods.

Disputes will be resolved by:

  • the exclusive jurisdiction of the competent courts of Locarno, Canton Ticino, Switzerland

26. Injunctive Relief

Customer acknowledges that misuse of the Services, unauthorized redistribution, breach of confidentiality, or infringement of intellectual property may cause irreparable harm for which damages alone may be inadequate.

Company may therefore seek injunctive or other equitable relief in addition to any other remedies available at law or under the Agreement.

27. Miscellaneous

27.1 Assignment

Customer may not assign or transfer the Agreement without Company’s prior written consent, except to a permitted successor in connection with a merger, acquisition, or sale of substantially all assets, provided the successor is not a competitor and agrees in writing to be bound.

Company may assign the Agreement to an Affiliate or successor in connection with a merger, acquisition, reorganization, or sale of substantially all relevant assets.

27.2 Subcontracting

Company may use subcontractors and subprocessors in performing the Services, provided it remains responsible for their performance to the extent required by the Agreement.

27.3 Force Majeure

Neither party is liable for delay or failure caused by events beyond its reasonable control, excluding payment obligations.

27.4 Severability

If any provision is held invalid or unenforceable, the remaining provisions remain in effect, and the invalid provision will be interpreted as closely as possible to its original commercial purpose to the extent lawful.

27.5 No Waiver

Failure to enforce any provision is not a waiver.

27.6 Notices

Unless the applicable Order Form expressly states otherwise:

  1. Customer must send contractual notices, legal notices, and non-renewal notices to the MATHILDE notice contact identified in the Order Form
  2. the default MATHILDE notice contact is info@wnlegal.ch
  3. notices from Company to Customer may be sent to the Customer notice contact identified in the Order Form
  4. email notice is sufficient unless mandatory law requires a stricter form for the relevant notice type

27.7 Entire Agreement

The Agreement constitutes the entire agreement between the parties regarding its subject matter and supersedes prior or contemporaneous proposals, statements, and agreements on that subject matter.

27.8 Language

The controlling contract language is:

  • English

If translations are provided, they are for convenience only unless expressly stated otherwise.

MATHILDE Acceptable Use Policy

Draft status: template for Swiss counsel review and internal completion.

This Acceptable Use Policy applies to all access to and use of the MATHILDE services, outputs, documentation, APIs, files, SDKs, and related systems provided under an order form, subscription, trial, pilot, evaluation, or other written authorization.

1. Core Rule

Customer may use MATHILDE only for the internal business purposes expressly permitted in the applicable order form and product schedule.

Any use that exceeds, circumvents, competes with, or substitutes for the licensed scope is prohibited unless Mathilde Sagl expressly permits it in writing.

2. Prohibited Conduct

Customer must not, and must not permit any affiliate, authorized user, contractor, advisor, or third party acting through Customer to:

  1. sell, resell, license, sublicense, assign, distribute, publish, transmit, display, lease, rent, timeshare, outsource, white-label, or otherwise make the services, outputs, documentation, or credentials available to any third party
  2. use the services or outputs to create, power, support, verify, improve, or commercialize any external-facing or third-party-facing:
    • data product
    • benchmark product
    • index product
    • analytics product
    • API
    • signal product
    • model service
    • decision-support product
    • application that materially incorporates, depends on, reproduces, or economically substitutes for MATHILDE
  3. expose raw outputs, bulk outputs, or substantially similar outputs in a form that allows any third party to reconstruct, replicate, or economically substitute for MATHILDE
  4. create or publish benchmark, pricing, ranking, or index products derived from MATHILDE unless expressly licensed
  5. use MATHILDE as a substitute license for any third party
  6. share accounts, credentials, API keys, tokens, certificates, or access mechanisms outside the licensed user population
  7. exceed licensed seats, user counts, entity scope, affiliate scope, endpoint scope, or usage quotas
  8. scrape, spider, crawl, or systematically extract data except through the expressly licensed interfaces and limits
  9. remove, obscure, or alter any proprietary, legal, attribution, watermark, or access-control notices
  10. reverse engineer, disassemble, decompile, or otherwise attempt to derive source code, hidden methodology, non-public schema, non-public model behavior, or private operational thresholds except to the extent such restriction is prohibited by mandatory law
  11. bypass or attempt to bypass authentication, authorization, rate limits, licensing controls, watermark gates, anti-abuse controls, or service boundaries
  12. interfere with service integrity, service security, or normal operations, including through load tests, denial-of-service behavior, or unapproved automated extraction
  13. probe, scan, or test service vulnerabilities without prior written approval
  14. use the services or outputs in violation of law, regulation, sanctions, export restrictions, or court order
  15. use the services or outputs to support unlawful market manipulation, sanctions evasion, deceptive trading conduct, or fraud

3. AI And Model Restrictions

Unless the applicable order form or product schedule expressly permits otherwise, Customer must not use the services, outputs, or documentation to:

  1. train, pre-train, fine-tune, or improve any general-purpose model, foundation model, or external-facing model
  2. benchmark or evaluate models for external commercialization
  3. build, train, or improve any agent, model, or automated system that is made available to any third party and materially incorporates or substitutes for MATHILDE

Unless expressly prohibited in the applicable order form, internal inference, research, and internal decision-support use may be permitted if it remains fully internal and does not violate the resale, redistribution, or substitution restrictions above.

For clarity, authorized internal use through Company-provided machine-readable access layers, including MCP, APIs, SDKs, and licensed files workflows, is part of permitted internal use and does not by itself constitute training, pre-training, fine-tuning, or model improvement.

4. Security And Credentials

Customer must:

  1. maintain reasonable security over all credentials and access paths
  2. promptly revoke access when a user no longer needs it
  3. notify [Security Contact Email] without undue delay of any suspected or actual credential compromise, unauthorized access, or misuse
  4. ensure that each authorized user uses only individually attributable credentials where the service supports them

5. Monitoring And Compliance

Customer acknowledges that Mathilde Sagl may monitor usage, logs, request patterns, and technical metadata to:

  • operate the service
  • enforce contractual scope
  • detect abuse
  • investigate suspected misuse
  • protect service integrity and security

6. Suspension

Mathilde Sagl may suspend or restrict access immediately, in whole or in part, if it reasonably believes that:

  1. Customer is violating this policy or the agreement
  2. Customer use presents a security, legal, operational, or abuse risk
  3. continued access may expose Mathilde Sagl, other customers, or third parties to material harm

Suspension under this policy is without prejudice to any other contractual or legal right or remedy.

Breach of this policy may also trigger the contractual penalties stated in the Master Terms of Service where the relevant conduct falls within the penalty clauses there.

7. Survival

The restrictions in this policy survive termination or expiration of the agreement for so long as Customer retains any outputs, documentation, derived data, or internal work product based on MATHILDE.

MATHILDE Privacy Notice

Draft status: template for Swiss counsel review and factual completion.

This privacy notice is a drafting baseline for the MATHILDE public and commercial service surface. It must be completed with the actual controller identity, subprocessor list, transfer information, retention periods, and live operational facts before publication.

1. Controller

The controller responsible for the processing described in this notice is:

  • Mathilde Sagl
  • Via Borgo 1, 6612 Ascona, Switzerland
  • [Registered Seat], Switzerland
  • Email: info@mathilde.dev
  • Website: https://mathilde.dev

If a Swiss representative or other statutory contact point is required for a particular processing arrangement, it must be listed here.

2. Scope Of This Notice

This notice applies to the processing of personal data relating to:

  • account holders
  • users authorized under customer accounts
  • billing and procurement contacts
  • website visitors
  • API users
  • support correspondents
  • event, partner, or business-development contacts

This notice does not change or replace any customer-specific data processing addendum where one applies.

MATHILDE is a measurement-out system: it produces market measurements from external market data and serves those measurements outward. Client requests select already-produced surfaces; they do not contribute private client data to the measurement process.

3. What Personal Data We Process

Depending on the relationship and services used, we may process:

  1. identity and contact data
    • name
    • business email
    • company name
    • title / function
    • business phone number
  2. account and entitlement data
    • account identifiers
    • user identifiers
    • roles
    • permissions
    • subscription or plan scope
  3. authentication and security data
    • login metadata
    • API key or token identifiers
    • access timestamps
    • IP addresses
    • device or client metadata
    • security events
  4. billing and commercial data
    • order details
    • invoice information
    • payment status
    • tax / VAT details
  5. support and communication data
    • correspondence
    • support requests
    • meeting notes
    • attachments voluntarily sent to us
  6. service usage and technical log data
    • endpoints called
    • request timestamps
    • response status
    • quota usage
    • file download events
    • operational telemetry reasonably required to operate and secure the service
  7. website and analytics data
    • cookies or similar identifiers [if applicable]
    • browser metadata [if applicable]
    • page and navigation events [if applicable]

As currently proved from the public intro and the authenticated product/billing surface, MATHILDE retains only the account, access-control, entitlement, API-key, usage-accounting, session, and billing metadata required to authenticate users, enforce quotas, manage subscriptions, and operate the service, together with any support or correspondence data voluntarily sent to us.

We do not treat customer private business data as part of the market-measurement input path.

4. Why We Process Personal Data

We process personal data to:

  1. provide and secure the MATHILDE service
  2. authenticate users and enforce access rights
  3. perform customer onboarding, contracting, invoicing, and collections
  4. operate, monitor, maintain, and improve the service
  5. investigate incidents, misuse, and security issues
  6. communicate with customers, prospects, and partners
  7. comply with legal, tax, accounting, sanctions, export-control, and regulatory obligations
  8. protect our contractual rights, systems, documentation, and intellectual property

5. Sources Of Personal Data

We may collect personal data:

  1. directly from the data subject
  2. from the customer or employer that created or administers the account
  3. from service use and system-generated logs
  4. from payment providers, CRM systems, support systems, and identity providers
  5. from publicly available business sources where relevant for commercial contact management

6. Recipients And Processors

We may disclose personal data to:

  1. affiliated entities within the MATHILDE group [if applicable]
  2. hosting, infrastructure, storage, monitoring, authentication, email, support, CRM, billing, and payment providers
  3. professional advisers such as lawyers, auditors, and accountants
  4. competent authorities, courts, or regulators where legally required
  5. transaction counterparties or acquirers in a corporate transaction, subject to appropriate safeguards

Where third parties act as processors for us, they may process personal data only on our instructions and subject to appropriate contractual restrictions.

Subprocessors and core service providers:

  • Supabase for authentication, session handling, and account metadata on the customer-facing frontend/auth surface
  • Stripe for subscription billing, customer portal operations, payment methods, and billing webhook processing
  • [Add any additional live providers before publication if the final service stack uses them]

7. International Transfers

Personal data may be processed in Switzerland and, depending on the service configuration, in other countries.

Where personal data is disclosed to a country that does not provide an adequate level of protection under Swiss law, we will use an appropriate transfer mechanism and appropriate contractual or organizational safeguards.

Transfer locations relevant to the live service:

  • [Insert countries]

Transfer mechanism:

  • [Adequacy decision / SCCs / other recognized mechanism]

8. Retention

We retain personal data only for as long as necessary for the purposes described in this notice, including to:

  • provide the service
  • maintain security and auditability
  • meet legal, tax, and accounting obligations
  • resolve disputes
  • enforce agreements

Indicative retention periods:

  • account and commercial records: [insert period]
  • support records: [insert period]
  • security and access logs: [insert final period; as currently proved, auth-surface usage events are retained 7 days, and auth-surface API-key rows in terminal status revoked or expired are prunable after 30 days]
  • billing and tax records: [insert period]
  • marketing/contact records: [insert period]

As currently proved from the implemented auth and frontend delete paths:

  • the auth-engine account row and linked API keys are deleted by the account-delete workflow once the account is disabled and the delete path is executed
  • where a linked Supabase user exists, the admin account-delete flow attempts to delete that Supabase user after the auth-engine delete succeeds
  • automatic deletion of Stripe-side customer or billing artifacts is not currently proved by the implemented delete flow and must not be assumed in the final published notice unless separately implemented and verified

If exact periods differ by data class, region, or environment, the final notice must state that clearly.

9. Data Security

We apply technical and organizational measures appropriate to the risk to protect personal data against unauthorized access, disclosure, loss, alteration, or destruction.

Those measures may include:

  • access controls
  • role separation
  • credential management
  • logging and monitoring
  • backup and recovery measures
  • vendor due diligence
  • incident response processes

Because no system is completely risk-free, we cannot guarantee absolute security.

10. Cookies, Analytics, And Similar Technologies

[Complete this section based on the actual website stack.]

If our website or customer portals use cookies, analytics, session identifiers, or comparable technologies, this section must describe:

  • which technologies are used
  • whether they are essential or optional
  • who provides them
  • what they do
  • how users can manage them

11. Data Subject Rights

Subject to applicable Swiss law and any applicable exceptions, data subjects may have the right to:

  • request information about their personal data
  • request correction of inaccurate data
  • request deletion where applicable
  • object to certain processing
  • request data portability where applicable
  • withdraw consent where processing is based on consent

Requests may be sent to:

  • info@mathilde.dev

We may require reasonable proof of identity before acting on a request.

12. Automated Individual Decisions

[Complete this section based on actual practice.]

If we make automated individual decisions within the meaning of applicable Swiss data protection law, the final notice must describe:

  • that such processing occurs
  • the logic at a meaningful level
  • the effects on the individual
  • available review rights

If no such processing occurs, say so clearly.

13. Data Breaches

Where required by applicable law, we will notify competent authorities and, where required, affected data subjects of data security breaches.

14. Changes To This Notice

We may update this notice from time to time. The final published notice should state:

  • the effective date
  • how material changes will be communicated

15. Language And Publication

If the relevant website or customer surface is provided in multiple languages, the final privacy notice should also be made available in those languages.

MATHILDE Data Processing Addendum

Draft status: template for Swiss counsel review and factual completion.

This Data Processing Addendum (DPA) forms part of the agreement between Mathilde Sagl and the customer identified in the applicable order form.

This DPA should be used only where the relevant service relationship actually creates a controller/processor or processor/subprocessor arrangement that merits its own annex.

1. Scope

This DPA applies only to the extent Mathilde Sagl processes personal data on behalf of Customer in connection with the services.

This DPA does not apply to processing where Mathilde Sagl acts as an independent controller for its own account-management, security, billing, compliance, product-governance, or business-operations purposes.

2. Roles

Unless the applicable order form or annex states otherwise:

  • Customer acts as controller for Customer Personal Data
  • Mathilde Sagl acts as processor for Customer Personal Data

If a particular service configuration creates a different role allocation, that allocation must be stated expressly in Annex 1.

3. Subject Matter And Duration

Subject matter:

  • [Describe the service and the relevant processing activities]

Duration:

  • from the effective date of the applicable order form until deletion or return of the relevant Customer Personal Data under this DPA

4. Nature And Purpose Of Processing

Mathilde Sagl may process Customer Personal Data only to:

  • provide the services
  • secure, support, maintain, and troubleshoot the services
  • comply with Customer’s documented lawful instructions
  • comply with applicable law

5. Categories Of Data And Data Subjects

The categories of data and data subjects are listed in Annex 1.

6. Documented Instructions

Mathilde Sagl will process Customer Personal Data only on documented instructions from Customer unless required to do otherwise by applicable law. If Mathilde Sagl is required by applicable law to process the data otherwise, it will inform Customer unless prohibited by law.

Customer’s instructions are documented in:

  • the agreement
  • the applicable order form
  • the applicable product schedule
  • this DPA
  • written support or administration requests that are consistent with the above

Customer may not issue instructions that would require unlawful processing or materially alter the nature of the services without written agreement.

7. Confidentiality

Mathilde Sagl will ensure that personnel authorized to process Customer Personal Data are bound by confidentiality obligations.

8. Security Measures

Mathilde Sagl will implement technical and organizational measures appropriate to the risk.

The baseline measures are described in Annex 2.

9. Subprocessors

Customer authorizes Mathilde Sagl to use subprocessors listed in Annex 3.

Mathilde Sagl will impose data protection obligations on subprocessors that are materially consistent with this DPA.

If Customer is granted an objection right, the final DPA must define:

  • scope of objection
  • timing
  • effect of unresolved objections

10. International Transfers

If Customer Personal Data is transferred outside Switzerland or another applicable protected jurisdiction, Mathilde Sagl will use an appropriate transfer mechanism and appropriate safeguards.

The transfer details must be listed in Annex 3 or the subprocessor list.

11. Assistance

Taking into account the nature of the processing and the information available, Mathilde Sagl will provide reasonable assistance to Customer for:

  • data subject requests
  • security incident handling
  • data protection impact assessments where applicable
  • regulatory inquiries relating to the processor role

Customer remains responsible for assessing whether any legal obligation applies to Customer.

12. Security Incidents

Mathilde Sagl will notify Customer without undue delay after becoming aware of a confirmed security incident affecting Customer Personal Data.

The final DPA should define:

  • reporting channel
  • target timing language
  • minimum incident content
  • cooperation obligations

13. Deletion Or Return

Upon termination or expiry of the relevant services, Mathilde Sagl will delete or return Customer Personal Data in accordance with the agreement, unless retention is required by applicable law or reasonably required for security, dispute, audit, or compliance purposes.

14. Information And Audit Support

Mathilde Sagl will make available information reasonably necessary to demonstrate compliance with this DPA.

If a broader audit right is offered, the final DPA must define:

  • frequency
  • notice
  • confidentiality
  • scope limits
  • cost allocation
  • substitute mechanisms such as certifications or audit reports

15. Conflict

If there is a conflict between this DPA and the master agreement regarding the processing of Customer Personal Data, this DPA controls to the extent of the conflict.

Annex 1: Processing Description

  • Subject matter: [fill]
  • Purpose: [fill]
  • Duration: [fill]
  • Data subjects: [fill]
  • Data categories: [fill]
  • Sensitive data, if any: [fill]

Annex 2: Security Measures

[Insert the actual technical and organizational measures or reference an approved security schedule.]

Annex 3: Subprocessors And Transfer Information

Current providers proved from the live frontend/auth and billing surface:

  • Supabase for authentication, session handling, and account metadata on the customer-facing frontend/auth surface
  • Stripe for subscription billing, customer portal operations, payment methods, and billing webhook processing

[Add any additional live providers, countries, and transfer safeguards before publication.]

MATHILDE Order Form Template

Draft status: template for Swiss counsel review and commercial completion.

This Order Form is entered into between:

  • Mathilde Sagl, Via Borgo 1, 6612 Ascona, Switzerland; [Registered Seat / Trade Register / VAT if applicable]
  • [Customer Legal Name], [registered details]

This Order Form incorporates the following documents by reference:

  1. MATHILDE Master Terms of Service
  2. MATHILDE Acceptable Use Policy
  3. MATHILDE Privacy Notice
  4. MATHILDE Data Processing Addendum [if applicable]
  5. the Product Schedule attached to or referenced in this Order Form

1. Commercial Summary

| Field | Value | | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | | Order Form ID | [insert] | | Effective Date | [insert] | | Initial Term | 12 months unless expressly overridden here | | Renewal | Automatic successive 12-month terms unless Customer gives written non-renewal notice at least 3 months before the end of the then-current term | | Billing Frequency | Monthly in advance by credit card through the customer account page unless expressly overridden here | | Currency | [insert] | | Fees | [insert] | | Payment Terms | Automatic recurring charge on the applicable billing date unless expressly overridden here | | Customer Notice Contact | [insert] | | MATHILDE Notice Contact | info@wnlegal.ch unless expressly overridden here |

2. Licensed Products

The licensed products and service components are:

  • [Aggregator / Primitives / Regime / Docs / Files / Other]

Applicable product schedules:

  • [insert file or annex references]

3. Permitted Scope

Unless expressly expanded below, Customer’s license is:

  • internal business use only
  • limited to Customer legal entity only unless approved affiliates are expressly listed below or in an attached annex
  • limited to [authorized users / seats / API keys / business units]
  • limited to [territory if relevant]

4. Delivery Channels

Licensed delivery channels:

  • [HTTP API]
  • [MCP]
  • [WebSocket]
  • [gRPC]
  • [Files]
  • [SDK]
  • [Other]

Any channel not expressly listed is excluded from the licensed scope.

5. Data Use And External Rights

External commercialization rights are:

  • none by default
  • [or describe explicitly if granted]

Derived-data rights are:

  • internal reporting only
  • internal inference / internal decision-support only
  • [other licensed exceptions]

AI / model training rights are:

  • prohibited by default unless expressly granted in writing
  • [or describe explicitly if granted]

Benchmark / index rights are:

  • prohibited by default unless expressly granted in writing
  • [or describe explicitly if granted]

6. Support

Support level:

  • [insert support tier]

Support hours:

  • [insert]

Response targets:

  • [insert or reference SLA]

7. Security And Compliance Contacts

Customer security contact:

  • [insert]

MATHILDE security contact:

  • [insert]

8. Special Commercial Terms

Unless expressly overridden in this Order Form:

  1. Customer may change plan or tier during the term through the customer billing interface or another Company-approved process
  2. if Customer remains on the same subscribed tier during the current annual term, Company price increases for that tier do not apply until the next renewal term
  3. if Company lowers the then-current price for the same subscribed tier during the current annual term, the lower price applies prospectively from the next billing cycle after the reduction takes effect
  4. if Customer changes tier during the term, the then-current price for the new tier applies from the effective date of the change and Stripe or another Company-approved billing system may apply proration, credit, or debit adjustments
  5. no refund is due for non-use, late non-renewal notice, or voluntary termination after the applicable renewal deadline, except where mandatory law requires otherwise or Company expressly agrees otherwise in writing
  6. if Company grants a pilot, demo, or evaluation access period and this Order Form does not state otherwise:
    • the default pilot term is 1 month
    • the pilot does not convert automatically into a paid subscription
    • Customer must manually activate a paid plan to continue after the pilot
    • total file-download volume during the pilot is capped at 50 GB

[Insert any additional negotiated exceptions, carve-outs, or expansions.]

If no additional negotiated exceptions are inserted here, the default contract position applies.

9. Contractual Penalty Overrides

Unless expressly modified below, the default contractual penalties in the Master Terms apply.

[Insert any negotiated override or write “none”.]

10. Signatures

For Mathilde Sagl

  • Name: [insert]
  • Title: [insert]
  • Signature: [insert]
  • Date: [insert]

For [Customer Legal Name]

  • Name: [insert]
  • Title: [insert]
  • Signature: [insert]
  • Date: [insert]

MATHILDE Product Schedule Template

Draft status: template for Swiss counsel review and product-owner completion.

This Product Schedule forms part of the applicable MATHILDE Order Form and Master Terms of Service.

It exists because Aggregator, Primitives, and Regime do not expose the same measured object, timeframe support, selector model, correction semantics, or delivery shape.

1. Covered Product

Product name:

  • [Aggregator / Primitives / Regime / Other]

Version or release family:

  • [insert]

2. Measured Object

The measured object covered by this schedule is:

  • [bars / outputs / document artifacts / file artifacts / other]

3. Included Interfaces

Interfaces included in the licensed scope:

  • [HTTP]
  • [MCP]
  • [WebSocket]
  • [gRPC]
  • [Files]
  • [SDK]

Excluded interfaces:

  • [insert]

4. Binding Product Semantics

The binding semantics for the covered product are:

  1. the covered product is a measurement surface, not a prediction surface
  2. row or payload existence does not necessarily imply strongest finality
  3. lawful corrections, recomputes, restatements, or withdrawals may occur in accordance with the documented product contract
  4. customer systems must be designed to tolerate such lawful corrections where the product contract permits them

5. Stable Boundary And Freshness Contract

[Insert the product-specific stable-boundary description.]

Examples:

  • for Aggregator:
    • bounded stable bars behind the relevant watermark
  • for Primitives:
    • deterministic grouped outputs over validated upstream bars behind the relevant serving watermark
  • for Regime:
    • grouped market-state outputs on the defended closed aligned 1h lane

6. Product-Specific Constraints

[Insert explicit constraints such as supported timeframes, family/group selectors, diagnostics/secondary behavior, or file period support.]

Examples:

  • supported tf values
  • diagnostics default behavior
  • secondary default behavior
  • allowed pairs universe
  • files period labels

7. Documentation Hierarchy

The following product materials are binding only to the extent expressly stated in the order form or master terms:

  • [OpenAPI / docs summary / docs system / endpoint guide / SLA / support docs]

The following materials are descriptive only and do not create independent warranties unless expressly incorporated:

  • [marketing copy / presentations / informal emails / demos]

8. Permitted Use Clarifications

Unless the order form expressly expands the scope, Customer may:

  • use the covered product internally
  • build internal analysis and internal work product
  • use outputs inside internal workflows consistent with the agreement

Customer may not, unless expressly licensed:

  • create a competing or substitutive external product
  • publish bulk outputs
  • create commercial benchmarks or indices
  • create external-facing model or agent products powered by the covered product

9. Product Changes

[Insert the notice policy for deprecations, schema changes, endpoint retirement, or methodology changes.]

The final schedule should distinguish:

  • ordinary non-breaking updates
  • breaking changes with notice period
  • emergency changes for security, legality, or integrity

10. Support And Incident Handling

[Reference or restate the support and incident terms relevant to this product.]

11. Product-Specific Exclusions

[Insert any product-specific exclusions, such as unsupported use cases, unsupported timeframes, unsupported markets, or unsupported dependency assumptions.]

12. Schedule Overrides

This Product Schedule overrides the Master Terms only to the extent expressly stated here. All other terms remain in force.

MATHILDE Aggregator Product Schedule

Draft status: concrete product schedule baseline for Swiss counsel review and commercial completion.

This Product Schedule applies to the MATHILDE Aggregator product where referenced by an Order Form.

1. Covered Product

Product:

  • Aggregator

Product role:

  • the upstream MATHILDE bar-truth layer

2. Measured Object And Product Families

The core measured object is:

  • bars

The surrounding product families also include:

  • state surfaces
  • closed-span file publication artifacts

The product is designed to turn imperfect multi-venue market streams into bounded bar truth with explicit stable boundaries, canonical minute truth, and inspectable construction lineage.

3. Available Interfaces

Subject to the Order Form, the product may be licensed through:

  • HTTP API
  • MCP
  • WebSocket
  • gRPC
  • files
  • documentation and exact-contract surfaces

Unless the Order Form states otherwise, no interface is granted merely because it exists publicly or technically.

4. Binding Product Semantics

The following semantics are part of the Aggregator product contract.

  1. Aggregator is a measurement product, not a prediction product.
  2. Aggregator forms bars on fixed UTC grids.
  3. Canonical 1m is the truth center for larger bars.
  4. Larger bars are derived from canonical 1m; they are not separate independent truth families.
  5. The live edge is governed by bounded 5s construction near the market edge.
  6. The same construction family governs both the live frontier and offline historical seed.
  7. Row existence is not the same as strongest finality.
  8. Stable read access is governed by explicit stable-boundary or watermark semantics.
  9. Historical truth may improve through repair, seed, harmonization, or recompute, and downstream consequences may require propagation into derived bars or files.

5. Stable Boundary And Time Contract

At a product-contract level:

  1. stable reads are bounded by the relevant stable watermark
  2. the product serves closed bars rather than open-edge execution signals
  3. publication artifacts follow closed-span publication rules rather than “newest available” rules
  4. recent live history may remain outside the stable boundary until the product can justify that it is safe to consume

The Order Form must not be interpreted to require open-edge execution semantics unless expressly and separately agreed in writing.

6. State Surfaces And Files

The product may include state surfaces that describe:

  • freshness
  • readiness
  • harmonization
  • coverage
  • convergence

The product may also include closed-span file publication artifacts such as day, month, or year period slices where licensed.

Those surfaces are part of the product meaning. They are not merely decoration around the bars.

7. Supported Scope And Constraints

The public measured bars surface is oriented to fixed UTC grids, including closed bars from 1m upward through larger derived horizons.

The governed pair universe is curated. Aggregator is not contractually framed as an indiscriminate “all tokens” universe.

Where the exact licensed scope matters, the Order Form should state:

  • permitted pairs or pair policy
  • permitted environments
  • permitted interfaces
  • whether files are included
  • whether state surfaces are included

8. Included Read Families

Where licensed, the product may expose read families such as:

  • latest
  • range
  • search
  • time-machine
  • stable live bars streams
  • predicate-triggered message streams

Those read families answer different questions and must not be treated as interchangeable obligations.

9. Product-Specific Exclusions

Unless expressly licensed, Aggregator does not grant:

  • execution rights
  • brokerage rights
  • venue-operation rights
  • trading-advice rights
  • permission to republish bars externally
  • permission to build a substitute bars API, benchmark, or external data service

10. Corrections, Restatements, And Rebuilds

Because Aggregator is a convergent measurement system, lawful corrections and rebuilds are part of the product contract. Customer must not treat any corrected, recomputed, or republished artifact as a breach merely because a historical row or file changed in accordance with the documented methodology.

11. Binding Documentation

The following documents may be binding if expressly incorporated in the Order Form:

  • product summary
  • system documentation
  • endpoint guide
  • exact contract / OpenAPI
  • support schedule

Informal emails, demos, presentations, and marketing copy remain descriptive only unless expressly incorporated.

MATHILDE Primitives Product Schedule

Draft status: concrete product schedule baseline for Swiss counsel review and commercial completion.

This Product Schedule applies to the MATHILDE Primitives product where referenced by an Order Form.

1. Covered Product

Product:

  • Primitives

Product role:

  • the deterministic grouped-measurement layer built on validated MATHILDE Aggregator upstream bar truth

2. Measured Object

The measured object is:

  • outputs

The product turns closed Aggregator upstream bar truth into grouped primitive market measurements under one deterministic contract.

3. Available Interfaces

Subject to the Order Form, the product may be licensed through:

  • HTTP API
  • MCP
  • WebSocket
  • gRPC
  • files
  • documentation and exact-contract surfaces

Unless the Order Form states otherwise, no interface is granted merely because it exists publicly or technically.

4. Binding Product Semantics

The following semantics are part of the Primitives product contract.

  1. Primitives is a measurement product, not a prediction product.
  2. Primitives computes deterministic grouped measurements over validated upstream bars.
  3. The grouped outputs are organized by family rather than treated as one flat field list.
  4. Diagnostics are part of the product contract where exposed.
  5. Canonical output identity is preserved by (pair, tf, e_ms).
  6. Lawful upstream-truth changes may trigger exact recompute of the affected output rows under the same canonical identity.
  7. Stable serving is bounded by the relevant serving watermark rather than by raw recency alone.

5. Measurement Scope

The product is designed to support grouped primitive measurement across families such as:

  • returns
  • range
  • drawdown
  • dependency
  • flow
  • seasonality
  • signal
  • related structural and statistical measurements

The exact currently supported public family and group space is governed by the binding taxonomy and registry surfaces where incorporated.

6. Stable Boundary And Time Contract

At a product-contract level:

  1. Primitives consumes closed upstream Aggregator bars only
  2. output serving remains subject to stable-boundary / serving-watermark rules
  3. row existence does not by itself imply strongest finality under the broader measurement chain
  4. lawful corrections, recomputes, and restatements remain part of the product contract

7. Selector And Output Semantics

Where licensed, Primitives may expose selector-driven output retrieval, including:

  • pair
  • timeframe
  • family
  • group
  • diagnostics flags

The exact supported selector contract is defined by the licensed interface and binding documentation.

8. Included Read Families

Where licensed, the product may expose read families such as:

  • latest
  • range
  • search
  • time-machine
  • stable live outputs streams
  • predicate-triggered message streams
  • closed-span file exports

Those families preserve different question meaning and are not interchangeable obligations.

9. Product-Specific Exclusions

Unless expressly licensed, Primitives does not grant:

  • permission to treat any output as investment advice or a trading instruction
  • permission to publish or commercialize a substitutive primitive-output data service
  • permission to build an external-facing benchmark, index, or model service materially based on Primitives outputs

10. Documentation And Contract Surfaces

The following documents may be binding if expressly incorporated in the Order Form:

  • summary
  • system document
  • taxonomy
  • registry
  • endpoint guide
  • exact contract / OpenAPI
  • support schedule

Counts, examples, and explanatory tables in descriptive materials remain non-binding unless expressly incorporated.

11. Corrections And Recompute

Customer acknowledges that upstream truth changes may lawfully trigger recompute of affected Primitives output rows. Such recompute does not create a second history; it preserves one canonical output history under the same identity.

MATHILDE Regime Product Schedule

Draft status: concrete product schedule baseline for Swiss counsel review and commercial completion.

This Product Schedule applies to the MATHILDE Regime product where referenced by an Order Form.

1. Covered Product

Product:

  • Regime

Product role:

  • the grouped market-state measurement layer built on closed aligned MATHILDE Aggregator upstream 1h bars

2. Measured Object

The measured object is:

  • outputs

The product preserves grouped market-state measurement under a fixed family-and- question matrix rather than collapsing market state into one coarse regime label.

3. Available Interfaces

Subject to the Order Form, the product may be licensed through:

  • HTTP API
  • MCP
  • WebSocket
  • gRPC
  • files
  • documentation and exact-contract surfaces

Unless the Order Form states otherwise, no interface is granted merely because it exists publicly or technically.

4. Binding Product Semantics

The following semantics are part of the Regime product contract.

  1. Regime is a measurement product, not a prediction product.
  2. Regime measures market state through one fixed family-and-question matrix.
  3. The public support boundary is one defended 1h lane.
  4. Canonical output identity is preserved by (pair, tf, e_ms).
  5. Stable serving is bounded by the stable 1h serving watermark.
  6. Lawful upstream-truth changes may trigger exact recompute of affected output rows under the same canonical identity.
  7. secondary=true, where supported, widens surfaced scalar context without changing row identity.

5. Public Support Constraints

The current public product contract is constrained as follows:

  1. timeframe support is 1h only
  2. secondary defaults to false unless the relevant interface expressly states otherwise
  3. diagnostics defaults to false unless the relevant interface expressly states otherwise

If a wider support boundary is ever licensed later, it must be stated expressly in a revised Product Schedule or Order Form.

6. Matrix And Family Semantics

The product is organized as a fixed market-state matrix rather than as a flat indicator list.

The current public family structure is centered on decomposed state questions such as:

  • trend
  • momentum
  • volatility
  • flow
  • risk
  • dependency
  • structure
  • inflection
  • substructure

The product contract preserves the distinction among those state questions.

7. Stable Boundary And Time Contract

At a product-contract level:

  1. Regime consumes closed aligned upstream 1h bars only
  2. output serving remains subject to stable 1h watermark rules
  3. row existence does not by itself imply strongest finality under the broader measurement chain
  4. lawful corrections, recomputes, and restatements remain part of the product contract

8. Included Read Families

Where licensed, the product may expose read families such as:

  • latest
  • range
  • search
  • time-machine
  • stable live outputs streams
  • predicate-triggered message streams
  • closed-span file exports

Those families preserve different question meaning and are not interchangeable obligations.

9. Product-Specific Exclusions

Unless expressly licensed, Regime does not grant:

  • permission to represent grouped state outputs as forecasts
  • permission to publish or commercialize a substitutive regime-output service
  • permission to build an external-facing benchmark, label, model service, or decision product materially based on Regime outputs
  • permission to infer multi-timeframe public support from the existence of one defended 1h lane

10. Documentation And Contract Surfaces

The following documents may be binding if expressly incorporated in the Order Form:

  • summary
  • system document
  • taxonomy
  • registry
  • endpoint guide
  • exact contract / OpenAPI
  • support schedule

Examples, case studies, and explanatory matrix narratives remain descriptive only unless expressly incorporated.

11. Corrections And Recompute

Customer acknowledges that upstream truth changes may lawfully trigger recompute of affected Regime output rows. Such recompute does not create a second history; it preserves one canonical output history under the same identity.