Privacy Policy for CostGlance
Last updated: 22 July 2026
1. Introduction
CostGlance (the “App”) helps users track expenses, manage cost groups, and plan budgets. This Privacy Policy explains what data the App collects, how it is used, stored, and shared, and the choices available to users.
2. Data Controller
If you have questions about this policy or your data, contact the developer using the support contact on the App Store / Google Play listing for CostGlance, or the contact method published with this Privacy Policy page.
3. Data We Collect
CostGlance does not require an account. Almost all data stays on your device.
- Financial Data (User-provided):
- Expense and budget records you create (cost name, amount, date, recurrence, description, group membership, and related metadata). Stored locally in the app’s storage (AsyncStorage). Included in backups if you export data.
- Preferences & Local Settings:
- Theme preference (`themeMode`), language/locale-related display settings, onboarding completion, quick-add preferences, and notification preferences (enablement, alert types, thresholds).
- A local cache of in-app purchase unlock state (whether Advanced Features are unlocked). Store purchases remain the source of truth and are re-verified with RevenueCat when possible.
- Local Notifications:
- If you enable notifications, the App schedules **on-device** reminders (for example month-start totals, high-cost due alerts, budget warnings, and recurring cost ending reminders). Notification titles and bodies may include amounts or cost names derived from your local data. Notification content is generated and displayed on your device; it is not uploaded to the developer’s servers.
- iOS Home Screen Widgets (optional, Advanced Features):
- When unlocked and added by you, widgets show summaries such as current-month spending and high-cost alerts. Summary data is shared from the App to widgets through an on-device App Group container. Widget data remains on your device and is not sent to the developer.
- Backup Files & Shared Content:
- When you export a backup, the exported JSON may contain your costs, budget data, theme preference, notification preferences, and backup metadata. Backups are generated and saved/shared only when you explicitly request them.
- Purchase / Store Data (via Apple, Google, and RevenueCat):
- Optional in-app purchases are processed by the App Store or Google Play. RevenueCat verifies transactions and entitlements. This may involve anonymous purchase identifiers and store transaction metadata handled by those services—not your expense ledger.
4. How We Use Data
- Core app functionality: storing and loading your expense and budget data so the App can operate offline and persist your data across launches.
- Notifications: scheduling local reminders you opt into, based on your costs, budgets, and notification preferences.
- Widgets: displaying on-device spending summaries on the iOS home screen when Advanced Features are unlocked.
- Backup & Restore: exporting and importing your dataset as a JSON file.
- In-app purchases: unlocking premium features (Advanced Features, including enhanced monthly insights and iOS widgets) via the store and RevenueCat.
- Basic UX preferences: theme, language, quick-add behavior, and related local settings.
- App updates: the App may use Expo’s update services to deliver app updates. That mechanism does not upload your expense or budget records to the developer.
5. Sharing & Third Parties
- In-app purchases: RevenueCat (`react-native-purchases`) verifies store transactions and entitlements. See [RevenueCat’s privacy policy](https://www.revenuecat.com/privacy). Apple and Google also process purchases under their own terms and privacy policies.
- Backup Export: when you share a backup file, you may send your expense, budget, and preference data to other apps or cloud services outside our control. The developer is not responsible for how third-party services handle exported files.
- On-device system features: iOS may display local notification content and widget content on your device lock screen / home screen according to your system settings. This is local display, not developer-operated sharing.
- No ads or tracking: CostGlance does not show ads, does not use advertising identifiers for tracking, and does not include analytics or crash-reporting SDKs that send your financial data to third parties.
- No automatic data sales: we do not sell your personal data.
6. Data Retention
- Data you create is retained locally until you delete it or use the app’s Wipe All Data function.
- Scheduled local notifications are cleared or rescheduled when you change preferences, wipe data, or remove the App.
- Widget summary data on device is cleared or locked when Advanced Features are not unlocked, or when you remove the widgets / App.
- Backup files you create are stored where you choose (device storage, cloud, or shared apps) and retention is subject to the storage/location you select.
7. User Controls
- Notifications: Settings → Notifications to enable/disable alerts and adjust related options. You can also revoke notification permission in iOS Settings.
- Widgets: add or remove CostGlance widgets from the iOS home screen. Advanced Features must be unlocked to use widget content.
- Delete/Wipe Data: Settings → Data Management → Wipe All Data to remove local app data.
- Export/Import: Use Export and Import in Settings to create or restore backups. Only export when you trust the destination.
- Purchases: Restore Purchases in Settings if you reinstall or change devices.
8. Security
- Data is stored on your device using AsyncStorage (and, for widgets, an on-device App Group container). We follow common best practices but cannot guarantee absolute security for local device storage.
- Backup files are plain JSON and should be treated as sensitive personal data — protect them like any file containing financial data.
9. Children’s Privacy
- CostGlance is not intended for children under 13. The app stores all data locally on the device and does not provide a remote wipe or delete option through the developer.
- If a child under 13 uses the app, the parent or guardian must delete the app and/or manually remove the app’s data from the device. The developer cannot access or erase data stored locally on the user’s device.
10. Changes to This Policy
- We may update this policy occasionally. The date at the top will reflect the last update.
11. Contact
- For privacy questions, contact the developer using the support contact on the App Store / Google Play listing, or the contact method published with this Privacy Policy page.