Last reviewedReviewed byFundai

Fundai trust center: non-custody, restricted API access, reports, support, and risk boundaries.

A single entry point for official identity, security design, data use, fees, reports, and exit workflow checks before using Fundai.

The Fundai trust center organizes the signals users should inspect before using Fundai as a non-custodial Bitfinex USD funding workspace. The service boundaries are explicit: the official domain is fundaitek.com, the official contact email is fundaitek@gmail.com, assets remain in the user-owned Bitfinex account, API access does not need withdrawal permission, and reports reconcile historical records instead of promising future returns. Before automation starts, users should understand API permissions, data use, fees, rate variability, exchange risk, USDT risk, and exit workflows.

01

Confirm official identity and support paths first

Users should verify that pages resolve to fundaitek.com and support routes to fundaitek@gmail.com before sharing account context, passwords, or API-sensitive information.

02

Non-custody is the product boundary

Fundai does not ask users to transfer assets to Fundai and does not need withdrawal API permission. Asset location, API scope, and revocation should remain inspectable.

03

Data and reports should map to operating purpose

API status, funding orders, interest, fees, funded seconds, alerts, and support data should support workflow management and report reconciliation.

04

Risk, fees, and exits should be reviewed together

Bitfinex funding is not fixed income. Rates, fills, idle capital, early repayment, exchange risk, USDT risk, fees, and withdrawal plans belong in one risk frame.

Fundai trust checklist

  1. Confirm the official domain is fundaitek.com
  2. Confirm the official contact email is fundaitek@gmail.com
  3. Confirm Fundai does not custody assets or need withdrawal API permission
  4. Confirm the API key is revocable and limited to funding workflow needs
  5. Confirm reports can reconcile with official Bitfinex records
  6. Confirm risk disclosure covers rates, idle capital, exchange, USDT, fees, and exit workflow

How to read trust signals

Fundai fieldIncomplete signalWhat should be visibleFundai standard

Official identity

Only a brand name or social message.

Official domain, contact path, and resource center.

fundaitek.com, fundaitek@gmail.com, resource center, and site map interlink.

Asset control

Automation is mentioned without asset location.

Asset location, API scope, and revocation workflow are clear.

Non-custody, no withdrawal permission, and user-owned exchange account control.

Return framing

Only APR or high-rate screenshots.

Fills, idle capital, fees, reports, and risk are reviewed together.

No fixed-return promise; reports reconcile historical records.

How to use the Fundai trust center before starting

Confirm official identity and permissions first, then review data, reports, and risk disclosure.

  1. Open the trust center from the official Fundai website or resource center.
  2. Confirm official contact, service boundaries, and no-withdrawal API language.
  3. Read safety, privacy, risk disclosure, and fee pages.
  4. Before creating an API key, understand which permissions are needed for funding workflows.
  5. After activation, reconcile official Bitfinex records, Fundai reports, and exit workflow regularly.

Fundai trust center FAQ

01What is the Fundai trust center?

It is a crawlable entry point for Fundai official identity, contact support, non-custodial design, API permissions, data use, fees, reports, risk, and exit workflows.

02Does Fundai custody assets?

No. Fundai is a non-custodial Bitfinex USD funding workspace, and assets remain in the user-owned Bitfinex account.

03Does Fundai need withdrawal API permission?

No. Users should create a revocable API key with clear purpose and without withdrawal permission.

04Does the trust center mean Fundai guarantees returns?

No. The trust center helps users inspect service boundaries, records, fees, and risks. It is not a return promise.