AheadPay Privacy Policy

1. Data stored on your device

The pre-release implementation stores payment information locally on your device to support offline use without an account. Local-first does not mean that all app activity stays on your device: the Android Firebase services described below can process analytics, diagnostic, and messaging information.

• Payment titles, amounts, currencies, categories, due dates, recurrence rules, statuses, and completion information
• Custom category names, icons, and colors; reminder preferences and schedules
• Record identifiers, timestamps, deletion markers, and synchronization state used by development features
• Preferences such as theme, text size, language, and last-used currency, along with local reminder schedules. The current app uses the Gregorian calendar and has no calendar selector.

2. Optional accounts and synchronization

Optional Google sign-in and account synchronization code exists in development. These features are not offered as public services through this website, and you are not currently being invited to create a public AheadPay account.

The development implementation can process account details such as an identifier, email address, display name, profile image, and preferences. If enabled in a development environment, synchronization can transfer payment records, categories, reminders, statuses, and change information to Damo Studio's account service and keep a local copy for offline use. Sign-in credentials and a cached profile use platform secure storage. Signing in alone does not upload local guest payments; transferring them requires a separate choice during setup.

Before any account or synchronization service is offered publicly, Damo Studio will document its production data practices, including account setup, synchronization, retention, and deletion. This policy does not promise public access to those services.

3. Local reminders and device permissions

The current pre-release implementation schedules payment reminders locally on your device. Notifications can include the payment title, amount, due date, and category. This information may appear on your lock screen or notification panel, depending on your device settings.

Android requests notification permission and may request exact-alarm access for reminder timing. Scheduled reminders can be restored after a restart or app update. The native iOS implementation requests alert and sound authorization. Notification permission is separate from analytics and diagnostic collection.

The current Android implementation does not request access to contacts, precise location, camera, microphone, or photos. Payment reminders are not delivered through SMS or email.

4. Android analytics

In the current pre-release implementation, Firebase Analytics and Crashlytics collection are enabled in Android release builds. They are disabled in normal development builds unless explicitly enabled for testing. These services can operate without an account. There is no separate in-app telemetry consent switch.

Analytics helps Damo Studio understand feature use and improve usability. Firebase can process installation identifiers, device and operating-system details, app versions, session and engagement information, timestamps, and approximate region derived from network information. Automatically collected events may include first use, sessions, updates, and notification interactions.

Custom analytics covers screen views; reminder creation, editing, deletion, and status changes; theme and text-size changes; and push receipt and opening. Development account and synchronization features can also report sign-in, sign-out, and synchronization outcomes when enabled. Event details can include recurrence type, currency code, built-in category or the label 'custom,' status, setting values, and success or failure. Custom events exclude payment titles, amounts, due dates, custom category names, account identifiers, email addresses, credentials, and notification text. The app does not set an Analytics user ID or custom user properties.

5. Crash reporting

Android Firebase Crashlytics helps diagnose crashes and technical failures. Reports can include stack traces, crash and session identifiers, installation identifiers, timestamps, app version, device and operating-system details, and other diagnostic information collected by Firebase. Analytics activity may appear in crash reports.

The app's own error reports include an error type, stack trace, operation label, severity, app edition, and platform. They omit the original error message, do not attach account or payment records, and do not set a Crashlytics user ID. This filtering does not remove Firebase's own diagnostic information or native crash reports.

6. Android push messaging

The pre-release Android implementation includes Firebase Cloud Messaging for app announcements and updates. Initial messaging registration waits for notification permission. Messaging communicates with Google and uses a Firebase installation identifier. The current implementation does not register that identifier with Damo Studio's account service for account-targeted messages.

Revoking notification permission controls notification display; it does not itself unregister a previously registered Firebase installation or disable Analytics and Crashlytics. Local payment reminders are scheduled on your device rather than sent as remote payment messages. The current implementation does not initialize Firebase services on iOS.

7. Network communication and third-party services

The Android Firebase services described above communicate with Google. Optional sign-in and synchronization features, when enabled in development, can also communicate with Google and Damo Studio's account service. These connections expose network information, such as an IP address, to the receiving service. Local payment tracking is designed to work offline; remote services require connectivity.

Google processes information for its analytics, diagnostic, and messaging services under its applicable terms and privacy practices. Development sign-in and synchronization can also involve account and payment information as described in section 2. Google and infrastructure providers may process information outside your country. Production account-service details will be documented before public availability.

8. Advertising and financial services

The current pre-release implementation does not include an advertising SDK, in-app billing, or subscription purchases. AheadPay is designed to track payment obligations rather than execute payments. It does not provide banking or payment-processing services.

9. Retention, editing, and deletion

In the current pre-release implementation, payments can be edited or removed from active views. Removing a payment marks it as deleted rather than immediately erasing the stored record.

Local databases and preferences may persist until app storage is cleared or the app is uninstalled. Operating-system backups and platform secure storage can have separate retention behavior. Uninstalling does not itself delete information already sent to a remote service. Firebase information is subject to the relevant service retention settings and deletion processes.

Public account and synchronization services are not currently offered through this website. This website does not promise an operational account-deletion service or automatic account deletion. Production account-data retention periods and deletion procedures, including any limits affecting backups, will be documented before those services are offered publicly.

For privacy questions about the pre-release implementation or retained information, contact [email protected]. This contact address is for enquiries and is not a promise of an operational public account-deletion process.

10. Security

The current pre-release implementation uses app-local storage for payment records and platform secure storage for sign-in credentials used by development features. The development account connection uses HTTPS. These measures do not guarantee that local records are encrypted or that any storage or transmission method is completely secure. Protect access to your device and review notification and backup settings.

11. Children's privacy

AheadPay is designed for personal payment organization and is not directed at children. If you have a concern about a child's information in connection with the pre-release app, contact Damo Studio so the concern can be reviewed.

12. Changes to this policy

Damo Studio may update this Privacy Policy when AheadPay's features, services, or data practices change. The updated policy will be published on this page with a revised effective date. Production account, synchronization, retention, and deletion details will be documented before those services are offered publicly.

13. Contact

For questions about this Privacy Policy, retained information, or AheadPay's privacy practices, contact Damo Studio.

[email protected]