iOS privacy
Updated October 19, 2026
This policy covers the Look Inwards iOS app, including the Look Inwards workspace and the previous native iOS diary available from Account. The website policy provides further detail about the shared Look Inwards workspace.
Your workspace and sign-in
You can use the workspace without signing in. Its device-only content is stored within the app's web storage. Optional Apple or Google sign-in opens your existing Look Inwards website account. Firebase Authentication processes your account identifier, email address and available basic profile information. Native sign-in passes a short-lived provider credential into the Look Inwards workspace to establish that session. Apple sign-in supports Hide My Email. Sign-in does not grant access to Google Drive, contacts or email messages.
Signed-in content is stored with Cloudflare D1 and cached on your device. Content can include your questions, ratings, optional wellbeing answers, timestamps, diary entries, lists and their edit history, personal icons, and preferences. These records are associated with your account so they can synchronize. Meanings are chosen by you; the app does not diagnose you or provide clinical scores.
Optional pictures
You may choose a picture for a personal icon. Cropping and optional face-region detection run on your device. Original photos and face-detection results are not uploaded. Only the small image crops you choose to save are included in your content and synchronize when signed in. Face-region detection does not identify people or create face-recognition profiles.
The previous iOS diary
The previous native diary retains its original, separate device storage and cloud account system. Its Google and Apple sign-in are provided by Firebase Authentication. Its cloud entries, favorites and plans are stored by the original Cloudflare diary service. These entries are not automatically merged with the Look Inwards website. Guest and signed-in native diaries remain separate.
Device storage, exports and service providers
Device-only and cached content can remain until you remove it, clear app data or uninstall the app. An offline device can retain an older copy until it reconnects. Exports are created locally and shared only with the destination you choose through the iOS share sheet. The app may keep a temporary export file in its cache so the chosen destination can finish reading it.
Google/Firebase and Apple provide authentication services. Cloudflare provides hosting, cloud storage, security and website performance services. These providers process connection and operational information, such as IP addresses, browser or device information, request timings and security logs, to deliver their services. Their own privacy policies also apply. The app has no ads, does not sell journal content, and does not use journal content for advertising or AI interpretation.
Deletion and control
In Look Inwards, Account → Delete account and data removes the active workspace records and its cache after confirmation and fresh authentication. A minimal deletion marker prevents an older device from silently restoring deleted data. The shared Firebase sign-in identity may remain because it can be used by other websites; this does not delete your Apple or Google account or unrelated data.
To delete the original native cloud diary and its dedicated Firebase identity, open Account → Previous iOS diary, then its account controls → Manage account → Delete account. This requires confirmation and fresh authentication. Signing in through Apple can require revoking the app's Apple authorization as part of deletion.
Removing an item may preserve reversible history. Use the appropriate account deletion control to remove the active account's content. Provider backups and operational or security logs may remain until their normal retention expires. Deleting one diary area does not automatically delete the separate account or records in the other area.
Contact
For privacy, access, correction or deletion requests, email selagame59@gmail.com. Send requests from the relevant account's email when possible; ownership may need to be verified. Do not include private journal entries in your initial message.