Skip to content

Proof before scale

One page for the controls behind HalalCrypto.

The AI growth roadmap identified trust architecture as the bottleneck. This proof center makes the current evidence layer visible: what is live, what is still manual, and what must stay gated before broader scale.

Launch-stage boundary

HalalCrypto should win trust with visible controls, not aggressive promises. This page does not replace the terms, privacy policy, or qualified legal and Shariah review.

Halal screening

Live

Published methodology and guideline basis

The screening framework, review cadence, source references, and challenge process are public. HalalCrypto follows a published Shariah-screening method informed by AAOIFI standards and Islamic-finance guidance.

Open governance

Operator map

Live

Domain roles and launch-stage operator disclosure

The canonical public domain, operational email domain, support channels, and launch-stage operating status are documented in one place.

Open operator page

Service health

Live

Public status and probe history

The status page reports monitored customer-facing services and explains the probe cadence used for public uptime visibility.

Open status

Security

Live

Responsible disclosure and scoped controls

Security contact, disclosure rules, in-scope systems, launch-stage bounty posture, and credential-handling boundaries are published.

Open security

Performance proof

Launch-stage

Backtest-first until live customer samples exist

The leaderboard must remain framed as backtest-based until enough verified live-customer trading history exists.

Open leaderboard

Credential controls

Manual launch

No self-serve API-key entry until validation is live

Online key submission remains disabled until the encrypted vault and permission validator are active. Support-led provisioning stays the launch default.

Open bot explainer

Guidelines and operating boundaries

  • HalalCrypto follows a published Shariah-screening method informed by AAOIFI standards, OIC Fiqh Academy principles, and Islamic-finance source material.
  • HalalCrypto is not an exchange, broker, custodian, investment adviser, bank, or personal fatwa service.
  • The service is designed around spot-only workflows and rejects leverage, margin, futures, perpetuals, options, lending, and yield wrappers.
  • Customer funds stay on the customer's own supported exchange account. HalalCrypto must not request withdrawal-enabled API permissions.
  • Country expansion and paid promotion in sensitive jurisdictions require owner-approved legal review before scale.
  • AI can summarize, route, draft, and explain, but risk limits, permissions, sanctions, and jurisdiction gates must remain deterministic.

Roadmap gates from the PDF

Trust reset

In progress

Proof center, governance page, explicit product boundaries, and operator map are public.

If not reached: Keep growth content-led and avoid paid acquisition scale.

Data spine

In progress

Funnel, retention, content, checkout, support, country-gate, and permission events are measurable end to end.

If not reached: Freeze new AI automations until telemetry exists.

Onboarding automation

pending

Country gating, KYC routing, checkout recovery, support triage, and permission validation are stable.

If not reached: Keep support-led onboarding as the default.

Premium retention

pending

Paid-user churn, support load, and alert usefulness are improving with enough live customer samples.

If not reached: Delay B2B/API expansion.

Geography expansion

Owner/legal gate

Owner-approved legal readout supports each new market and promotion regime.

If not reached: Keep geo-sensitive growth content-led and gated.

Applied roadmap

The growth plan turned into operating phases.

1
Applied now

Trust and proof center

This page ties together governance, operator, security, status, performance evidence, and credential-control boundaries.

Open phase
2
Applied now

Account intelligence layer

Portfolio scanner, coin screener, risk quiz, account intelligence hub, and exchange-permission validator are live. Country eligibility checks remain owner/legal-gated.

Open phase
3
Public spec live

AI research assistant

Future AI answers must be source-grounded explainers. They must not present personal fatwa, legal advice, or personalized investment advice.

Open phase
4
Public spec live

Support and onboarding copilot

Support triage, onboarding reminders, and recovery nudges can be automated after event tracking and human-review gates are stable.

Open phase
5
Public spec live

Premium research and B2B

Premium research, watchlists, widgets, and B2B APIs should wait until trust, telemetry, and retention proof are stronger.

Open phase

Data spine

Trust and activation events to measure before scaling.

The roadmap says growth automation should wait for telemetry. The event taxonomy now defines the first trust, activation, and compliance events without collecting raw holdings, API keys, API secrets, or full IP addresses.

EventStageOwnerRequired properties
proof_center_viewtrustgrowthpath, source_path
methodology_viewtrustgrowthpath, source_path
governance_viewtrustcompliancepath, source_path
security_viewtrustproductpath, source_path
risk_quiz_completedactivationproductsuggested_track, risk_band
email_capture_submittedactivationgrowthsurface, consent_version
signup_startedactivationproducttrack, source_path
checkout_startedactivationproducttrack, price_usd, source_path
terms_acceptedactivationproductterms_version, privacy_version, refund_version

Next useful step

Review the method before reviewing the price.

The strongest conversion path for this category is education to proof to risk fit. If the methodology and proof center do not make sense, checkout should wait.