No. Reamer Research and Reamer Server run entirely on your own machine, and neither sends strategy code, data, results or orders to Reamer Labs. Their only contact with Reamer Labs is activating or deactivating a licence, and for Reamer Research, re-signing it near each monthly renewal; each sends only the licence key, a one-way hash of the machine's identity and, on renewal, the seat id. There is no telemetry, no usage analytics and no crash reporting.
What is sent, and when
- On activation: the licence key and a machine fingerprint, which is a SHA-256 hash of the machine's hostname and network hardware address. The licence server checks the key, binds it to that machine, and returns a signed licence.
- On deactivation: the same, to release the seat so you can move it to another machine.
- Near a Reamer Research renewal: within two days of the subscription's end date, a run asks the licence server to re-sign the licence with the new end date. It sends the same key, fingerprint and seat id, and nothing else.
REAMER_LICENSE_NO_REFRESH=1turns it off. - At any other time: nothing. Each start checks the signed licence on your machine, and a running process does not check in. Reamer Server makes no call after activation.
What is never sent
- Strategy code, parameters or configuration
- Market data or any other input data
- Backtest results, orders, fills or positions
- Usage statistics, feature analytics or crash reports
Reamer Server's orders go to your broker through your own connector, not through Reamer Labs.
Checking it yourself
After activation, both products run with no internet access, so you can block outbound traffic and confirm they work. A blocked Reamer Research refresh costs at most five seconds and leaves the signed licence as it was. The Reamer Server deployment guide says that any traffic from a running process to the licence server is unexpected and should be reported. The kit also includes a vendor questionnaire pack with a data-handling statement for your firm's review.
What Reamer Labs does hold
Your email address, the licence key, the machine fingerprint and activation times, plus the name of each licensee on an order paid by invoice. Payment details stay with Paddle, which handles checkout. See the privacy policy.
See also Is there a backtesting engine I can call from Python that runs locally and never uploads my code?