We give private daily records a local home and an optional app lock. Foleil's food, training and personal notes do not become public because you keep them together. When you enable the lock, returning to the app requires the supported device-owner authentication before its private interface is uncovered.

The advantage is an extra practical boundary around a phone you use throughout the day. It is not a claim that no information ever leaves the device: optional AI, Apple Health exchange, exports and chosen backups have their own data paths and controls.

How it works

Enable App Lock through device-owner authentication, using the supported Face ID, Touch ID or device-passcode route. The app covers its private interface while inactive or awaiting authentication, and a cancelled attempt does not count as a successful unlock. Local records, external assistance, exports and backup choices remain separate controls rather than one blanket privacy switch.

Why it matters

Apple's guide to locking or hiding iPhone apps, accessed 19 October 2026, documents device authentication as a boundary for access to apps. It is useful platform context for a separate in-app lock, not a claim that either protection defeats every threat.

The person holding the phone and the information visible on its screen are practical privacy concerns. Foleil's lock addresses interface access. It does not revoke a file you already exported, change an online provider's retention terms or hide information you separately chose to show in a widget or notification. Good control means keeping those scopes clear.

Compared with other health and fitness tools

Athlytic's official overview, accessed 19 October 2026, describes on-device health-data processing. We do not claim local processing is unique or infer that another product lacks an app lock. Foleil's reason to choose this combination is the local daily record plus an explicit authentication cover around our connected training, food and reflection interface. A privacy preference should rest on actual settings and disclosures, rather than an unsupported assertion that one competitor sends everything away or that Foleil sends nothing.

The evidence and a practical example

Imagine checking a journal entry, then leaving the app while the phone is still in use. With App Lock enabled, a return is covered until the device-owner authentication succeeds. A failed or cancelled attempt leaves the cover in place, instead of briefly revealing the private page as though the attempt had worked.

The evidence is the enabled preference, the covered interface and the result of the authentication attempt. Enabling the lock also requires authentication, rather than treating an unauthorised toggle as proof of ownership. Review notification previews and widgets separately if their content is sensitive. This example concerns an ordinary privacy boundary and does not claim a security audit result, immunity to a compromised device or medical confidentiality under every jurisdiction.

Frequently asked questions

Is App Lock the same as encrypting every export?

No. It protects access to the app interface. Exported files and the destinations you choose have separate protections and responsibilities.

Does cancelling authentication reveal the page?

No. A cancelled or failed attempt does not count as a successful unlock. The private interface remains covered.

Does local storage mean AI questions never leave?

No. An enabled online route can process your submitted words, images and applicable context externally. Review its actual consent and data-use disclosure.

Sources

  • https://athlyticapp.com/. Official or peer-reviewed source; accessed 19 October 2026. Publication dates, where relevant, are distinguished in the text.