Flip

Flip answers the question every agent in this directory eventually runs into, and it is the only one that has published an answer this specific. Some of what you ask it to do happens in a cloud browser it runs for you, and when a site on the other side asks for a login it does not ask you for a password. It texts a link that opens that site's own sign-in page on your phone, you sign in there with whatever two-factor or passkey the site uses, and the app sends only the session cookies back. Its policy states plainly that your password, passkey and one-time codes stay between you and the website, and that Flip never receives or stores them. It then keeps that session as a saved login so it does not have to ask again.

Money is where the rest of it lives. Bank access is read-only through Plaid, the policy says Flip cannot move money from a connected account that way, and separate processors are named by legal name for the parts that do move money. OpenAI and Anthropic are named for the model work, under terms the policy says forbid them training on it.

The pricing was the odd part and is not any more. It publishes eight comparison pages against Acorns, Rocket Money, Autopilot, Splitwise, Cleo, Albert, YNAB and Monarch Money, each quoting the rival's monthly fee to the dollar, and on 10 September its own column carried no figure at all. Read again on 22 September, the front page answers it in the FAQ: $119.88 a year, billed annually at what it calls $9.99 a month, or $19.99 monthly, after a four-day trial. Separately it publishes a spend-tracking shortcut as free forever, where every Apple Pay tap texts Flip and it keeps the tab.

Two things moved with the price. The front page no longer carries the $57 million in connected balances it published on 10 September, so that row is empty rather than stale. And the FAQ's sentence on credentials, that they are never stored in plaintext, is weaker than the policy's, that Flip never receives or stores your password, passkey or one-time codes; the row above follows the policy, which is the document.

The button that starts the thread was malformed when this listing was written, an ampersand where RFC 5724 puts the question mark, so the message text sat inside the recipient; read again on 22 September 2026 it is correct, and the link is recorded above. The policy names five processors by legal entity while naming nobody for the messages themselves, so the row for who carries iMessage stays empty.