Terms and data policy
Last updated: 2026-08-30
← Cycle time estimate ·
1 Disclaimer ·
2 Data policy ·
3 Auditability ·
4 Terms of service
Every technical statement on this page is something you can verify yourself.
Data flows, the content security policy, the fields actually stored — see section 3
for how.
This is a translation. Where the language versions differ, the Traditional Chinese
version governs — see section 4, item 6.
1 · Disclaimer
- 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.
- 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. Until we do, any percentage would be a claim rather
than a measurement — so we publish none. Use your own measured data to judge
whether this tool suits your purpose.
- The output should not be your only basis for a quote, a schedule, or
acceptance. Cross-check it against your own measurements or experience.
- 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.
- 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 · Data policy
2.1 What is never transmitted
The following never leaves your browser under any circumstances, and
there is no setting that changes this:
- NC code, and any path geometry derived from it
- Workpiece, product, and operation names
- 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 the feedback form and
Contact transmit anything, and neither page has a file
upload field. Feedback sends exactly the fields you filled in — you can expand
"See exactly what will be sent" and check the complete content before sending.
In addition to those fields, we attach:
- The engine version, and a hash of the machine configuration (one-way, used to
reproduce the result)
- The proportions of that run's time attributed to each limit —
no program geometry, no machine parameters, no cycle length
- 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
- A random identifier generated by your browser, used for de-duplication. This site
has no accounts and the identifier contains no identity information
- 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:
| Key | Contents |
|---|
nccs.anon_token |
Random identifier for de-duplicating feedback. No identity information |
nccs.last_run |
The limit attribution proportions, engine version and diagnostic codes from
your last run, plus the machine configuration file you loaded, if any.
Used to pre-fill the feedback form.
No NC code and no path geometry |
nccs.usage |
A count and a first-use date. Nothing about any individual analysis |
nccs.view3d_color, nccs.view3d_tool, nccs.workspace_layout |
Your 3D colouring preference and tool diameter, and the workspace height and column widths you dragged to |
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
- Feedback is used only to improve the estimation model. It is not
resold, not given to third parties, and not used for advertising.
- There is no fixed deletion period. The value of feedback is
precisely the long-term error trend — only years of "estimated vs measured" on the
same class of machine show whether the model is actually getting better.
- 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.
- 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.
| Page | Outbound connections |
|---|
Cycle time estimate /index.html | None (enforced by CSP) |
Machine file builder /machine.html | None (enforced by CSP) |
Feedback form /feedback.html | Database endpoint only |
Contact /contact.html | Database endpoint only |
This page /legal.html | None — and this page is not even allowed to load JavaScript |
How to check:
- 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.
- Look at the response headers of
/index.html and confirm that
Content-Security-Policy contains connect-src 'self'.
- Watch this site's traffic in your corporate proxy logs; it should match the above.
Dependencies.
- The calculation engine (the WebAssembly module) contains no third-party
code — 15 crates, all 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.
- The 3D path view uses Three.js (MIT licence). That file is
served by this site, not from a CDN, and is loaded only when you
open the path view. The version and SHA-256 checksum are published at
/vendor/three/SHA256SUMS so you can compare it byte for byte against
the official release.
- The web front end contains no analytics, no error tracking, no external font
service, and uses no cookies.
Item 2 does not weaken section 2.1: connect-src 'self' is enforced by the
browser and is independent of what code runs on the page. No code can
send data out under that policy.
4 · Terms of service
- This service is currently free and carries no service level agreement.
It may change, be suspended, or be discontinued at any time without notice.
- There are no accounts, no registration, and no login.
- The file size limit is 100 MB; exceeding it is flagged as soon as you choose the
file and calculation is disabled. The cause is the memory budget of a browser tab
and interaction latency — it is not a feature tier.
Gigabyte-scale programs additionally hit the 4 GB address space of 32-bit
WebAssembly, which is structural.
- Reports carry a watermark and may be used freely for your own internal evaluation.
- Operator. This service is currently operated by an individual
(a natural person) in Taiwan, Republic of China; no legal entity has been
established. The governing law is that of the Republic of China.
The operator's name and legal entity will be announced before this service
begins charging, at which point these terms will be revised.
Contact: contact@nccyclesense.com.
- Language versions. Traditional Chinese, English and Japanese are
provided. Where the versions differ,
the Traditional Chinese version governs.