A: 1. Are you aggregating + sharing fraud typologies that are observed and confirmed with all using the platform?

Yes, Sensfrx aggregates fraud typologies observed across the platform. We analyze patterns like bot behavior, account takeover attempts, fake signups, and payment fraud. While we don’t share sensitive customer-specific data, we do maintain and share anonymized trend insights and emerging fraud patterns through:

* Our dashboard insights and reports
* Community knowledge base (in progress for future release)
* Optional alerts for newly detected fraud signatures

This allows all users to benefit from the collective intelligence of the network while maintaining privacy and compliance.

2. Do we have shadow mode to run fraud rules?

Yes, Sensfrx supports Shadow Mode (also called "monitor-only" mode). This allows you to:
* Run fraud rules without enforcing decisions
* Log, observe, and analyze what would have happened
* Tweak your policies before going live

This feature is ideal for testing rules safely in production environments without impacting user experience.

3. For the use cases, are they meant to be used only on payment mechanisms (payment gateways), or also for preventing fake lead sign-ups?

Sensfrx use cases go beyond payment fraud. Our fraud detection engine covers:
* Fake lead signups (New Account Fraud)
* Bot signups or scraping (Bot Fraud)
* Account Takeover attempts (Account Security)
* Payment fraud (Transaction Fraud)

So yes, you can use Sensfrx to prevent fake leads, spam registrations, or bot-based form abuse, not just payment-related scenarios.

4. Can the SDK be embedded in any platform based on your answer in #3?

Yes. The JavaScript SDK can be embedded on any web platform, including:
* Custom-built websites
* CMS platforms (WordPress, WHMCS, Blesta with ready plugins)
* Landing pages or funnels
* Web apps (React, Vue, etc.)

We also provide server-side SDKs (PHP, Python) and direct API integration options if you need backend-level control.