Security
Last updated 2026-11-18
API keys
- Keys are shown once and stored only as SHA-256 hashes.
- Each key can have a spend limit (lifetime, daily, weekly or monthly), an expiry date and an access level (full, run, view).
- Keys can be disabled, re-enabled, rotated (the old secret stops at once) or deleted.
- Key changes are recorded in the wallet's activity log; secrets never are.
Transport and web
- The service is served over HTTPS only, with HSTS.
- Keys travel in the
AuthorizationorX-API-Keyheader, never in cookies; the site sets no cookies. - Rate limits apply per key and, for public endpoints such as signup, per IP address.
Data handling
- Results are deleted automatically after the retention window (24 hours minimum, then 0, 3 or 7 days by wallet setting).
- Request inputs on usage records are removed after 90 days.
- The crawler identifies itself, follows robots.txt after the homepage, caps pages and time per audit and refuses private-network addresses.
Payments
Online payments happen on Whop's hosted checkout (Whop is the merchant of record). No card data passes through the service; we only receive the payment status, amount and ID from the Whop API, and credit a wallet only after verifying the payment there.
Accounts
There are no user accounts, passwords, 2FA or SSO: a wallet is controlled by its full-access API keys.
Certifications
None. We have no SOC 2 or ISO 27001 certification and no independent penetration test.
Reporting a vulnerability
Email justshipit00@gmail.com. Test only against your own keys and sites. There is no paid bug bounty.