Dayfuku

Privacy Policy

Effective: November 13, 2026

1. Controller and Contact

The controller responsible for processing personal data within the meaning of the General Data Protection Regulation (GDPR / DSGVO) is the provider identified in our Imprint.

For privacy questions or requests, please use our Contact page.

2. Scope and Overview

This Privacy Policy applies to the Dayfuku iOS app and to this website insofar as it provides legal information and contact links for the app.

Dayfuku follows a local-first architecture. Your journal content is stored on your device by default. The provider does not operate its own servers for storing your journal entries, notes, photos, or activity history.

Depending on which features you use, data may also be processed by Apple services, RevenueCat, and TelemetryDeck. This policy explains which data categories are involved, for what purposes they are processed, and what rights you have.

3. Data Stored in the App

The app stores the following categories of data locally on your device:

  • Journal content: entries, notes, mood selections, dates, timestamps, and activity logs.
  • Photos: images you capture or import for journal entries.
  • Journal context and metadata: optional app-generated metadata and non-HealthKit context associated with your entries, such as dates, timestamps, place labels, activity-related values, and similar contextual information created or imported by features you enable.
  • Apple Health import cache: if you enable Apple Health imports, the app may read and store selected HealthKit-derived values locally on your device, including step count, sleep analysis, workouts, and active energy burned.
  • App configuration: settings, reminder preferences, feature preferences, iCloud sync preference, dictation preferences, app lock preferences, and onboarding progress.
  • Local diagnostics: locally stored crash and error metadata used to help the app record failures on-device.

Legal basis: Art. 6(1)(b) GDPR for providing the app's functionality.

4. Apple Services and Optional App Features

The app can use Apple frameworks and services to provide optional features. These features can be disabled in the app or in iOS Settings where applicable.

  • iCloud Sync (CloudKit): if enabled, journal entries, photos, activity categories, activities, activity logs, and non-HealthKit entry context may be synchronized through your private iCloud database. Values imported from Apple Health/HealthKit are stored locally on your device and are not synchronized through iCloud/CloudKit.
  • Apple Health (HealthKit): if you enable Apple Health imports, Dayfuku may read selected HealthKit data types, including step count, sleep analysis, workouts, and active energy burned. These imported values are used only to add context to your journal and insights, are not used for advertising or marketing, and are not synchronized through iCloud/CloudKit.
  • Other device permissions and local processing features: if you enable relevant features, the app may use device permissions and local processing frameworks, such as location services, maps, camera, photo library access, microphone access, and on-device speech recognition or dictation models, in order to create entries, dictate notes, attach media, derive contextual information, or display saved data.
  • Notifications: used for reminder notifications you configure locally on your device. In addition, the app declares Apple background remote-notification capability used in connection with CloudKit sync behavior.
  • App Store and Apple ID: app downloads, billing, purchase and subscription handling, and refund handling are provided by Apple.

Legal basis: Art. 6(1)(a) GDPR for optional permissions you enable, and Art. 6(1)(b) GDPR where the processing is necessary to provide requested app functionality such as purchases, subscriptions, or optional iCloud sync.

5. Purchase and Subscription Management (RevenueCat)

Dayfuku Pro purchases and subscriptions are supported through RevenueCat. RevenueCat processes purchase, entitlement, and technical metadata needed to validate purchases, determine access, and provide purchase analytics.

The provider does not process App Store payments directly. For details, please refer to RevenueCat's Privacy Policy.

Legal basis: Art. 6(1)(b) GDPR for performance of the purchase or subscription contract.

6. Analytics and Diagnostics (TelemetryDeck)

The app uses TelemetryDeck, a privacy-focused analytics service provided by TelemetryDeck GmbH, Germany, for limited product analytics. The purpose is to understand how features are used and to improve onboarding, subscriptions, search, check-in flows, usability, stability, and overall product quality.

What is sent: a fixed list of app-defined events, such as which onboarding step was viewed or completed, the goal chosen during onboarding, whether a check-in was created and from where (for example the journal, onboarding, or a widget), whether a purchase screen was shown, or whether search or Insights were used, together with coarse values like yes/no flags, counts, and size ranges. The analytics software also sends its own events when the app is installed and when a session starts. Each event carries its time and technical metadata added by the analytics software, such as app version and build, device type, operating system version, language and region, time zone, screen size, and the day of week and hour of use. Events also include usage statistics, such as the first day the app was used, the number of days and sessions it was used on, session lengths, and a session identifier, which we use to understand how many people come back.

How you are counted: on first use, the app creates a random identifier for this installation and keeps it on your device. The app passes it to the analytics software, which hashes it before sending, so neither TelemetryDeck nor we receive the identifier itself. Events from the same installation can be linked to each other, so this data is pseudonymous rather than anonymous. The identifier is not your advertising identifier (IDFA) or your device's vendor identifier, it is not linked to your name, email, Apple Account, or purchases, and it is not used to track you across other apps or websites. According to TelemetryDeck, IP addresses are not stored. The app keeps the identifier in its settings, and the analytics software stores usage statistics (such as recent session start times and lengths) and events that have not been sent yet on your device; those unsent events contain the hashed identifier.

What is never sent: journal entries, notes, mood selections, activity names, place names or coordinates, photos, search queries, HealthKit-derived values, or other content you enter or import.

The legal basis is Art. 6(1)(f) GDPR. Our legitimate interest is improving Dayfuku based on how it is actually used, without collecting the content of your journal.

You can turn analytics off at any time in the app under Settings, Privacy, Share Usage Data. When you turn it off, the app stops recording and sending events and deletes the identifier, unsent events, and other analytics data from your device. A request that was already being sent at that moment may still reach TelemetryDeck. If you turn it on again, a new identifier is created. You can also object to this processing (Art. 21 GDPR) by contacting us. Because we cannot link the identifier to you, we generally cannot find or delete events that were already sent.

Analytics is on by default for new installations; if you updated from an earlier version, it starts off.

Earlier versions of the app also used TelemetryDeck. Those versions counted installations using a hashed version of your device's vendor identifier rather than a random identifier.

The app also stores certain crash and error diagnostics locally on-device. These local diagnostics are separate from TelemetryDeck analytics and are not uploaded, because the provider does not operate a backend for app content.

For details, please refer to TelemetryDeck's Privacy Policy.

7. Website and Contact Processing

This website is a static site. Based on the current site implementation, the provider does not use contact forms, advertising cookies, or website analytics scripts on these pages.

When you visit the website, the hosting provider may process technical access data that is necessary to deliver the site, such as IP address, request metadata, and server logs.

If you contact the provider by email or through a mailto: link, your message and related metadata are processed for the purpose of handling your request.

Legal basis: Art. 6(1)(f) GDPR for secure website delivery and responding to inquiries, and Art. 6(1)(b) GDPR where your request relates to a contractual relationship.

8. Recipients

Depending on how you use Dayfuku, personal data may be processed by the following recipients or service categories:

  • Apple: for App Store distribution, in-app purchases, Apple ID account handling, optional iCloud/CloudKit synchronization, Apple Health/HealthKit access, other device permission-related functionality, and notification delivery.
  • RevenueCat: for purchase and subscription entitlement handling.
  • TelemetryDeck: for limited product analytics.
  • Website hosting and email providers: to deliver this website and receive email inquiries.

9. International Transfers

Apple, RevenueCat, TelemetryDeck, and technical infrastructure providers may process data outside the European Union or European Economic Area, including in the United States, depending on their infrastructure and service configuration.

Where such processing occurs, it is governed by the relevant provider's legal and contractual safeguards. Please review the respective privacy policies of those providers for more information.

10. Data Retention

  • Local app data: remains on your device until you delete it, reset the app's data, or remove the app. This includes HealthKit-derived values imported from Apple Health. Resetting the app's data keeps your analytics choice and, if analytics is on, its identifier. Turning analytics off deletes the identifier and other stored analytics data but remembers your choice; removing the app deletes all of it.
  • iCloud data: remains in your iCloud account until you delete the relevant records or disable sync and remove the synced data. HealthKit-derived imported values are not part of Dayfuku's iCloud synchronization.
  • RevenueCat data: retained according to RevenueCat's policies and any applicable legal obligations.
  • TelemetryDeck analytics: retained according to TelemetryDeck's policies.
  • Email inquiries and website/server logs: retained only as long as needed for the relevant communication, security, or legal purpose.

11. Your Rights

Under the GDPR and the German Federal Data Protection Act (BDSG), you may have the following rights, subject to the applicable legal requirements:

  • Right of access (Art. 15 GDPR)
  • Right to rectification (Art. 16 GDPR)
  • Right to erasure (Art. 17 GDPR)
  • Right to restriction of processing (Art. 18 GDPR)
  • Right to data portability (Art. 20 GDPR)
  • Right to object (Art. 21 GDPR), in particular to processing based on legitimate interests
  • Right to withdraw consent (Art. 7(3) GDPR) for processing based on consent

Because Dayfuku stores most app content locally on your device, you can directly view, edit, delete, or reset much of your data yourself in the app and through your device settings. For third-party or contact-related processing, you may contact the provider via the Contact page.

12. Right to Lodge a Complaint

You have the right to lodge a complaint with a data protection supervisory authority, in particular in the EU member state of your habitual residence, place of work, or the place of the alleged infringement (Art. 77 GDPR).

As the provider is based in Germany, the competent supervisory authorities are the data protection authorities of the German federal states. A list is available from the German Federal Commissioner for Data Protection and Freedom of Information (BfDI).

13. Automated Decision-Making

The provider does not use automated decision-making or profiling within the meaning of Art. 22 GDPR that produces legal effects or similarly significant effects on you.

14. Children's Privacy

The app is not directed at children under the age of 16 and the provider does not knowingly collect personal data from children under 16.

15. Changes to This Policy

This Privacy Policy may be updated from time to time. The version published on this page is the current version and includes its effective date.