A private dashboard that shows one person their own bank balances and net worth over time. It is not a commercial product and is not offered to anyone else.
Clearview reads balances and transaction history from its operator's own financial accounts and displays them on a single dashboard, so that account balances scattered across a dozen institutions can be seen in one place and tracked over time.
It has exactly one user, who is also the person who wrote it and the owner of every account it connects to. There are no other users, no customers, no sign-up, and no public access to the running application.
Theodore Caputi
Sole operator, developer, and user
Contact for data privacy and security inquiries, including
from financial institutions:
tcaputi@gmail.com
When a financial institution is connected, the following is retrieved through that institution's authorized API:
The data is used for one purpose: displaying the operator's own balances, transactions, and net-worth history back to the operator. It is never sold, shared, transferred to any third party, used for advertising, used to train anything, or used to make decisions about any person.
Connections are established through licensed data aggregators. Each connection is initiated by the operator and authenticated directly with the institution inside the aggregator's own flow.
| Aggregator | Status |
|---|---|
| Plaid | active |
| SnapTrade | active |
| Sophtron | active |
| Quiltt | active |
| Teller | withdrawn by the vendor in July 2026; no longer used |
Two places, and both are described here because a partial answer is not an answer:
Access tokens are encrypted with Fernet (AES-128-CBC with HMAC-SHA256) before they are stored. The copy held in the cloud database is ciphertext only: the encryption key is held in the macOS Keychain on the operator's machine and is never transmitted, so the cloud component cannot decrypt a token even in principle.
The dashboard is not reachable from the open internet. It sits behind Cloudflare Access, which requires authentication against a Google identity with multi-factor authentication before any request reaches the application. Anonymous traffic is redirected to that login and never sees application data. All traffic uses TLS 1.2 or above.
Balance and transaction history is retained so that net worth can be charted over time; that history is the point of the application.
The operator can disconnect any institution from within the dashboard, which revokes the connection at the aggregator and stops all further data retrieval. Stored data for a disconnected institution can be deleted outright on request.
An institution or an account holder who wants a connection terminated or data deleted can write to tcaputi@gmail.com.