PRIVACY POLICY

Provider and scope

Moodinator is provided by Maximilian Mauroner (Lab4Code), Italy. It is a local-first mood tracking application with no developer-operated server, user account system, or cloud synchronization.

Moodinator does not use advertising or analytics. Lab4Code does not receive mood data or app settings. Data can still leave the device through user-directed exports, sharing, backups, external support actions, feedback, and operating-system features as described below.

Information stored on the device

Moodinator stores information the user chooses to enter or configure, including:

• Mood data: ratings on the 0–10 scale, timestamps, recorded UTC offsets, notes, emotions, context tags, energy values, and related history.
• Settings: entry preferences, display preferences, onboarding state, and other app configuration.
• Reminders: local notification titles, messages, schedules, permission state, and scheduling identifiers.
• App lock data: whether app lock and biometrics are enabled, PIN length, failed-attempt state, and a salted hash of the PIN.
• Backup metadata: the selected backup folder and time of the latest backup.

New entries retain the UTC offset at their recorded time so calendar days remain stable when the user travels. Exports and backups include this offset. Older entries without a recorded offset use the current device timezone.

Storage and security

Mood data is stored in the app's local SQLite database inside the operating system's app sandbox. On Android, Moodinator does not apply database-level encryption to that SQLite database. The app sandbox, device encryption, screen lock, and other platform protections may reduce access, but app lock is not database encryption.

If an app-lock PIN is set, Moodinator stores a salted hash, not the plaintext PIN, in the operating system's secure storage. Biometric enrollment and matching are handled by the operating system; Moodinator does not receive or store biometric templates.

No security measure guarantees absolute protection. Users should protect unlocked devices and exported files, use a device passcode, and keep the operating system updated.

Local notifications

Moodinator schedules reminder notifications locally after the user enables them and grants permission. Reminder titles and messages may be visible on the lock screen or in notification history, depending on device settings. Moodinator does not use remote push notifications.

Exports and backups

Mood-history exports and backups are plaintext JSON files. Therapy exports are plaintext CSV files. Moodinator does not encrypt these files.

On Android, a JSON export is written to a folder the user selects. On iOS, JSON exports are written temporarily to the app cache and offered to the operating-system share sheet. Therapy CSV exports are also written temporarily to the app cache and offered to the share sheet. If sharing is unavailable, the app can offer to copy the full JSON or CSV content to the device clipboard, where other apps may be able to read it.

Moodinator attempts to delete its temporary cache export after the export flow, but an interrupted or failed share can leave a temporary file until the operating system clears the app cache. A user may choose another app or destination, including a cloud-backed storage provider. After data is copied, shared, or saved outside Moodinator's private storage, the destination provider's and operating system's practices apply.

Moodinator registers a periodic backup task with the operating system. The operating system decides whether and when it runs; execution is not guaranteed. After backup storage is available, the task may create a backup automatically and throttles successful backups to at most once per week. On Android, no backup can be created until the user selects a folder. On iOS, the app's Documents area is the default.

Retention cleanup keeps the eight newest app-managed moodinator-backup-*.json files it can identify in managed backup locations and deletes older identified backups. It does not delete arbitrary exports, renamed copies, clipboard contents, or copies held by another app or provider.

External support actions and feedback

For ratings 9 and 10, Moodinator offers crisis-support actions. If the user chooses one, the app asks the operating system to open the phone or messaging app for U.S. 988, or opens Find A Helpline (opens in a new tab). These actions are user-initiated. Moodinator does not monitor entries, contact emergency services, or send the mood entry to those services. The carrier, browser, operating system, or selected service may process information under its own terms and privacy policy.

If the user chooses Send Feedback, Moodinator opens a prefilled issue form on GitHub. The template does not include mood entries, app settings, or device metadata. Anything the user adds and submits is shared with GitHub and posted publicly in the Moodinator repository, subject to GitHub's terms and privacy policy. Users should not include private mood entries or other sensitive information.

Data sharing and sale

Lab4Code does not operate servers that receive Moodinator data and does not sell it. Moodinator does not use advertising or analytics.

Data can leave the app when the user deliberately exports, shares, copies, imports, opens an external support action, or submits feedback to GitHub; when an operating-system-scheduled periodic backup runs after backup storage is available; or when the operating system handles device backup or transfer outside Lab4Code's control.

User control and deletion

Users can delete an individual mood entry, use Settings > Data & Backups > Delete Mood Data to delete mood history, and export or back up mood history before deleting it.

Delete Mood Data removes mood rows, mood–emotion link records, and database emotion records used by that history. It does not delete the user-visible Emotion List presets, context-tag presets, other settings, reminders, app-lock settings or secure-storage PIN hash, or export and backup files saved outside the app.

Uninstalling normally removes app-sandbox data, but external files remain, secure storage and platform backups may behave differently by operating system, and platform backup or device-transfer features may retain or restore data. External copies must be reviewed and deleted at their destination.

Because Moodinator has no account and Lab4Code does not hold a server-side copy of app data, there is no developer-side account or app-data deletion request to perform.

Children

Moodinator is not directed at children under 13. Because Lab4Code does not receive app data, it does not knowingly collect personal information from children through developer-operated servers.

Changes and contact

Material changes will be identified by updating the date at the top of this policy.

Questions can be sent to support@lab4code.com.

Maximilian Mauroner (Lab4Code)
Italy