Only the Anafi engine, and only within the rule you signed. The engine's key lives inside an attested TEE; no one on the Anafi team can use it or move funds outside the flow you authorized.

A policy can send a set amount to destinations you listed — on-chain, off-chain or via off-ramp — when its conditions are met: a schedule, an incoming deposit, a price move, or a pull request from a third party you authorized.
A policy can't send to unlisted destinations, exceed your caps or frequency, or change after you sign it.

The attested engine interprets the rules you commit. It runs in an Intel TDX Trusted Execution Environment, so its code is verifiable and its memory is sealed off from us. It sees your wallet address, destinations, rules and triggers. It does not see or store personal data.

If Anafi goes offline, execution pauses. Your funds stay in your wallet and you don't need to do anything; missed payments execute once when the engine is back. If Anafi's internal systems are compromised, an attacker still can't reach your funds: the engine key sits in the TEE, and every transfer is bounded on-chain by the rules you signed.

We can only hand over what we hold: wallet addresses and execution logs. Your rules are encrypted, and we hold no KYC or banking data — that stays with licensed partners under their own obligations.

Whatever its KYC requires — typically full name, date of birth, ID document and proof of address — plus the bank details you provide for payouts. The provider's privacy policy governs this data, not Anafi's.

In the dApp at app.ana.fi: one transaction from your wallet, effective as soon as it's confirmed.

Hexens (full-scope audit, August–October 2026) and Hakira (penetration test). Scope: the engine, backend, compiler, dApp and smart contracts (Solidity and Rust).