Terms of use
Access is for authorised research use.
By using the Rizqon website or terminal, users agree to use the service lawfully and only for their own authorised research, portfolio review, and account workflow.
- Keep account details accurate and protect login credentials.
- Do not share accounts, scrape the service, bulk export data, bypass security, reverse engineer the platform, or redistribute provider data.
- Do not use displayed data for unauthorised commercial, automated, non-display, or data-resale purposes.
- Rizqon may change, restrict, suspend, or terminate access where needed for security, misuse, provider licensing, commercial, or legal reasons.
No financial advice
Rizqon does not recommend investments.
Rizqon is not a broker, exchange, investment adviser, financial planner, tax adviser, legal adviser, or personal religious adviser. Charts, scanners, watchlists, ratings, ratios, analyst data, news, alerts, and research tools are provided for information and education only.
- Nothing on Rizqon is a recommendation to buy, sell, hold, avoid, or size any investment.
- Users remain responsible for independent research and personal suitability decisions.
- Markets involve risk. Prices can move quickly, past performance does not guarantee future results, and capital can be lost.
- Users should seek qualified financial, tax, legal, and professional advice before acting.
Market and third-party data
Data is useful, but never guaranteed.
Rizqon may display prices, chart bars, fundamentals, financial statements, analyst estimates, news, FX/rates, company metadata, and Shariah compliance information sourced from third-party providers and cached backend systems.
- Data may be live, delayed, cached, stale, incomplete, unavailable, inaccurate, interrupted, or corrected later.
- Provider licensing can limit redistribution, automated access, commercial use, and non-display use.
- Users should verify important values against exchange filings, provider pages, company reports, or other primary sources before acting.
- Rizqon should not be treated as the sole source of truth for pricing, compliance, portfolio valuation, tax, or Zakat decisions.
Shariah compliance
Compliance results are method-based signals, not a fatwa.
Rizqon includes Shariah screening to help Muslim investors research securities, but a compliance label is an informational result based on available provider data and screening methodology.
- Different standards, including AAOIFI, FTSE, MSCI, S&P, and Dow Jones-style methodologies, can produce different outcomes.
- Compliance status can change as company filings, business activities, accounting values, market capitalisation, or provider interpretation changes.
- Zakat and purification outputs are estimates and should not be treated as final religious rulings.
- Users should consult a qualified Islamic finance scholar for personal religious guidance.
Data sources and methodology
Rizqon uses provider-backed and cache-first workflows.
The current nonprod system uses Twelve Data for market-data workflows, Muslim Xchange for Shariah compliance workflows, and Supabase for authentication/profile workflows. Public references to providers should be rechecked before production release.
- Quotes, bars, fundamentals, financials, rates, news, and compliance results may load from live provider calls, shared backend caches, page snapshots, or stale-first cached data.
- Refresh timing can depend on market hours, holidays, provider limits, rate-limit protection, cache age, and scanner/background job progress.
- Where data is cache-backed, users should expect differences between visible values and provider or exchange pages until refresh completes.
- Provider names, feature coverage, and update windows should be reviewed against live code and commercial agreements before prod.
Privacy summary
Rizqon collects account and usage data needed to run the service.
Rizqon may collect account identifiers, email or username details, authentication/session data, subscription state, support messages, security logs, usage diagnostics, preferences, watchlists, portfolio entries, and saved terminal settings.
- Data is used to authenticate users, operate the terminal, manage access, secure the platform, respond to support requests, improve reliability, and meet legal obligations.
- Service providers may include authentication/database, hosting, payment, security, analytics, and support tooling where enabled.
- Users should be able to request access, correction, deletion, or privacy support through the contact route once the production policy is finalised.
- Rizqon should use reasonable safeguards, but no internet service can guarantee perfect security.
Cookies and local storage
Essential storage supports login, security, and preferences.
Rizqon may use cookies, local storage, and browser storage for authentication, launch handoff, theme selection, session continuity, security, and user preferences.
- Essential storage is needed for login and terminal access.
- Functional storage may remember theme, navigation, and interface preferences.
- Analytics or marketing cookies should only be described as active if they are actually enabled in production.
- Users can control cookies through browser settings, although blocking essential storage may break login or terminal functionality.
Subscription and billing
Billing terms must match the final payment setup.
Rizqon plan pricing is currently presented in AUD and the public web UI references Stripe-based checkout logic that is not yet fully configured in nonprod.
- Plan inclusions, trial wording, renewal cadence, cancellation rules, and refund handling must match the live payment implementation before prod.
- Where paid access is enabled, cancellation should explain whether access continues until the end of the paid period.
- Taxes, exchange fees, provider data limits, and plan-feature restrictions should be shown clearly where applicable.
- Subscription and billing wording must be approved before production release.
