Morrowhale · Privacy
Your space. Your data.
How data is processed when you visit the website, use Morrowhale, share Pause Post or contact us.
1. Controller and scope
The provider of Morrowhale responsible for the processing described here is:
Tim Fengler
Nettelhoff 3
46348 Raesfeld
Germany
Email: support@morrowhale.app
This notice covers morrowhale.app, the separate Pause Post preview at share.morrowhale.app, the Morrowhale app, support and, where applicable, TestFlight. Apple's privacy information also applies to processing for its own purposes, such as your Apple Account or TestFlight. CloudKit synchronization is described in section 7.
Updated: 3 November 2026. This notice describes Morrowhale 1.0 and its website and Pause Post features. Older test versions may lack or differ in photo, export and deletion features; older versions may retain more original content when entries are removed. You can also email us with questions about your data.
2. Visiting the website
When you visit this website, the hosting service processes technical connection and access data. This may include your IP address, date and time, requested address or file, response status, amount of data transferred, and browser and operating system information. This information may be stored in server logs.
The purposes are delivering the website, maintaining stable and secure operation, and detecting and investigating faults or misuse. The legal basis is Article 6(1)(f) GDPR. Our legitimate interest is an available, functional website protected against misuse.
We use Hostinger to host the main website and provide the support mailbox. Information about Hostinger's published data processing terms and subprocessors is available in its Data Processing Agreement. Its published Terms of Service are also available. The separate Pause Post infrastructure is described in section 3.
No blanket retention period for technical hosting logs is guaranteed here. A time filter in a hosting dashboard does not establish that all logs and backups have been deleted. Hosting operations must be distinguished from copies kept by the operator.
3. Website features and local browser processing
The main website has no embedded advertising or analytics services and no contact form. Fonts, images and scripts are served by the website itself. German and English use separate page paths. Your language choice and the automatic light or dark appearance are not stored as personal browser preferences; appearance follows your system setting.
The optional breathing demo on the homepage lasts 32 seconds. It runs only in your open browser, does not measure your breathing or body data, and does not use your camera or microphone. Its sequence and progress are not stored, sent to an application server or added to any app history. Leaving or reloading the page leaves no demo history behind. Loading the page and its files involves the technical connection data described in section 2.
Hostinger's delivery and security infrastructure may process technical access logs and hosting statistics, such as request counts or countries inferred from IP addresses. This differs from embedded analytics or advertising scripts. The absence of those scripts does not mean that hosting processes no connection data.
Pause Post in the browser
A separate static preview for shared breathing rhythms is provided at share.morrowhale.app. It shows the exercise and any personal note and lets you try the rhythm in your browser. No Morrowhale account is needed. The preview code does not save breathing sessions in the app, create an exercise database or persist data in browser storage. It contains no advertising or analytics scripts.
The individual content of a breathing link is in the fragment after the # character. Your browser reads it locally. A normal HTTP request does not send that fragment, including its exercise data, sender name and personal note, to the web server. The requested path may reveal the selected cover color. Generic link preview images are not generated on the server from your individual exercise or personal note.
The separate preview hosting and delivery infrastructure still processes ordinary connection data such as IP address, time, requested path, response status and browser information. Necessary technical logs and infrastructure cookies from the hosting provider are possible; the URL fragment is not part of the normal HTTP request path. The Hostinger assignment described for morrowhale.app is not extended here to the separate Pause Post infrastructure. Technical delivery and protection serve the operational and security purposes described in section 2.
4. Data processed by the app
You do not need a separate Morrowhale account. Your profile name, profile photo, personal intentions and feelings after a breathing session are optional. You can use the other features without providing them.
Depending on your use, the app stores:
- Profile: an optional display name, profile photo and selected personal intentions.
- Created or accepted breathing exercises: name, subtitle, phase timings, rounds and cover; received Pause Post also includes origin information and received notes with technical identifiers and receipt times.
- Personal selections: favorite pauses and their order, your go-to rhythm and remembered duration.
- Breathing sessions: start time, active duration, completion status and a copy of the rhythm used at the time.
- Reflection: optional feelings and, where present, a saved rating.
- Technical information: record identifiers, modification and deletion times, and information for synchronization and deletion requests.
During the introduction or in your profile, you can optionally select what you would like from Morrowhale, such as more calm or little pauses in everyday life. Your selection is stored locally in your profile and helps suggest a suitable initial go-to rhythm. You can change it or leave it empty in your profile.
The displayed breathing time comes from the session sequence and your interaction with it. Morrowhale does not measure breathing movements or body data, use the camera or microphone, or access your location. The app contains no advertising or third-party analytics SDKs and does not send your breathing library to a Morrowhale application server. iCloud, Pause Post you explicitly share, TestFlight, external links you open and support messages you send are separate.
Sharing and receiving Pause Post
You can explicitly share your own rhythms as a link, rhythm file or designed picture card. Links and rhythm files contain the title, description, rhythm, rounds and cover, plus your optional sender name and current personal note. Sender names are freely chosen and not verified. Your profile photo, personal session history, feelings and previously received greetings are not included.
A picture card shows the visible content you create, particularly your personal note. A QR code is optional and initially off for every new Pause Post. If enabled, it contains the same complete breathing link, including your current optional details. Without a QR code, the card is an image; the rhythm also needs to be supplied as a link or rhythm file.
The messaging or file service you select receives the complete shared link, file or image and processes it under its own terms. Although a normal browser preview request does not send the URL fragment to its web server, your chosen messaging service can receive the complete link. Anyone receiving a copy can read and forward its content. Later edits or deletion in Morrowhale cannot recall shared copies.
Opening a rhythm file or link creates a local pending import containing the rhythm and any sender name or personal note. This lets the app wait for your decision after an interruption. The pending import is not yet part of your library and is not synchronized through the app's CloudKit integration. Only your explicit acceptance saves the rhythm, origin and personal note in your library. Accepting or discarding removes the pending import.
Accepted notes may be retained with the exercise, technical identifiers and receipt times, and privately synchronized through iCloud. Further greetings with the same exercise content and sender may be assigned to the same rhythm. When sharing again, sender and personal note fields start empty; received greetings, identifiers and receipt details are not automatically forwarded. Once accepted, received content is included in personal data export and the content and data deletion processes described below.
5. Local storage, drafts and session recovery
Your personal library is stored on your device. The app also stores device-specific appearance, haptic, breathing focus and hint settings, plus the most recently selected picture-card format and motif. iOS manages the selected app icon. Widget appearance is shared locally between app and widget through an App Group and is not synchronized through the app's CloudKit integration. Introduction progress also stays only on the device and contains neither your name nor your selected intentions. The short introductory breathing round uses temporary state and is not saved in your personal session history.
Unfinished editor input may remain as a draft containing names, rhythm, source copy, unfinished number input and a modification time. An interrupted session may leave a recovery checkpoint with rhythm, start, progress and state. Pending navigation helps open a requested app screen later. Undecided Pause Post imports are held locally with their document. Preparing and sharing Pause Post may create temporary local picture-card and file copies in the app's area; the app includes cleanup of these copies. This does not recall copies already handed to a selected service.
These drafts, settings and recovery data are not part of Morrowhale's CloudKit synchronization. Apple device backups and transfers may nevertheless include local app data. Which backups exist also depends on your system settings.
6. Your profile photo
You can provide one photo through Apple's system photo picker. This does not give the app unrestricted access to your photo library. Cropping and processing may create a temporary copy of the selected original in the app's area. The normal import flow removes it afterwards; interruptions or errors may leave temporary remnants.
Morrowhale creates a cropped, resized JPEG avatar. Re-encoding does not carry the original EXIF or GPS metadata into the saved avatar. This applies to the avatar; the selected original is first provided for processing. The original in your photo library is not changed.
A profile change is applied only when you choose Save. The saved photo is processed locally and, when synchronization is available, in your private iCloud. Confirmed removal clears image data in known personal photo records and resets avatar caches. Technical photo records can remain; older or subsequently synchronized versions and backups must be considered separately.
7. Automatic private iCloud synchronization
When iCloud is configured and available for the app, Morrowhale automatically synchronizes your personal library through a private CloudKit database. This includes profile name, photo and selected personal intentions, created and explicitly accepted exercises with saved origin information and received notes, favorites and their order, go-to rhythm, remembered duration, and sessions with historical rhythm copies and optional reflection details.
The app currently has no separate switch to enable or disable this synchronization. Availability depends on your Apple Account, system settings and technical setup. Core features can be used locally without available cloud synchronization. Changes may remain local during connection problems; later synchronization or restarting the app may be necessary. A positive connection status does not confirm that every record has reached every device.
This is not a public Morrowhale library for other users. Apple services are used for synchronization and also process technical account, connection, synchronization and error information. A Morrowhale server does not automatically receive the private library.
CloudKit uses services from Apple and participating Apple companies. Apple's published developer terms describe processing of personal CloudKit data in Attachment 4, section 3.6. This is separate from Apple's processing for its own Apple Account and platform purposes. See Apple's published developer terms.
Further information is available in Apple's privacy policy and iCloud terms.
8. Purposes and legal bases for app processing
The library, personal design, sessions, history, drafts and recovery provide the Morrowhale features you use. This includes your explicit choice to create and share Pause Post, preview it and accept received rhythms. Cloud synchronization lets you use your library on devices with the same Apple Account. Technical deletion markers handle delayed changes; deletion receipts support processing and checking your confirmed request.
Processing necessary to provide the ordinary app features you request is based on Article 6(1)(b) GDPR. Security measures and preventing unwanted restoration of removed content serve our legitimate interest in reliable personal storage under Article 6(1)(f) GDPR. Article 6(1)(c) GDPR applies to necessary handling of statutory data protection requests. Technically necessary device storage or access for expressly requested features additionally relies on section 25(2), no. 2 of Germany's TDDDG. This does not assume consent to unrelated additional purposes.
9. Changing or removing individual content
You can change profile details, replace or remove a photo, edit your own rhythms and manage sessions or reflection details. Drafts and session recovery checkpoints can be discarded separately.
In versions with the revised deletion features, removing your own rhythm clears its content from the related exercise copies known at that time. Favourite, duration and starting-rhythm selections are adjusted. Existing sessions retain the rhythm used at the time; independent editor drafts also remain. Removing the library exercise does not delete them.
Removing a session clears or resets its name, historical rhythm data, original time and duration information, rating and feelings in its known copies. The library exercise remains.
Technical identifiers and deletion and modification information remain for synchronization. These deletion markers currently have no automatic expiry. Older or later-arriving copies may still contain original content; the current version does not retrospectively clean all versions.
10. A separate deletion request in Your Data
If your app version includes “Einstellungen → Deine Daten” (Settings → Your Data), you can confirm a separate deletion request there. The comprehensive route first checks the private cloud inventory. If this is not possible, or considered cloud data is not yet present locally or uses an older format, it stops before local deletion and displays an explanation.
After successful preparation, the app removes the captured local inventory of profiles, photos, created exercises, favorites and sessions, including existing duplicates, historical rhythm copies and deletion markers. It also clears local editor drafts, the recovery checkpoint, pending navigation and Pause Post imports, local Pause Post cache files, temporary photo-import files, avatar caches and appearance, widget appearance, haptic, breathing focus, hint and picture-card settings. Built-in rhythms and the selected app icon remain.
The app initiates transfer of the deletion through existing automatic iCloud synchronization. Whether and when it completes depends on factors including availability and synchronization. Local completion and cloud verification are shown separately. While evidence is outstanding, the app shows “iCloud-Bestätigung ausstehend” (iCloud confirmation pending). “Erfasste iCloud-Daten entfernt” (captured iCloud data removed) means the previously captured records were absent on inspection and a fresh inventory of the considered personal record types in the same account was empty. Rechecking status does not initiate further deletion of new content.
If iCloud is unavailable, a separately confirmed local option is offered. It does not confirm complete iCloud deletion. When connection returns, local deletions may be transferred or remaining cloud content may reappear.
An interrupted confirmed request may resume at the next launch. Its original record scope is not automatically expanded to include newer records. An older receipt without a clear scope needs renewed confirmation. New writes may remain blocked while local cleanup is pending.
The app stores a request identifier, time and status locally, plus temporarily needed local and cloud target identifiers, counts and, where applicable, a technical cloud account identifier. Target identifiers no longer needed are removed after local completion or successful cloud verification. A minimal status receipt and local data revision remain, with no automatic expiry implemented. Open request identifiers support continuation and status checks. The reduced receipt shows the last request's result and is replaced by a newly confirmed request. The local data revision guards against outdated writes; it is not an ongoing log of your breathing activity.
Other devices may still have their own local content. Their drafts and recovery information are not remotely deleted. Existing exports, original photos and device backups are also not removed by the app's deletion request. Uninstalling the app does not confirm deletion of iCloud data. The app does not promise immediate physical overwriting of all storage or backup copies.
11. Export and retention of app content
If your app version includes “Deine Daten” (Your Data), you can create a JSON file of personal data captured on that device. This includes existing duplicates, removed entries, saved original payloads, profile photos, historical rhythms, origin information and received notes, pending Pause Post imports, drafts, recovery information, selected settings and technical deletion metadata. Where readable, content is also provided in structured form; image and original bytes are available as Base64 data.
Export does not perform a full cloud inventory check. Cloud data not yet downloaded to that device, original photos in your photo library, temporary photo-import files, RAM caches and device backups are not included. The file is not an automatically restorable app backup.
You choose the destination folder or file provider in Apple's file dialog. Morrowhale does not itself encrypt the export or keep its own permanent export copy. Further processing by your chosen file provider also follows that provider's terms. Later deletion in the app does not recall saved or forwarded files.
Your library, drafts and recovery checkpoint generally remain until you change, discard or remove them through the described features. A recovery checkpoint may also be cleared when the session ends or is resolved. Sections 9 and 10 explain deletion markers, old copies and deletion receipts. Independent backups and Apple service processes are not equivalent to the visible app inventory.
12. Email support and contact
If you write to us, we process your email address, any name you provide, the message and attachments you choose to send. An email started from the app may include its version and build in the subject; your personal library is not automatically attached.
The purpose is handling your request. Contract-related enquiries use Article 6(1)(b) GDPR. Other enquiries use Article 6(1)(f) GDPR, based on our interest in answering messages and resolving problems. Necessary handling of statutory data protection requests relies on Article 6(1)(c) GDPR.
Recipients are the operator and the Hostinger email service used for the support mailbox as described in section 2. Email transport also involves the email services chosen by senders and recipients.
For ordinary support, personal messages and attachments are needed while the enquiry is open, follow-up questions remain or a reported fault is still being checked. After final resolution, personal content is deleted or removed from any technical fault note still needed. Longer retention applies only where a specific message is subject to an applicable statutory retention duty or is needed for a specific legal claim. No uniform fixed deletion period is guaranteed here for the email service's technical logs or backups.
Contact: support@morrowhale.app.
13. TestFlight beta and feedback
For a TestFlight beta, Apple processes technical usage and crash information even without voluntary feedback and makes relevant information available to the development team. This may include app/build version, device and operating system details, installation and session information, and crash reports. Depending on the invitation method, a name and email address may be visible in the tester list. People joining solely through a public link appear there without those details. Emailing feedback may reveal your email address to the developer.
Voluntary feedback can include comments, screenshots and technical information, including personal content visible on your screen. The operator uses it to analyse faults and improve the beta. Ordinary technical information is used on the basis of Article 6(1)(f) GDPR for that legitimate interest. Please limit screenshots and comments to what is needed for the fault.
Apple describes its own processing and retention in its TestFlight privacy information. In the operator's own copies, personal information is retained only as needed to investigate the reported fault, fix it and verify the corrected build. It is then removed; a technical fault description still needed should be kept without personal references. Apple's own controls and retention processes are separate.
14. Recipients, transfers and external links
Recipients for each purpose are described in the sections on hosting, Pause Post, iCloud, email and TestFlight. The app does not automatically publish your library or operate a public user feed. When you share Pause Post, your selected messaging or file service and recipients receive the content you explicitly share. Exporting data or sending a support attachment also determines additional recipients. Technical hosting and delivery services support the separate browser preview, subject to the distinction in section 3 between connection data and the locally read fragment.
Processing exclusively in Germany or the European Economic Area is not guaranteed. Apple Inc. in the United States is involved; hosting and platform services may also operate internationally. Hostinger's published data processing terms provide for standard contractual clauses for relevant transfers to countries without a recognized adequate level of protection. Apple's public CloudKit provisions refer to an adequate level of protection or appropriate contractual clauses for EEA transfers. Apple's own privacy policy separately describes the standard contractual clauses it uses. You can request information about relevant safeguards and available copies through support@morrowhale.app; for Apple's own processing, see its privacy contact. Hostinger's published terms and subprocessors are available in its Data Processing Agreement.
Some breathing-technique information links to external sources. The relevant website is contacted only when you choose to open it. It may then process ordinary connection data; the provider's privacy notice applies. The same applies to links to Apple or other services on this page.
15. Your rights and how to contact us
Subject to the applicable conditions, you have rights of access, rectification, erasure, restriction of processing and data portability. Where processing is based on consent, you may withdraw it for the future without affecting the lawfulness of processing before withdrawal.
Right to object: where processing relies on legitimate interests, you may object on grounds relating to your particular situation.
Contact support@morrowhale.app or the postal address above. Start by telling us which process your request concerns. Please do not send your entire library or sensitive screenshots without being asked. Because personal app content is local or in your private cloud, a coordinated process using your devices may be necessary. The app's technical features do not replace handling an applicable rights request.
You may complain to a data protection supervisory authority, particularly where you live or work or where an alleged infringement occurred. For this operator in North Rhine-Westphalia, one contact is the North Rhine-Westphalia Commissioner for Data Protection and Freedom of Information.
The described service does not use automated decisions with legal or similarly significant effects. Optional profile and feeling information is not required for other app features. Without technical connection data the website cannot be delivered; without necessary local app storage the related features are unavailable.