Privacy Policy

1. About this policy

This Privacy Policy applies to Momendoom, a time-awareness application developed by James Michael D. Magnaye (ratatatatcode). It explains how the app accesses, stores, uses, and shares information.

Momendoom records time you choose to track as Doom or Productive sessions. It does not monitor other apps, websites, browsing history, or your device activity. No account or sign-in is required.

2. Information stored and how it is used

Momendoom stores session identifiers, session type (Doom or Productive), start and end times, optional notes and tags, and app preferences such as notification and introduction settings. This information is stored locally in the app’s SQLite database on your device.

The app uses these records to run timers, display session history, calculate totals and charts, and let you edit, delete, export, or restore your records. All session summaries and analysis run locally. Notes and tags are not sent to AI services or analyzed remotely.

The app does not request your name, email address, contacts, location, camera, microphone, advertising identifier, or payment details. It has no backend, cloud sync, advertising SDK, third-party analytics, or telemetry, and does not automatically send your session data to the developer.

3. Notifications and file access

If you enable the optional active-session notification, Momendoom requests notification permission. Notifications are generated locally and can show your active session and elapsed time, including on a lock screen according to your device settings. You can turn them off in the app or device settings; declining permission does not prevent session tracking.

Importing a backup uses the system file picker to access the file you select. Exporting uses the system share sheet or a browser download. The app does not require broad access to your files or storage, app-usage access, or accessibility monitoring permissions.

4. Sharing and backups

The developer does not receive, sell, rent, or share your locally stored session records. Momendoom does not automatically upload these records to external services.

When you choose Export JSON, the backup contains completed sessions, notes, and tags in unencrypted, readable text. Active sessions and device settings are excluded. Any app, person, storage provider, or cloud service you choose as the export destination can access that file under its own privacy practices. Only share backups with destinations you trust.

Importing reads the backup you select and merges valid records into your local database. Android automatic app backup is disabled in the current app configuration. On iOS, device backups may include app data depending on your operating-system settings. Operating-system backups are controlled by the platform, rather than by a Momendoom cloud-sync service.

5. Retention and deletion

Local session records and preferences remain on your device until you remove them or clear the app’s storage. You can edit or remove notes and tags and delete completed sessions from session details. In Settings, use Delete all local data to clear session records and preferences and cancel session notifications. You can also clear app storage through Android settings or uninstall the app to remove its local app storage.

Delete all local data also attempts to remove the app-owned export cache. Temporary import copies are removed after reading. Successful share copies may remain in a private cache so the receiving app can finish reading them; exports older than one day are pruned on the next export, and the operating system may also clear the cache.

Deleting app data does not delete backups you saved or shared elsewhere, or copies in device backups. Delete those copies separately with the relevant storage or backup provider. Local deletion is a logical database deletion and is not a guaranteed forensic secure erase.

There is no Momendoom account or server-side session history for the developer to delete. Because the developer cannot access your local database, deleting your local records must be done on your device.

6. Data security

Momendoom uses the operating system’s app storage protections. Its local SQLite database does not use additional application-level encryption, and exported JSON backups are not encrypted. Protect your device with a screen lock, take care when entering sensitive information in notes, and store backups securely. No storage method can guarantee absolute security.

7. Information you send when contacting us

If you email the developer, you voluntarily provide your email address, message, and any attachments. This information is used to respond to your inquiry and resolve support or privacy issues. Email providers process the communication to deliver and store it under their own policies. Please do not send session backups or sensitive notes unless necessary for your request.

Support correspondence is retained only as long as needed to address the inquiry and meet any applicable legal obligations. You may contact the developer to request deletion of correspondence you have provided, subject to those obligations.

8. Children’s privacy

Momendoom does not knowingly collect children’s personal information through a remote service. The local-storage practices described in this policy apply to everyone using the app. If you believe a child has sent personal information to the developer through support, contact us so we can address it and delete it where appropriate.

9. Changes to this policy

This policy may be updated when the app or its data practices change. Updates will appear on this page with a revised effective date. Material changes that require additional notice or consent will be communicated as required before those practices take effect.