Security and data handling

For whoever approves tools: what Deptho and Deptho Pro do on your machines. Each statement below is checked against the code.

Network access

These are the only hosts the packages contact, and only at these times. Everything else (loading data, replaying orders, sweeps, reports, the license check) runs without network access.

No telemetry

No telemetry, no usage reporting, no crash reporting. The license check never contacts a server.

How the license is checked

A license key is a signed token: DEPTHO1.<payload>.<signature>. The payload holds the licensee's email address, the plan, the number of seats, the expiry date and the issue time. Deptho Pro verifies the Ed25519 signature on your machine against a public key built into the package. Keys expire at the end of the paid period plus 7 days; each renewal's key arrives by email, and on an offline machine you copy it over.

What leaves your machine

Nothing. Strategy code, signals, orders, datasets and results stay on your machines. Reports are single HTML files saved locally with everything embedded, so opening one needs no network access.

Source code

The free deptho library is open source under the Apache License 2.0, so it can be audited: github.com/jjinaustin/deptho. Deptho Pro is closed source; its package index lists a SHA-256 hash for every file, which pip checks on install.

Payments

Stripe processes payments as merchant of record. Card details go to Stripe; we never see them. From Stripe we receive your email address and plan, to issue and send your license key.