Non-custody clarifies boundaries
Fundai does not handle withdrawals or require assets to leave the user account, so tool risk and exchange risk can be inspected separately.

Fundai Trust Protocol
Last reviewedReviewed byFundai
A financial tool earns trust by showing asset location, permission boundaries, and operating records.
Fundai safety starts with non-custody: assets stay in the user-owned Bitfinex account, API access does not require withdrawal permission, and users can revoke keys, stop strategies, and keep reports. That does not remove market or exchange risk; it makes each risk visible, recordable, and actionable.
Fundai does not handle withdrawals or require assets to leave the user account, so tool risk and exchange risk can be inspected separately.
Funding automation needs funding-offer permissions, not withdrawal creation. Users should retain the ability to revoke API keys.
Trust should come from reconcilable records: orders, interest, fees, idle capital, and abnormal states.
Stopping strategies, revoking API keys, downloading reports, and preserving cash-flow records are basic financial-tool requirements.
Checklist
Fundai Standard
Asset location can be ignored.
Automation can overshadow custody questions.
Asset location is checked first.
API details can be skipped.
Permissions become only setup steps.
No withdrawal permission is a required boundary.
Only results are visible.
Only feature status is visible.
Reports, alerts, and exit records are part of trust.
HowTo
Turn API and report review into a regular workflow.
FAQ
No. Non-custody means Fundai does not hold assets, but exchange, API, rate, and market risks still exist.
Fundai does not need withdrawal API permission, and users should not grant withdrawal access to funding tools.
Users can stop strategies, download reports, and revoke the API key in Bitfinex.