Helmora mark

Helmora Privacy Policy

Simple, local-first privacy.

Helmora is designed to reduce overwhelm, not create more of it. For the current MVP, app data is stored locally on the user’s device and the app does not require an account to get started.

Local first

Core app data is stored on the device for the current MVP.

No account required

Users can use Helmora without creating a login.

Optional permissions

Notifications and location are optional and tied to specific features.

User control

Users can reset demo data, remove content, or delete the app.

1. Information Helmora stores

Helmora can store information such as profile details, people and notes, mind items, prep lists, settings, and reminder preferences. In the current MVP, this information is stored locally on the device.

2. Permissions Helmora may request

Helmora may request access to:

  • Notifications, if the user turns on reminders for appointments, prep, or check-ins.
  • Location, if the user asks Helmora to suggest nearby food options in Decider.

The rest of the app can still be used without location access, and notification access is optional.

3. Data sharing

Helmora does not use third-party advertising SDKs in the current MVP. The app does not sell personal data. If future cloud sync or analytics features are added, this policy should be updated before those features are released.

4. Notifications and reminders

Reminder scheduling is handled on the device. Notification content is intended to stay concise and helpful, such as appointment, checklist, or reconnect reminders that the user has enabled.

5. User choices

Users can manage their information by:

  • Editing or deleting people, notes, mind items, prep lists, and templates inside the app.
  • Resetting demo data in Settings.
  • Removing the app from their device.

7. Policy updates

This policy may be updated as Helmora evolves. If important privacy behavior changes, the policy should be revised before those changes go live.

Last updated: April 4, 2026