Screening governance
Methodology, version, evidence, authority, and history remain visible.
Trust & Safety
Trust is a product system, not a badge.
Security, privacy, Sharia governance, market-data integrity, explainable alerts, and operational reliability must work together.
Trust framework
Six areas protect the user experience.
Evidence integrity
Alert proof and historical status preserve the context at event time.
Market-data integrity
Provider, timestamp, freshness, and unavailable states are explicit.
Operational transparency
Monitor health, provider issues, and delivery failures must not stay silent.
Privacy choices
Optional analytics remains denied until consent and excludes private product data.
User control
Only the user can approve versions and activate or change monitoring.
Privacy by design
Private strategy text does not belong in public analytics.
Passwords, credentials, raw prompts, detailed Watchlist logic, reviewer notes, support attachments, direct identifiers, and asset holdings must not be sent to GA4 or GTM.
Optional analytics boundary
Consent defaults execute before optional tags
Only configured tags can load after consent
First-party product records remain authoritative
Security reporting
Use a verified protected route.
A dedicated public security-reporting address is not configured yet. Use general support without sending sensitive exploit details or credentials.
Contact support safelyNever send through public forms
Passwords or authentication tokens
Wallet seed phrases or private keys
Production secrets or database exports