↗ Crazy Rabbit
Policy / Updated 8 October 2026

Privacy Policy

This policy covers the Crazy Rabbit website and current RABBITX Beta. It describes the current local-only product and inactive checkout.

Website visits

This version of the website adds no analytics, advertising trackers, account system, forms or application cookies. When hosted on Cloudflare Pages, the hosting provider processes connection and request information, such as IP addresses and technical logs, to deliver and protect the website. Cloudflare handles that information under its own Privacy Policy.

Local reviews and reports

RABBITX makes requests to the targets you configure. Those targets can observe your requests and network address. Saved projects and JSON/HTML reports are written locally to the paths you select. The current Beta does not include a Crazy Rabbit cloud account or a report-upload service.

Reports can contain sensitive URLs, parameters, response evidence and configuration. Choose storage, access permissions, sharing and deletion appropriate to your authorization. Delete local files when you no longer need them.

Contact and third-party links

If you contact us through GitHub, the information you submit is processed by GitHub and may be public. We use feedback to answer questions and improve the product. Do not include secrets or private target evidence. Download links and documentation open GitHub, governed by GitHub’s privacy statement.

Payments

No live payment data is collected through this website. The checkout placeholder loads no Paddle script and contains no billing form. Before live sales, this policy will be updated to explain the actual payment provider and data handling.

Questions and updates

Contact the maintainer to ask about information you have shared or request removal of information under our control. Third-party records and public copies may require a separate request to that provider. Policy updates will appear here with a revised date.

Talk to Crazy Rabbit

For product questions, beta feedback and policy questions, contact the maintainer through GitHub Issues. A GitHub account is required. Do not post credentials, payment details, private target URLs or security-sensitive evidence in a public issue.