The measurement is a local process at your desk, reading your two CSV files. It loads the reviews your analysts already closed and your customer attributes into memory and writes its outputs next to your files and nowhere else. They are counts, rates, confidence intervals (the range the true rate is likely to sit in) and one answer per review, keyed by review id. Your customer ids, countries and amounts do not leave the machine. Your review ids survive as those keys, so choose opaque ids.
Apart from those outputs, the tool keeps one local marker, the date of its first use, in ~/.crusetra/premiere-utilisation-scoring.json (an earlier date under the former ~/.cascade still counts): one labeled date, which the thirty-day evaluation clause of the license reads and which is never transmitted.
The tool has no callback and no telemetry, so it opens no connection to us and sends no usage data. There is no account to create.
Check the test set offlineCut the network, run everything, then recompute the content hash (the fingerprint of its bytes) of our public test set.
run it yourself
CRUSETRA_OFFLINE=1 npm testthe whole suite with the network cutnpm run sceller -- releve-public.json --checkprints "already sealed, and the seal matches" and the content hash
Where it livessrc/sceller.ts:60 · src/dossier.ts:11