Fernhour Privacy Policy
Last updated: 16 September 2026
This privacy policy explains how Fernhour handles your information when you use Fernhour: Cozy Focus Timer for Android (com.fernhour.app), the Fernhour iOS app, the browser game and the fernhour.com website. It describes the information we use, the services that process it, and how you can control or delete it. Optional features only access information when you choose to use them.
For privacy questions or data requests, contact hello@fernhour.com.
The new native mobile edition is being prepared for iOS and Android store review. It is not yet the edition available on Google Play. This policy describes its account, cloud-save, health and reminder features separately from the earlier apps and browser game. The new edition starts a new world and does not import earlier-edition progress.
Optional mobile waitlist
If you join the mobile waitlist, we store your email address, any iOS or Android interest you choose, and the date and wording version of your consent to mobile-launch and product-update emails in our London-hosted Supabase database. These records are separate from game accounts, saved worlds and health data. We use a short-lived, daily-changing keyed hash of your connection address to limit repeated submissions; the waitlist does not store the raw address. To leave the list or request removal, email hello@fernhour.com. Joining does not create an account or grant mobile access.
Progress on your device
You can play without an account. In the new native edition, your timer, intentions, tasks, furniture, companion, manual care check-ins and imported workout summaries are saved locally on this device. Guest progress is not uploaded to the cloud. The app can reopen the last saved world you explicitly chose for offline play, including an account world. If that world cannot safely be opened, the app keeps its files and offers recovery from the separate guest world. Fernhour does not include advertising.
Optional accounts and cloud saves
When you choose Google or Apple sign-in, Supabase processes your account identifier, email address, authentication information and any basic profile information supplied by that provider so you can save a world to your account. This can include your provider-supplied name and, for Google sign-in, a reference to your profile image (its URL). Supabase retains these details as account metadata. The new native game uses your account identifier and email; it does not upload photos from your device. Our Supabase project is hosted in London. Your account can access its own saved world. In the new native edition, credentials are held in your device’s secure storage, outside game snapshots and logs.
New native cloud saves include furniture and its placement, acorns, saved focus history and intentions, tasks, manual care check-ins, companion selection and your furniture wish. Active and paused timers, imported steps and workout summaries, sign-in credentials, notification settings and device preferences are excluded. Manual care check-ins record water, stretching, breathing or fresh air that you confirm yourself, together with the local calendar date. Those dated check-ins are sent to Supabase when you sync your account world. They are separate from imported Apple Health and Health Connect records, which stay on your device. Signing in does not automatically replace your guest world. When device and cloud progress differ, you choose which complete world to keep; rewards are not combined.
In the new native edition, signing out disconnects cloud access and clears the native sign-in session. It keeps your currently open world available locally. Other local worlds, including your separate guest world, remain saved. Signing out does not delete your account or its data.
In the earlier apps and browser game, cloud saves can also include rooms, achievements and other content from that edition. Imported health records, active timers and device preferences are excluded there too. Those earlier versions return to the separate guest world on sign-out.
For Sign in with Apple, Fernhour stores an encrypted sign-in grant on its server, linked to your account, so it can disconnect Apple access when you delete your Fernhour account. This credential is not included in your saved world or sent to the app. The grant record is removed with your account after revocation. Google access can be disconnected through Google’s account controls.
Optional health access
In the new native edition and earlier mobile builds with health access, you may choose to let the app read steps and completed workouts from Apple Health or Android Health Connect. Activity from a watch must first sync to your phone’s health store through a compatible app. Fernhour does not record workouts, include a standalone watch app or write to your health store. Only information you allow is readable. You can revoke access in your device’s health settings. Empty results do not necessarily mean permission was denied.
In the new native edition, permission and import are separate choices. Importing reads the last seven days of available activity when you ask; there is no background health import. Imported activity stays on this device, is excluded from cloud saves and does not earn acorns. Saved workout summaries belong to the current local world and can be removed with Movement → Remove saved activity. This does not delete the original records from your health store. Steps are shown as a recent reading rather than added to your cloud world.
Earlier builds with saved-world exports include imported workout summaries in those files; keep such exports private. The new native edition has no save-file export or import screen. Fernhour provides general wellbeing routines, not medical assessment or treatment.
Optional purchases
Purchases are available only in the earlier web game. The new native edition has no billing integration, paid items or subscriptions. Its earned acorns cannot be purchased. Earlier iOS and Android releases also do not request or activate paid-item ownership. The earlier web cloud world can remember furniture layouts; it does not contain a purchase license. The payment information below applies to web purchases.
Dodo Payments handles hosted checkout, payment processing, receipts, taxes and payment disputes. It collects the billing, contact and payment information you enter there, along with information needed to process the transaction and prevent fraud. Read Dodo Payments’ privacy policy for its handling of that information.
Fernhour links your account to order and payment references, purchase status, and refund or dispute status so it can deliver and restore purchased decorations. These records are held in Supabase, separately from your saved world. Our checkout request contains a purchase reference, not your tasks, intentions, health records or saved-world content. Fernhour does not store your card details or the complete billing information sent with payment confirmations.
Clearing device storage does not remove a purchase. Deleting your Fernhour account removes its linked purchase access and account records; limited payment-event references remain to prevent duplicate processing. Dodo manages its own transaction records separately. Account deletion does not issue a refund.
Control your data
Sign out before uninstalling: secure sign-in credentials may remain in the iOS Keychain after the app is removed. Clear the app’s storage or uninstall the mobile app to remove its ordinary local data, subject to your device’s backup settings. Browser progress can be removed by clearing this site’s storage. Removing local app data does not remove workouts from your health store. The earlier browser game and mobile builds with export controls let you export your world in Settings; the new native edition does not have these controls.
Clearing local storage does not delete an account or its cloud save. In the new native edition, open World → Settings & account → Account and cloud saves → Delete my account. Deletion requires a recent sign-in and typed confirmation. Once the server confirms deletion, the app removes the matching local account world and its imported workout summaries. Your separate guest world and other accounts’ local worlds remain. If deletion or local cleanup is interrupted, return to the account screen to check its status and finish cleanup.
You can also use our account deletion page for account deletion and help. Removing an account on the website does not erase local copies on other devices; remove that app’s local data separately. A short-lived encrypted receipt lets you check an interrupted deletion; it expires after 24 hours. If you cannot sign in, contact hello@fernhour.com for help.
Hosting and reminders
The website host and account services may process ordinary request information needed to deliver their features. New native timer reminders default off. Enabling them and requesting notification permission are explicit choices. Your device stores the reminder preference and a timer ticket. The system notification is a generic timer-completion message; it contains no intention, task, account identity or health record. No push-notification registration or notification server is used. Device settings apply and delivery can be delayed. Notifications and health access are not required to use the focus timer.
Website analytics
The website, including the browser game, uses Vercel Web Analytics to understand page visits, traffic sources, approximate region and device or browser type in aggregate. It does not use tracking cookies. We remove query strings and fragments from the page URLs sent to analytics. Your tasks, intentions, saved world, check-ins and health records are not included in analytics events. The new native edition contains no analytics or crash-reporting SDK. The mobile apps do not include this website analytics integration.
Learn more about Vercel Web Analytics privacy.
Finding and fixing website errors
We use Sentry to receive technical error reports from the website, including error details, code locations and browser or device context. Session recording, performance tracing and interaction breadcrumbs are disabled. We remove user details, extra application data and URL query strings from reports. We do not attach your tasks, intentions, saved world or health records. These reports help us investigate failures.
When you contact us
Messages sent to hello@fernhour.com are processed by Resend and forwarded to our support inbox. We use your email address, message and any attachments to respond to your request. Please do not include sensitive health information. You can use this address to ask about your privacy or request removal of support correspondence.