Privacy Policy

Originally published: 16 September 2025

Last updated: 10 November 2026 (malife Pro and optional cloud transcription)

This Privacy Policy explains how Alexander Zakharov (“we”, “us”, “our”) processes your personal data when you use the malife mobile application and related services.

Controller: Alexander Zakharov, Turmweg 31, 20148 Hamburg, Germany

Email: privacy@malife.app

Target markets: Global

DPO: Not appointed

1. What this policy covers

  • The malife app and any in‑app/website features we operate.
  • It does not cover third‑party websites you may access via links.

We keep this policy clear and practical. The sections below explain the data used by each feature and your controls.

2. Data we process

We only collect what we need to provide the service. We do not sell data or use cross‑app advertising trackers.

Account & Profile

  • What: Name, email address (incl. Apple private relay), avatar, user identifiers.
  • Why: Create your account, authenticate you, sync your data across devices.
  • Source: You; sign‑in providers (Apple/Google).
  • Retention: Until account deletion (see §8).

User Content (synced)

  • What: Life Areas, Projects, Tasks, subtasks, tags, notes, journal entries, calendar events (if Google Calendar is connected).
  • Attachments: Photos, videos, audio files and documents you choose to upload (per-file limit 50 MB). Audio file attachments are separate from task dictation, which is described below.
  • Why: Core functionality (organize and sync your content).
  • Storage: Firebase Firestore data is stored in eur3; uploaded files are stored in the EU. Processing locations are described in §4.
  • Retention: Until you delete items or delete your account.

Focus Timer History

  • What: Session durations, streaks, timer preferences.
  • Why: Provide focus features and statistics.
  • Retention: Until deletion or account closure.

Voice Input (dictation)

On Apple devices, task dictation uses Apple’s Speech framework. Recognition may happen on your device or use Apple’s servers, depending on the device, language and system service. malife does not require on-device-only recognition. Apple dictation itself does not upload a raw recording to malife storage. In version 2.3.0 and later, with AI assistance enabled and cloud transcription available, the app can also record your voice capture and send the recording, device language and recognition hints (such as life-area and project names) through malife’s authenticated backend to OpenAI for transcription. A temporary local file is removed after reading or discarding it; files left after an interruption are cleaned up on a later recording attempt. The backend sends the audio for transcription without saving it as an attachment. The returned transcript can be processed as described below. If cloud transcription is unavailable, the app keeps the Apple dictation text. Apple’s processing is governed by its Speech, Siri and Dictation privacy information and your system settings.

  • AI parsing: When AI assistance is enabled in updated versions, transcripts, with life-area and project names and identifiers, can be sent to OpenAI to suggest task fields. With AI assistance off, the transcript remains available for manual task entry. Task parsing sends text; optional cloud transcription is a separate audio request covered by AI assistance in version 2.3.0 and later. Turning AI assistance off stops new cloud recordings and uploads, while Apple speech recognition remains governed by its separate system settings. Other AI features use different content, described in §5.
  • Controls: You can disable speech recognition at Settings → Privacy & Security → Speech Recognition; “Improve Siri & Dictation” may allow Apple to retain samples if you opt in.

Google Calendar Integration (Optional)

If you choose to connect your Google Calendar:

  • What: Calendar event data (titles, times, descriptions, locations, attendees), calendar list info, sync tokens.
  • Why: Display your calendar events alongside tasks to help you see your full schedule.
  • Access scope: Read-only (calendar.readonly), so this integration cannot modify your Google Calendar.
  • Storage: Events are cached locally for offline viewing, with sync preferences in app settings. AI planning can also process event titles and times supplied as context; see §5.
  • Sync window: A full refresh requests events from 30 days in the past to 90 days in the future. Incremental sync may update cached events outside that window; old cached events are cleaned up during sync.
  • Provider: Google Calendar API.
  • Controls: You can disconnect at any time in Settings → Google Calendar. Disconnecting removes all cached calendar data from your device.
  • Deletion: Disconnecting removes the calendar cache and sync state. Tasks or planning results you have saved separately remain account content until you delete them or your account.
  • Optional: This feature is entirely optional and not required to use the app.

Device Permissions

  • Microphone: Only while you actively use voice input; no background recording.
  • Photos/Camera/Files: Access through system pickers to add attachments; we do not scan your library.
  • Location/Contacts permissions: We do not request access to your device location or address book. Content you provide, including connected calendar events, can contain locations or contact details.
  • Push notifications: Reminders only; no marketing pushes. To deliver reminders and authorize notification actions, we store your account ID, an app-installation identifier, a notification delivery token and a notification-session identifier. These records are linked to your account and used for delivery and security, not advertising.

Purchases

  • What: Your internal account identifier, purchase history and receipts, product identifiers, subscription and trial status, access grants, and technical app/device information needed for purchase validation and support.
  • Why: Validate and restore purchases, keep Pro access synchronized, provide eligible founder grants and trial reminders, and maintain subscription records. Version 2.3.0 introduces optional malife Pro; earlier app versions may not offer a paid subscription.
  • Providers: Apple In‑App Purchase handles payment. RevenueCat validates purchase records and manages subscription access using your internal account identifier. malife does not receive your payment-card details. Subscription status is synchronized to malife’s backend.
  • Retention: As needed for purchase history, fraud prevention, and tax compliance.

Analytics & Diagnostics

  • What: Usage events, feature flags, app/device information and crash diagnostics. Installation identifiers and account-linked records are personal data; they are not anonymous merely because they omit your name.
  • Approximate location: When usage analytics is enabled, Google Analytics can derive general location from masked network IP addresses. This does not use device location permission. See Google’s Analytics data-disclosure information.
  • Why: Understand feature use and diagnose failures.
  • Provider: Firebase Analytics and Crashlytics (Google).
  • Controls in updated versions: Settings → Optional data sharing provides separate Usage analytics and Crash reports switches, off by default. Disabling a switch stops future optional collection; it does not automatically erase reports already sent. Crash-report changes can require an app restart.
  • Older versions: Earlier releases could send analytics without these controls and could associate reports with your internal account ID. If the controls are unavailable in your installed version, contact us about an update or deletion request.
  • Service metadata: Authentication, sync, update checks and notification delivery also process technical information such as app and operating-system versions, network request metadata, installation identifiers and configuration information. The optional analytics and crash-report switches do not turn off these underlying services or all of their technical diagnostics.
  • Retention: Analytics retention depends on the configured Google Analytics settings and report type. Firebase states that Crashlytics starts removing crash data and associated identifiers after 90 days. See Firebase’s privacy and retention information.

Activation & Retention Tracking

Optional activation measurements help us understand onboarding and feature use. They are linked to your account and are not anonymous:

  • What: Timestamps of first-time actions (e.g., first task created, first project created, first task completed, first voice input used), task creation count, days active per week.
  • Why: Measure product activation, identify successful onboarding patterns, and improve the new user experience.
  • Storage: Firebase Firestore in EU region (eur3) under your user account.
  • Tracking window: In updated clients, activation milestones are limited to the first 7 days after signup, and account-linked retention measurements stop 97 days after signup. Collection also requires Usage analytics to be enabled.
  • Data collected:
    • Activation milestones: 4 timestamps + task count (only during first 7 days)
    • Retention metrics: App open dates, daily active flags
  • Account linkage: These records include an internal user ID and behavioral timestamps. They can be associated with your account.
  • Retention: The server selects these records for removal 97 days after account creation, comprising the seven-day activation window and 90 further days. Cleanup runs periodically and physical removal is asynchronous. Recovery copies have separate retention, described in §7.
  • Deletion: Automatically removed when you delete your account.
  • Controls: Updated clients require your optional Usage analytics choice. Functional onboarding-checklist progress is separate and remains available when analytics is off.

Registration notices

Our backend sends a new-account notice to an administrator through Telegram, including your display name when available. The notice does not include your email, account identifier or app content. Telegram receives the notice and its timing. Earlier notices could include other account details. In-app account deletion does not automatically remove historical Telegram messages; contact us about those records or a deletion request.

Sensitive & Children’s data

  • Sensitive content: Journal prompts can ask about sleep, energy and mood. Your answers are saved and synced as journal content and may reveal health information. Notes and tasks can also contain sensitive information you choose to enter. When AI assistance is enabled, requesting a journal reflection shares the selected entry and recent reflection context as described in §5.
  • We do not target minors; the app is intended for 13+.
  • The app is not a medical device and does not provide medical advice.

3. Purposes & legal bases (GDPR)

We rely on these legal bases:

  • Contract (Art. 6(1)(b) GDPR): Provide and improve core app functions; account creation; sync; reminders; purchases.
  • Consent (Art. 6(1)(a)): Optional analytics and crash reporting in updated versions, optional AI sharing where presented for confirmation, Google Calendar integration (read-only calendar access), and push reminders where required by your platform settings. You can turn off optional sharing and disconnect integrations; the AI assistance choice applies across your account in updated versions, as explained in §5.
  • Legitimate interests (Art. 6(1)(f)): Security, fraud prevention and necessary operational diagnostics. Optional usage analytics and crash-report sharing are described separately above. We use access restrictions and data minimization to protect personal data; account and installation identifiers are not treated as anonymous.

malife is not a medical service. Journal answers and other free-text content can nevertheless contain sensitive personal information that you choose to enter.

4. Where your data is stored

  • Primary storage: Firestore in eur3 and file storage in the EU, with encryption in transit and at rest. Backend functions also process data in the United States. Provider and telemetry processing can occur in other locations.
  • Access control: Account authentication, data-access rules and service permissions restrict access to account data and backend operations.
  • Backups & logs: Recovery history and logs have different retention periods. See §7 for the currently configured windows and exceptions.

5. AI features

malife uses OpenAI for text-based AI features and, in version 2.3.0 and later, optional voice-recording transcription. Updated versions ask once during setup, or before first use for existing accounts. One account-wide choice covers task assistance, voice task parsing, setup suggestions and journal reflections, and in version 2.3.0 and later optional cloud transcription. You can enable or disable it under Settings → AI assistance. We store the choice in your private account settings and synchronize it across updated devices. Earlier task-only or voice-only permissions do not automatically become this broader permission. The content sent depends on the feature:

  • Task assistance: After you enable sharing in an updated version, new-task titles and notes, plus life-area and project names and identifiers, can be sent to OpenAI for organization and priority suggestions. Opening Inbox can also send unorganized tasks for suggestions. The shared AI assistance setting controls these requests. Manual task entry and organization remain available with sharing off.
  • Setup suggestions: With AI assistance enabled, setup answers, life-area and project names, goals and any profession entered for demo content can be sent to OpenAI for life-area, project or task suggestions. Manual setup remains available with AI off.
  • Voice task parsing: With AI assistance enabled, transcripts and life-area and project names and identifiers can be sent to OpenAI to suggest task fields. With it off, transcripts remain editable for manual entry. The shared setting avoids asking after every recording. It does not control Apple speech recognition.
  • Planning: The Morning Review service supports candidate task titles, notes, subtasks, deadlines, project/life-area names and activity signals. Available calendar context can include event titles, times and busy/free time. Version 2.3.0 introduces Morning Review. Free uses a deterministic review without a model call. Smart Morning Review requires Pro and AI assistance to be enabled; its planning context can be sent to OpenAI. Turning AI assistance off keeps the basic review available.
  • Journal reflection: The selected entry text and recurring themes/emotions from recent reflections. With AI assistance enabled, choosing to reflect on an entry sends this content without another sharing prompt. Saving a journal alone does not start reflection in updated versions. Automatic journal requests from older clients are blocked by the server.
  • Content you include: Text may contain names or sensitive information. Do not submit information you do not want the provider to process.
  • Provider handling: OpenAI training-sharing options are disabled for our API organization. Provider retention is separate from malife’s result-cache cleanup. OpenAI describes abuse-monitoring retention of up to 30 days by default, with legal and safety exceptions, in its API data controls documentation. Provider caching and previously stored requests have separate retention. We do not promise zero provider retention.
  • Earlier versions: Earlier app versions could start task, setup or voice AI requests without the updated sharing controls, and could start journal reflection after saving. Requests that omit the updated sharing acknowledgment are now rejected by the text AI service, so older versions may need an update to use those features. This describes earlier code behavior, not a determination that every user’s content was sent. Contact us about earlier processing or to exercise your data rights.

Turning AI assistance off stops new requests and discards pending results on updated devices when they receive the change. It cannot recall content already sent to OpenAI. A device that cannot verify the saved choice keeps AI off; if saving a change fails, retry as prompted. Manual features remain available. Text-completion requests do not include uploaded attachment files. Optional cloud transcription sends the voice recording as a separate request, as explained in §2. Turning AI assistance off cannot recall audio or text already sent. Voice onboarding is a separate feature and is currently disabled. AI responses can be inaccurate and should be reviewed before you rely on them.

6. International transfers

When data is processed outside the EEA (e.g., by backend functions in the United States, by OpenAI for AI features, by Apple/Google during sign-in/IAP, or by Google Calendar API when you enable calendar integration), we rely on appropriate safeguards such as Standard Contractual Clauses (SCCs) and vendor contractual commitments. We also implement technical and organizational measures (encryption, access control, data minimization, local caching).

When network-based Apple transcription is used, processing is performed by Apple pursuant to its terms and may involve international transfers managed by Apple.

7. How long we keep data (retention)

  • User content (tasks, projects, journals, attachments): Kept until you delete items or delete your account.
  • Google Calendar cache (if enabled): Stored locally on your device until you disconnect or delete your account.
  • AI request results: Access to transient cached results stops after 7 days; periodic cleanup removes result content asynchronously. Minimal account-linked request markers remain until account deletion to prevent duplicate paid requests. Saved reflections and planning results are account content, not transient caches.
  • Operational logs: The default project log bucket retains logs for 30 days; the required audit-log bucket retains its records for 400 days. Provider and other service logs can have different schedules.
  • Purchases: As needed for transaction history, chargebacks, and tax law.
  • Recovery copies: Firestore point-in-time recovery and Storage soft-deleted files currently have 7-day recovery windows. Removing live data does not immediately erase these copies. These windows do not describe every export, provider copy or audit log.

Minimal account-deletion markers are retained to prevent deleted account data from becoming accessible again. Their account identifier remains personal data. If legal obligations require longer retention, such as for tax records, we retain the necessary records separately.

8. Your controls & rights

In‑app controls

  • Data export: Settings → Profile → Export your profile, life areas, projects, tasks, journal entries, and timer settings. Attachments metadata is included; large files can be requested via support.
  • Google Calendar: Settings → Google Calendar → Disconnect. Removes all cached calendar events and sync data from your device immediately.
  • Deletion: Settings → Profile → Delete account. After verification, deletion blocks account access and starts resumable cleanup. The app can show a pending state while cleanup finishes. It is not immediate physical erasure of all data; recovery copies, audit logs and minimal deletion markers follow the separate handling described in §7.

GDPR/UK rights

You can request access, rectification, erasure, restriction, portability, or objection via privacy@malife.app. We verify identity and respond within one month. You may lodge a complaint with your local supervisory authority; in Germany, this is your state authority (e.g., Hamburg).

California/US rights

We do not sell or share personal information for cross‑context behavioral advertising. You can request access or deletion at privacy@malife.app.

9. Security

We use encryption, account authentication, access restrictions and security checks to protect your data. If a personal data breach occurs, we assess its impact and make notifications required by applicable law. Under the GDPR, reportable breaches must be notified to the supervisory authority without undue delay and, where feasible, within 72 hours of awareness. Where notification to affected people is required, including qualifying high-risk breaches, we notify them without undue delay.

10. Subprocessors (current)

  • Google Firebase (authentication, storage, backend processing, notifications, analytics and crash reporting), including EU primary data storage and US backend processing.
  • Google Calendar API (optional calendar integration, read-only access), Independent controller; processes calendar data when you enable this feature. Events cached locally on your device.
  • OpenAI (task assistance, optional cloud voice transcription, planning and journal reflection), including US processing.
  • RevenueCat (purchase validation and subscription access management), including processing of account identifiers, receipts, purchase history and technical app/device information. See RevenueCat’s privacy information.
  • Apple (Sign‑In, IAP), independent controller for purchase/auth flows.
  • Apple (Speech recognition, OS-level), independent controller when network-based transcription is used; see Apple’s Siri & Dictation privacy disclosures.
  • Google (Sign‑In), jurisdiction varies by Google.
  • ElevenLabs (voice onboarding, currently inactive), US.
  • Telegram (administrator registration notices), as described in §2. Historical messages require separate handling from deletion of live app data.

This list describes the main app integrations. Contact us for information about applicable processing agreements and international-transfer safeguards.

11. No ads & no tracking

  • No third‑party ads.
  • No cross‑app tracking.
  • No data sales.

12. Changes to this policy

We update this page and its “Last updated” date when this policy changes. The app links to this policy. Material changes will be communicated prominently.

Contact: privacy@malife.app