Privacy and the holdout checker
What the current static publication and client-side worksheet do, without unverified promises about host retention.
Experiment-plan inputs
The holdout checker evaluates dates and a version label in the user's browser. It contains no account connector or input-upload call; exporting downloads the entered plan and its untested classification. Use an experiment label, not a password or personal identifier.
Host and font requests
Cloudflare Pages serves this publication and receives normal web requests. This edition requests fonts from this site's own files rather than Google-hosted font endpoints. Actual host logging, analytics and retention have not been independently established. Self-hosted typography and browser-local inputs do not amount to an infrastructure no-tracking guarantee.
Other services
Source links lead to independent product or documentation destinations with their own practices. This site has no registration interface and the checker does not submit a model to a vendor. The notice describes the implementation, not a completed legal compliance review or an assurance about a linked service.
Sources
- QuantConnect optimization parameters
- ALFRED real-time and vintage data
- OpenTimestamps protocol documentation
Research guides
AI data leakage and holdout audit
Audit feature availability, outcome overlap and test exposure with a frozen experiment record and a worked calendar-boundary example.
Backtest, forward and live evidence
Reconcile simulated decisions, prospective instructions and account fills without promoting one evidence layer into another.
Algorithmic versus AI signal claims
Map fixed rules, trained predictions, AI explanations and order routing to the specific consumer evidence each needs.
Input, export and search responsibilities
The planning tools process reader entries locally in the browser and supply no account connector or remote model submission. Their downloaded files include the entered labels and notes. Do not include credentials or private account identifiers. This edition creates no browser persistence for those entries and no server-side storage service for them.
Search terms can enter the URL, browser history and host requests. The current template requests self-hosted fonts; it does not require Google font requests. Actual hosting analytics, retention and accountable legal handling remain unconfirmed. Those infrastructure questions are different from a browser-local calculation and cannot be replaced by a blanket no-tracking promise.