The easiest way to make a subscription tracker feel magical is to connect it to a bank account. Transactions appear automatically. Setup becomes almost invisible. The product can promise that it finds everything for you.
Glint takes the less magical route: you add subscriptions yourself.
That is not because automatic importing is uninteresting. It is because every convenience creates a second question: what does the app need to know about you in order to provide it?
The product boundary comes first
Glint is meant to answer a focused question: what recurring charges have I chosen, when will they renew, and what are they costing me over time?
It does not need a bank connection to answer that question. It does not need card details, transaction history, an account on a Glint server, or a profile that follows you around the internet.
The core database lives on the device. Renewal reminders are scheduled locally. The app can still show monthly and yearly equivalents, upcoming charges, categories, and spending insights without becoming another service that holds a copy of someone’s financial life.
That boundary makes the app less automatic. It also makes the privacy promise understandable without a page of exceptions: Glint does not connect to your bank because it does not need to.
Manual entry has a real cost
There is no point pretending that typing information is as effortless as importing it. A manual tracker asks the user to remember the subscriptions they already have, enter the amount and renewal date, and keep that information current.
The design has to earn that effort.
That means keeping the form short, offering a quick-start path, remembering sensible defaults, supporting the currencies and billing cycles people actually use, and making edits painless. It also means being honest about accuracy. Glint can only remind you about the information you give it; it cannot discover a forgotten charge hiding in a bank statement.
Good privacy does not remove friction by itself. It gives the product team a reason to remove every other unnecessary friction.
Optional services should remain optional
Glint does make a few network requests, but each one is tied to a feature the user can understand.
- Brand search can send a domain or typed keyword to Brandfetch so the app can show a recognisable logo. Leave that field empty and Glint falls back to an initials tile.
- Exchange rates come from a public rate service. No subscription details are included in that request.
- Pro users can turn on backup to their own iCloud or Google Drive app-data area. Glint does not receive a copy.
- Purchases are processed by Apple or Google and validated through RevenueCat.
The useful test is not “does the app ever use the internet?” The useful test is “can a person explain why this data leaves the device, what receives it, and what happens if they decline?”
Convenience is not the only form of quality
Products are often judged by how many steps they remove. That is fair—but incomplete.
Sometimes a deliberate step buys clarity, control, or a smaller trust surface. Adding a subscription manually is a little slower. In return, the user decides exactly what Glint knows, and the app remains useful without a Glint account or a bank connection.
That is the tradeoff. It will not suit everyone, and it does not need to. A focused product becomes easier to build when it is clear about the kind of convenience it will not pursue.
You can learn more about Glint at https://glintsubscriptions.com/.