Security
Built like the moneydepends on it.
Feedshop carries creators' earnings and merchants' order data, so security isn't a checklist for us — it's load-bearing. Here's how the platform is protected, and how to tell us if you find a hole in it.
How we protect the platform
Security by architecture.
Role-separated APIs
The platform is split into separate services per audience — public read-only, creator, partner, admin — so a public surface simply has no path to private data or writes.
Session-based authentication
All sign-in flows go through one identity service; sessions are strictly necessary cookies scoped to our domains, and every authenticated API verifies them independently, with role checks on every request.
Salted IP hashing
Click tracking never stores a raw IP address — only a salted one-way hash, kept for fraud detection. What we don't store can't leak.
Signed merchant postbacks
Merchant-reported conversions are authenticated with per-merchant HMAC signatures, so order data can't be spoofed or replayed by anyone who doesn't hold the secret.
Least-privilege administration
The admin surface is a separate application behind role-locked accounts — no shared tokens, no master keys, destructive actions behind explicit confirmation.
EU hosting
The platform and its data run on infrastructure in the European Union, under European law, with encrypted transport everywhere.
Responsible disclosure
Found a vulnerability?
We want to hear about it — directly, before anyone else. Email a description and reproduction steps to security@feedshop.app and we'll take it from there.
- We acknowledge every report within 72 hours.
- We won't take legal action against good-faith security research.
- Please don't access other people's data, degrade the service, or publish the issue before we've had a reasonable chance to fix it.
- Machine-readable details live at /.well-known/security.txt.