Privacy Policy

Overview

DayWallet is a personal money-planning app that helps you understand what you can safely spend each day. Your financial data is stored locally on your device by default and does not require an account to use.

This policy explains what information DayWallet stores, which third-party services may process data, and what choices you have.

1. Data You Enter — Stored Locally on Your Device

DayWallet stores the following information locally in an on-device database:

• Account balance and transaction history
• Bills, due dates, and payment status
• Income events and payment cycles
• App settings and preferences
• Notification preferences and schedules

This data never leaves your device unless you explicitly export it yourself. DayWallet does not require an account, login, or internet connection for any core budgeting feature.

2. What DayWallet Does Not Collect

DayWallet does not collect or access:

• Your contacts, photos, or camera
• Your precise or approximate location
• Your microphone or audio input
• Your bank account credentials or banking data
• Any financial data beyond what you manually enter

3. Notifications

If you enable notifications in Settings, DayWallet stores your reminder preferences on-device and requests permission from iOS to deliver local notifications.

Notifications are used only to deliver bill due date reminders, income arrival reminders, and daily check-in prompts. Notification content is generated on-device and is not transmitted to any server.

4. Advertising (Free Users)

Free users may see banner ads delivered by Google AdMob (Google LLC).

• If you allow tracking, personalised ads may be shown based on your interests
• If you decline tracking, only non-personalised ads are shown

You can change this at any time in iOS Settings → Privacy & Security → Tracking → DayWallet.

What Google AdMob may collect

• Advertising identifier (IDFA) — only if tracking is authorised
• Coarse location derived from IP address
• App interaction data for ad measurement and fraud prevention
• Device information including iOS version and screen size

Google Privacy Policy  ·  Google AdMob disclosure

Premium users never see ads regardless of tracking status.

5. In-App Purchases

DayWallet offers Premium subscriptions processed by Apple through the In-App Purchase framework. DayWallet does not receive or store your payment card details. Purchase processing and verification are handled by Apple. You can restore a previous purchase at any time using Restore Purchases in the app.

Subscription terms are governed by Apple’s standard End User License Agreement (EULA).

Apple Privacy Policy  ·  Apple Standard EULA / Terms of Use

6. Crash Reporting

DayWallet v1.0 does not include active crash reporting. The app contains optional Sentry integration which is only activated if configured at build time. The v1.0 App Store release does not have crash reporting enabled, so no crash data is transmitted.

7. Data Export

DayWallet Premium users can export transaction history to a CSV file via Settings. This export is initiated manually by you and saved to your device. DayWallet does not transmit this data anywhere.

8. Cloud Sync

DayWallet v1.0 does not offer cloud sync or account-based backup. All budgeting data remains on your device. If cloud sync is introduced in a future version, this policy will be updated before that feature is launched.

9. Data Retention and Deletion

Because all budgeting data is stored locally on your device, data remains until you edit, delete, or export it. You can permanently delete all app data using Settings → Clear all data. Uninstalling the app removes all locally stored data from your device.

10. Children

DayWallet is not directed at children under 13 and is not intended to knowingly collect personal information from children. If you believe a child has provided personal information through this app, contact us at the address below.

11. Your Choices

12. Third-Party Services

13. Changes to This Policy

When DayWallet adds new features that affect data practices, this policy will be updated before those features are released. The effective date at the top of this document will reflect the most recent revision.

14. Contact