Beta — the platform and this API are in beta. The rules on this page are binding; we may add features and tighten validation without notice.

Reporting a security vulnerability

If you believe you have found a security vulnerability in a Creator Guard website, the platform or the partner API, please tell us. We read every report.

How to report

Email info@creator-guard.com with the subject "Security". Please include:

  • what you found and where (the URL or the API endpoint),
  • the steps to reproduce it,
  • what an attacker could do with it,
  • how we can reach you with questions.

Do not put personal data of creators, agencies or partners into your report. If you came across such data, say so, but do not copy it.

Please write in English.

Scope

  • creator-guard.com — the website in every language
  • app.creator-guard.com — the portals and the admin
  • api.creator-guard.com — the partner API (/v1) and the webhooks we send
  • docs.creator-guard.com — this documentation

Out of scope

  • Denial-of-service and load tests, and automated scans that send large amounts of traffic.
  • Social engineering of our team, partners, agencies or creators, and physical attacks.
  • Services of third parties we use (for example our database or email provider): report those to the provider.
  • Findings without a demonstrated security impact: missing headers on static pages, clickjacking on pages without actions, version banners, self-XSS, rate limits on requests that change nothing.
  • An API key you found in public: it is revoked as soon as it is reported to us (see Authentication). Tell us where you found it.

While you test

  • Use only your own account and your own test data. Never read, change or delete data that is not yours; if you see someone else's data, stop and report.
  • Use test-mode keys (cg_test_) whenever you can.
  • Do not contact creators, agencies or partners.
  • Do not make the issue public before we have fixed it. We will tell you when the fix is live.

What happens next

We confirm your report within 3 business days and keep you updated until the issue is fixed.

If you act in good faith and follow this policy, we will not take legal action against you or ask anyone else to, and we consider your research authorised.

We do not run a paid bug bounty programme. With your permission we thank you by name in our changelog.