Your financial data never leaves your device. The app has no account system, no server, and no analytics service. The only outbound network requests are to fetch bank logos from a third-party service. Nothing you enter — balances, bank names, interest rates, goal names — is ever transmitted anywhere.
CD Ladder is an independent iOS application developed by Joe Hallissey. This policy covers how the app handles your information. Questions can be directed to the contact information at the bottom of this document.
All data is stored locally on your device using Apple's SwiftData framework. This includes:
None of this data is transmitted to any server. It exists only on your device and, if you enable iCloud, in your private iCloud account (see iCloud section below).
The app does not collect, store, or transmit:
The app makes two kinds of outbound network requests:
When you select or search for a bank, the app requests a logo image from logo.dev (img.logo.dev). The request includes the bank's domain name (e.g. ally.com) as part of the URL. No financial data, balances, or personal information is included in these requests. logo.dev's privacy policy is available at logo.dev.
The app includes code to query the FDIC's public BankFind API to supplement the bundled list of institutions. This feature is currently disabled. When enabled, it would send a bank name search string to banks.data.fdic.gov, a public U.S. government API. No personal or financial data would be included.
No other network requests are made.
The app maintains a local diagnostic log file (cdtracker-events.jsonl) stored on your device. This log records operational events such as:
This log never leaves your device automatically. You can view it at any time in Settings → About → View & Send Logs. If you contact support and are asked to share it, you can do so manually using the share sheet in that same screen. The log contains no balances, interest rates, or identifying personal information.
Settings → Export my data generates a JSON file containing all your goals and CD records. This file is created locally and shared only if you explicitly choose to send it somewhere (e.g. email, Files, AirDrop). The export is not sent to any server automatically.
Because this file contains your financial planning data, the app warns you that it is sensitive and, if you have Face ID / Touch ID app lock enabled, requires biometric authentication before generating the export.
A future version of the app plans to offer optional iCloud sync, which would store your data in your private iCloud account using Apple's CloudKit framework. When this feature ships, it will be opt-in, and your data will be governed by Apple's iCloud Terms and Conditions in addition to this policy. The current version of the app does not use iCloud.
If you enable app lock in Settings, the app uses Apple's LocalAuthentication framework to require Face ID or Touch ID before displaying your data. Biometric data is processed entirely by Apple's secure enclave — the app never sees or stores your biometric information.
If you enable maturity reminders, the app schedules local notifications on your device using Apple's UserNotifications framework. These notifications are generated and delivered entirely on-device. No notification content is routed through any external server.
Notification text never includes dollar amounts or other sensitive financial values.
This app is not directed at children under 13 and does not knowingly collect information from children. If you believe a child has entered personal information into the app, please contact us and we will assist in removing it from the device.
Because the app does not collect, sell, or share personal information with third parties, most CCPA rights (right to know, right to delete, right to opt out of sale) are satisfied by default — there is nothing to disclose, delete, or opt out of. If you have questions specific to your California privacy rights, please contact us.
If we make material changes to this policy, we will update the effective date at the top of this document and, where appropriate, notify users through the App Store update notes. Continued use of the app after changes constitutes acceptance of the updated policy.
For privacy questions, data requests, or to send diagnostic logs to the developer: