Fundai Trust Center

Last reviewedReviewed byFundai

Fundai privacy and data boundaries for a non-custodial Bitfinex funding desk.

Separate API permissions, account data, reports, alerts, and deletion workflow so users can see what Fundai can and cannot do.

Fundai privacy design is tied to the product boundary. Fundai does not custody assets, does not require withdrawal API permission, and does not ask users to transfer exchange funds to Fundai. To provide Bitfinex USD funding automation, report reconciliation, and status alerts, Fundai needs to process account connection state, API status, funding orders, interest records, strategy settings, and necessary contact data. The purpose of that data should be to help users manage and inspect their own funding workflow, not to turn financial decisions into an opaque box.

01

Fundai data purpose should be explainable

Data use should connect to funding automation, report reconciliation, alerts, account state, and risk checks instead of vague collection.

02

API keys should not include withdrawal permission

Fundai non-custody is built on restricted API access; users should be able to inspect permission scope in Bitfinex and revoke the key.

03

Reports are for reconciliation, not return promises

Funding earnings, fees, funded seconds, idle capital, and early repayment records create an inspectable ledger, not a fixed-return claim.

04

Alerts and contact data should stay minimal

Status alerts, support, and billing messages need necessary contact information, but their purpose and offboarding workflow should remain visible.

Checklist

Data-boundary checks before using Fundai

  1. Confirm Fundai does not need withdrawal API permission
  2. Confirm the API key is dedicated to Fundai and revocable in Bitfinex
  3. Confirm data use maps to funding orders, reports, alerts, or support
  4. Confirm report records can be reconciled with Bitfinex source records
  5. Confirm how to remove API access when stopping use
  6. Confirm you keep necessary accounting, tax, and exit records

Fundai Standard

How to judge data boundaries

Fundai fieldAvoidUser should seeFundai standard

API scope

Unclear purpose or withdrawal access.

Key purpose and revocation path are visible.

No withdrawal permission, revocable access, and inspectable scope.

Data purpose

Generic service-improvement language only.

Clear mapping to orders, reports, alerts, and support.

Data use is tied to the funding operating workflow.

User control

No clear offboarding path.

API access can be removed and records can be kept.

API revocation, report retention, and exit checks are part of the standard.

HowTo

How to inspect Fundai data boundaries

Start with API permissions, then check reports, alerts, and the offboarding workflow.

  1. Create a dedicated Fundai API key in Bitfinex.
  2. Confirm the key has no withdrawal permission.
  3. After connecting Fundai, verify funding orders and reports can be reconciled.
  4. Confirm the purpose of alert or support contact data.
  5. When stopping use, revoke the API key and retain necessary records.

FAQ

Fundai privacy and data FAQ

01Does Fundai need withdrawal permission?

No. Fundai non-custodial design should not require withdrawal API permission. Users should create a restricted, revocable API key dedicated to Fundai.

02Does Fundai custody my assets?

No. Assets remain in the user-owned Bitfinex account and Funding Wallet. Fundai handles automation, reports, alerts, and permission state.

03Do Fundai report records imply guaranteed returns?

No. Reports reconcile historical orders, interest, fees, and idle capital. Future rates still depend on supply, demand, and risk conditions.