Why Cardier Doesn’t Ask For Your Bank Login

Most financial apps ask for your bank login on first launch. Cardier does not. The reason is narrow and practical: tracking which benefits are on which credit card does not require access to your transaction history. The information needed to do the job is the card itself — issuer, product, renewal date — not what you spent yesterday at the grocery store. We built the app around what the work actually needs.

What the app actually needs to know

Cardier’s core job is to tell you which credits and benefits exist on each card in your wallet, and when each one resets. To do that, it needs:

• Which cards you hold.Issuer + product (e.g., “Amex Platinum,” “Chase Sapphire Reserve”). You enter this on setup.
• Each card’s anniversary or open date (for cardmember-year credits and free-night awards).
• Which monthly credits you actively use— so the app can mark those captured and surface the ones you don’t.

That is it. There is no version of this list that requires the app to read your checking account, your salary, or where you ate dinner. The benefit catalog for each card is public information that we maintain; matching it to your wallet only needs you to tell us which cards you have.

The honest tradeoff

Manual entry has a cost: you have to add each card yourself and tap “used” when you redeem a credit you want recorded. That is a small recurring action. The benefit is that nothing leaves your device without you knowing. We think the tradeoff is the right one for a tool that is fundamentally a calendar, not an aggregator.

For the things automation would help with — automatically detecting that you used a $15 Uber Cash credit, for example — we are exploring narrower opt-in approaches (transaction-level integrations that you can grant per-card and revoke any time) rather than a single broad bank-login flow. That work is downstream of the v1 release.

What data Cardier stores, plainly

The practical answer:

• On-device by default. Your card list and benefit tracking sits in local storage on your phone. The app works offline.
• Optional cloud sync if you create a Cardier account to sync across devices. Cloud sync is encrypted in transit and at rest.
• No transaction-level data. We do not collect what you spent or where you spent it. The app does not need it.
• No selling or sharing of your data. Cardier is a paid product. The subscription is the revenue model.

The longer-form version of all of this lives in our Privacy document and on the Security section of the homepage. The short version is above.

Why we made this choice

Two reasons. First, the design follows the work. A benefit tracker is a calendar problem and a catalog problem. Neither requires transaction data. Building around a narrower surface means fewer places for things to go wrong.

Second, the user we are building for is a premium cardholder who has already thought about data sensitivity. The cardholder paying $695/year for a Platinum is a person whose financial data is worth more than the average — and more often, a person who has already opted out of broad data sharing wherever they can. Asking that user to hand over a bank login as a prerequisite to using a tracker has always felt like the wrong question to open with.

What we are not saying

This piece is not an argument that aggregator-based finance apps are bad. They serve a different job — broad cash-flow visibility, automated categorization, net-worth tracking — that genuinely does require transaction data. If that is what you need, an aggregator is the right tool. Cardier is built for a narrower problem, and the narrower problem does not need that surface.

We also are not claiming we are the only credit-card tool that takes this position. We are saying we considered the design tradeoff carefully and made the call we think is right for what Cardier does.