Configurator Terms

1.What the service is

An embeddable cut-to-size configurator: the shopper enters parts, sees a cutting plan and a price computed from the Merchant's own published rules. CutOptim delivers the resulting order to the Merchant (signed webhook and/or e-mail) and keeps saved projects, quotes and order records on the Merchant's behalf.

2.What CutOptim does not do

CutOptim does not collect or process payments. It does not host a shop, cart or checkout (these stay in the Merchant's shop, for example WooCommerce). It is not the seller and does not fulfil, ship or manufacture. It gives no tax or legal advice. The Merchant is solely responsible for its prices, taxes, terms of sale, consumer-law information and its communication with shoppers.

3.Pricing and the customer relationship belong to the Merchant

The Merchant owns its price lists, rules and customer relationship. A quoted price is the output of the Merchant's own configuration, and the Merchant checks it before publishing. A signed quote token binds a price for the limited time configured.

4.Early access

The service is in early access: features may change, be withdrawn or break, and access may be by invitation. During early access the service is provided as is, without a warranty of uninterrupted or error-free operation, to the extent mandatory law allows.

Sandbox tenants are for testing only: test orders are not real orders, and shoppers are never mailed from a sandbox.

5.Roles and data

The Merchant is the controller of shopper data and CutOptim is the processor, under the Data Processing Agreement. The Merchant provides the privacy notice for its shop. The embedded configurator also links CutOptim's short shopper privacy notice.

6.Acceptable use

No illegal goods or content; no probing of other tenants; no circumvention of rate limits or keys. Keys and secrets are the Merchant's to protect.

7.Orders are records

Order records cannot be deleted by the Merchant through the console, and closing the account does not erase them. Order records are kept as the law requires.

8.Delivery of orders

Delivery to the Merchant's server is at-least-once with retries; the Merchant de-duplicates by event id. E-mail delivery depends on a third-party provider; inbox placement is not guaranteed.

9.Fees

No price is stated in these terms. The fees that apply to a Merchant are those shown to it when it subscribes. Usage is metered per quote, final plan and order.

10.Availability and liability

Availability: see the service level statement below. Liability: the Limitation of liability section of the CutOptim Terms of Service applies to the Configurator as well.

11.Changes to these terms

Changes follow the Modifications section of the Terms of Service: registered users are notified of significant changes by e-mail at least 30 days before they take effect. The version of this text is shown at the top of this page.

How the service runs today

• One server (Hetzner, Nuremberg, Germany) with one Configurator service container behind a reverse proxy. There is no high availability or failover. Maintenance reboots happen.
• Releases are deployed automatically after a test gate, typically within a few minutes of a change. A deployment may briefly interrupt the service; zero-downtime deployments are not promised.
• Orders: webhooks and e-mails are queued in the database and retried by a worker (at-least-once; an in-flight item is reclaimed after 15 minutes). The order is written before delivery, so a delivery outage does not lose an order. If the e-mail provider is unavailable, e-mails wait in the queue and nothing is dropped.
• Backups: a daily encrypted database dump kept 14 days and a weekly dump kept 90 days, stored off the server. The practical data-loss window after a restore is therefore up to about 24 hours. This describes how backups work; it is not a recovery-time or recovery-point commitment.
• Rate limits protect the service per tenant and per IP; sandbox tenants have daily caps.

What is not offered at this time