Hunterlian is a book about security, so it would be strange if the site itself wasn't built carefully. Here's what we actually do.
Server-side identity checks
Every authenticated request carries an ID token that's verified on the backend — never trusted from the browser alone.
Immediate session revocation
Signing out revokes your tokens on the server, not just in your browser. A captured token stops working the moment you sign out.
Server-authoritative prices
Payments are calculated on the server from our Firestore configuration. The browser can never send a lower amount.
Payment webhook verification
Paystack webhooks are verified with an HMAC-SHA512 signature before any order is created or entitlement granted.
Rate limiting
Auth, payment, and reader endpoints are rate-limited per IP and per account to keep abuse and enumeration attempts out.
Ownership checks everywhere
Every user-scoped resource — orders, entitlements, bookmarks, reading progress — is checked against the caller's UID.
No user enumeration
Password reset responses are identical whether or not the email exists, so attackers can't build a list of registered accounts.
No password storage
We never see or store passwords. Authentication is handled end-to-end.
Disclosure policy
Found a vulnerability? We want to know — and we'll treat it seriously.
Report it to hunterlian01@gmail.com. Please include a clear description, reproduction steps, and the potential impact. We acknowledge every report within 72 hours and give credit publicly if you'd like.
See the full report page for the exact rules of engagement and what to include.
What we ask of researchers
- Test only your own accounts. Do not attempt to access, modify, or delete data belonging to other users.
- Do not run denial-of-service tests or stress tests against production.
- Do not use social engineering against Hunterlian staff or users.
- Give us reasonable time to fix the issue before disclosing publicly.