Privacy
What this site is
<bØt-tri¢ks> is a free, public AI-security learning resource.
It hosts lessons, walkthroughs, and a set of hands-on practice labs
(Bot-Tricks Labs) where visitors can experiment with prompt-injection
techniques in safe, simulated environments.
What we collect
Almost nothing. There is no analytics script, no tracking pixel, no third-party advertising, no fingerprinting, and no cookies set by this site.
The only data the site stores in your browser is:
-
labsSessionId— a randomly generated localStorage value (lab-xxxxxxxxxxxxformat) used to keep your lab session alive between page loads. It is never sent anywhere off the site, and you can clear it by clearing site data for bot-tricks.com.
The web server's standard access logs record your IP address, the request path, response code, and user agent. These logs are kept briefly for operational debugging and never sold or shared.
What the labs do
The hands-on labs send user input to a Python backend on the same
server (bot-tricks.com/labs/api/). Lab inputs are processed
in-memory for the duration of the session and are not retained beyond
the session lifetime.
Third parties
- Arcanum-Sec — branding partner. The site links to arcanum-sec.com; clicking that link takes you to their site, which has its own privacy practices.
- GitHub — the GitLost lab simulates a GitHub agentic workflow. It runs locally in a simulated environment; it does not call the real GitHub API.
- LLM provider for the concierge lab — see the premium lab page for the current provider and their terms.
Cookies
This site does not set cookies. The only client-side state is the
labsSessionId localStorage value noted above.
Children's privacy
This site is intended for security researchers, students, and professionals. It is not directed at children under 13, and we do not knowingly collect information from children.
Changes to this policy
We may update this page as the site evolves. The "Last updated" date at the top reflects the most recent revision. Material changes will be noted in the internal change log.
Contact
Questions or concerns: reach D4NGLZ on Telegram (@D4NGLZ).