Terms and data policy Last updated: 2026-09-28

← Cycle time estimate

Your NC code never leaves this computer. Neither do workpiece names, nor your machine configuration file. The browser enforces this; it is not a promise from us. Section 3 is how to check.

This is a translation. Where the language versions differ, the Traditional Chinese version governs (see section 4).

1 · Disclaimer

  1. The cycle times this site produces are estimates, not guarantees. How close they are depends on where the machine parameters came from, and every report states the source level used for that run. With no machine file loaded the level is T0 — controller-family defaults, of which not one value comes from your machine.
  2. We do not claim any error percentage. Stating an error figure requires samples measured against real machines, and we do not have enough of them yet. Use your own measured data to judge whether this tool suits your purpose.
  3. The output should not be your only basis for a quote, a schedule, or acceptance. Cross-check it against your own measurements or experience.
  4. This site does not check NC programs for safety. No collision detection, no material removal simulation. We accept no liability for machining results, damage to machines or workpieces, or any consequential loss.
  5. Unsupported commands are listed explicitly in the report's diagnostics section; nothing is silently estimated. Treat any report containing diagnostics as a low-confidence result.

2 · Privacy Policy

2.1 What is never transmitted

The following never leaves your browser under any circumstances, and there is no setting that changes this:

  1. NC code, and any path geometry derived from it
  2. Workpiece, product, and operation names
  3. Your machine configuration file

This is not merely our internal discipline — the browser enforces it. The cycle time page sets its Content-Security-Policy to connect-src 'self', which makes it technically incapable of sending anything anywhere; and our origin has no endpoint that could receive data (it is a purely static deployment with no server-side code). Section 3 explains how to verify.

2.2 What is sent when you submit feedback

Only four pages transmit anything: Feedback, Contact, Account and Checkout. None of them has a file upload field (page by page in section 3). The account page sends the email address used to sign in, the computer codes you add and the names you give them, requests for an activation file, and the random identifier when you press claim. A computer code is a hash: it does not reveal the computer's original identifier. The checkout page opens Paddle's checkout: the payment details you enter there go directly to Paddle, not to us. We only pass in the email address you signed in with, so that the payment is linked to your account.

Feedback sends exactly the fields you filled in. Before sending you can expand "See exactly what will be sent" and check the complete content. In addition to those fields, we attach:

  1. The software version, and a hash of the machine configuration (one-way, used to reproduce the result)
  2. The proportions of that run's time attributed to each limit — no program geometry, no machine parameters, no cycle length
  3. The diagnostic codes and counts from that run. The codes are our own constant strings; the diagnostic messages are not included, because messages can quote literal values from the program
  4. A random identifier generated by your browser, used for de-duplication. It contains no identity information
  5. The block count of this program, and which machine parameters it depends on (parameter names and counts only, no program code)
  6. The configuration template you selected; this is empty when you load your own configuration file
  7. How many times this browser has used the tool and the date of first use (date only). This is the denominator for "what fraction of people who used it are willing to report back", and it contains nothing about any individual analysis

2.3 What is stored in your browser

This site uses no cookies and no analytics of any kind. What is kept in your browser's localStorage is listed below, and none of it is transmitted automatically:

CategoryContents
Anonymous identity and feedback cache Random identifier for de-duplicating feedback (no identity information), plus the summary and parameters of your last calculation (used to pre-fill the feedback form). No NC code and no path geometry
Interface preferences 3D view preferences, tool diameter, grid and bounding box toggles, workspace height and section collapse states. Never contains any part of an analysis
Sign-in token nccs.session, only present when signed in on the Account page; disappears when you sign out or clear site data
Account page, pending step If you press Buy, or arrive from the desktop app with a computer code, before signing in, that step is remembered (nccs.buy_intent, nccs.device_intent). Sign in within 30 minutes and it picks up where you left off; it is deleted once used

Clearing your browser data deletes all of the above. The only consequences are that we can no longer recognise your earlier feedback, the feedback form can no longer pre-fill, and the 3D preferences return to their defaults.

2.4 Retention and deletion

  1. Feedback is used only to improve the estimation model. It is not resold, not given to third parties, and not used for advertising.
  2. There is no fixed deletion period. It takes years of "estimated vs measured" on the same class of machine before an error trend is visible. You can ask us to delete yours at any time (see the next item).
  3. You can ask us to delete it at any time, no reason needed: email contact@nccyclesense.com or use Contact. If you write from the same browser we can match your earlier submission by that random identifier; if you have already cleared your browser data, describe roughly when you submitted and which machine, and we will find it by hand.
  4. The email address on your account, and the messages you sent us through Contact, can be deleted on request in the same way. When we delete an account, the feedback claimed under it goes back to being anonymous; if you want that feedback deleted too, say so in your email.
  5. If this service shuts down, the feedback data is deleted with it. It is not transferred to a third party as part of any business transfer.

3 · Auditability

You can verify the limits in section 2.1 yourself. You do not have to take our word for it.

PageOutbound connections
Cycle time estimate /index.htmlNone (enforced by CSP)
Machine file builder /machine.htmlNone (enforced by CSP)
Feedback form /feedback.htmlDatabase endpoint only
Contact /contact.htmlDatabase endpoint only
Account /account.htmlDatabase endpoint only (sign-in, activation file issuing)
Checkout /pay.htmlPaddle's checkout script and checkout window only. The only page on the site that loads third-party code; Paddle's bundled analytics are blocked by the CSP
Introduction /intro.htmlNone, and this page is not even allowed to load JavaScript
Pricing /pricing.htmlNone, and this page is not even allowed to load JavaScript
This page /legal.htmlNone, and this page is not even allowed to load JavaScript

How to check:

  1. Open your browser's developer tools, go to the Network panel, and run one estimate. Apart from the page's own assets and the WebAssembly module, no request is made.
  2. Look at the response headers of /index.html and confirm that Content-Security-Policy contains connect-src 'self'.
  3. Watch this site's traffic in your corporate proxy logs; it should match the above.

Dependencies.

  1. The calculation code (the WebAssembly module) contains no third-party code: all 17 crates are written by us, including the TOML parser and the WebAssembly interface. This is enforced by our continuous integration: adding an external dependency fails the build.
  2. The 3D path view uses Three.js 0.185.1 (MIT licence). That file is served by this site, not from a CDN, and is loaded only when you open the path view. /vendor/three/SHA256SUMS lists the official release's checksums: our three.module.min.js and three.core.min.js are byte-for-byte identical to the official release. In OrbitControls.js and TrackballControls.js only the import line points at a local path, so those two files' checksums will not match, and that is expected. This does not weaken section 2.1: connect-src 'self' is enforced by the browser and is independent of what code runs on the page.
  3. The web front end contains no analytics, no error tracking, no external font service, and uses no cookies.

4 · Terms of service

  1. The web version is free; the desktop version is paid software (prices and plans on the Pricing page). Neither carries a service level agreement; the web version may change, be suspended, or be discontinued at any time without notice.
  2. Cycle time estimation needs no account — no registration and no login. An account is optional, and only needed to claim your anonymous feedback, or to obtain an activation file once the desktop version ships. Creating one stores your email address (used to sign in); we store no other personal data. There is no password — sign-in uses a one-time link sent to that address.
  3. The 10,000 lines limit applies to the total of the files loaded at once; exceeding it is flagged as soon as you choose them and calculation is disabled. This is the free-tier boundary (see Pricing); the desktop version does not have this limit.
  4. The usage limits and feature boundaries of the free tier and other plans are governed by the specifications published on the Pricing page.
  5. Reports are yours; we place no restrictions on how you use them.
  6. Operator. This service is provided by NcCycleSense, a sole proprietor based in Taiwan, Republic of China. The governing law is that of the Republic of China. Online orders are sold and charged by Paddle.com Market Ltd acting as Merchant of Record; see section 6. Contact: contact@nccyclesense.com.
  7. Changes to these terms. When these terms are revised, the "Last updated" date at the top of this page is updated with them. Continuing to use the site after a revision means you accept the revised terms.
  8. Language versions. Traditional Chinese, English and Japanese are provided. Where the versions differ, the Traditional Chinese version governs.

5 · Scope of the software licence

This section is about the scope of use for the software itself. It does not cover the reports you produce with it — those are yours (section 4, item 5).

  1. The free tier may be used freely for commercial work. Use the web version for quoting, scheduling or process planning without paying us and without asking us first. The same goes for the nccs command line tool that ships with the desktop version when it runs without a licence (one file of up to 10,000 lines at a time). The desktop version follows the terms of the licence you bought.
  2. Intellectual property and no resale. This software is protected by copyright law. Without written permission, you may not copy, rename, resell, or bundle the software or its tools into a commercial product or service for external distribution. Internal use within your own facility or workflow is unrestricted.
  3. Security inspection and no tampering. You are welcome to inspect the runtime behavior and auditability of the software. Decompiling or reverse-engineering the software to circumvent plan boundaries is strictly outside this licence.
  4. Desktop licence. The desktop licence comes as an offline activation file and belongs to the company or person who bought it. One seat is one person at a time, on up to 2 computers; it may move between people inside your company but may not be transferred to another company. Each computer's activation file is valid for one year; before it expires, download it again for free from the account page (on any computer with internet access). The software itself never goes online. When you replace a computer, remove the old one yourself on the account page, twice a year; beyond that, email us. The licence is perpetual. Every version released during early access is a free update; when early access ends, 12 more months of version updates are included (for purchases made after early access ends, 12 months from the purchase date). Versions obtained during the update period keep working afterwards.
  5. If we shut down. If we ever stop operating, we will release a final version that does not need the activation file renewed, so that people who bought it can keep using it.

6 · Payment and Refund Policy

  1. Payment is handled by Paddle (Merchant of Record). Online orders, billing, invoicing and tax reporting for this site are handled by our authorised reseller Paddle.com Market Ltd. Your card statement will show Paddle's name.
  2. Full refund within 14 days, no questions asked. Within 14 days of purchase, email us through Contact or reply to the receipt Paddle sent you, and you get the full amount back.
  3. After a refund. No activation file is issued from the account page any more. An activation file you already downloaded is verified offline on your own computer, so we have no way to disable it early - that is the price of "never opens a connection while running" - and it stops working within a year at most. After a refund, please stop using the desktop version and delete the file.

Questions about these terms, or a request to delete your data: email contact@nccyclesense.com or use Contact.