YOUR STORY, KEPT YOURS

Privacy Policy

Lorecasts is operated by Ubermobi.com. Effective date: 3 October 2026. Last updated: 3 October 2026.

1. Who we are and how to contact us

Lorecasts is operated by Ubermobi.com. Privacy questions, access or correction requests, and complaints: [email protected].

2. Information we may handle

3. How information is used

We use information to provide sign-in, analyse only the memories you choose, generate personalised Lorecasts and plans, save and restore your account data, manage subscription access, answer support requests, and protect and improve the service.

4. AI analysis and service providers

If you ask Lorecasts to analyse memories, selected compressed images and analysis instructions are sent to OpenAI through a Lorecasts server function. The request also includes a hashed identifier derived from your account ID. Lorecasts instructs the AI not to identify people or infer sensitive traits, but you should review results and avoid selecting material you do not want analysed.

For API use, OpenAI states that customer data is not used to train or improve its models by default unless the customer opts in. OpenAI may retain API abuse-monitoring logs, which can include prompts and responses and, in some circumstances, image or file inputs, for up to 30 days by default, or longer where required by law. Lorecasts requests that Responses API output not be stored as application state (`store: false`); this setting does not by itself disable abuse-monitoring logs. We do not promise zero data retention. See OpenAI’s API data controls.

Supabase provides sign-in, the account database and server functions. Supabase stores primary project data in the region configured for our project; its platform services, backups and support processes may involve additional locations under its terms. We do not represent that all data is stored or processed only in Australia. See Supabase’s region information. RevenueCat receives the app’s account identifier and purchase/entitlement information to check subscription access. Apple processes App Store billing. Mailgun may deliver sign-in emails through Supabase’s configured email service. These providers process information to provide their services.

5. Where information is stored

On your device: the app stores the app session, Lorecasts profile and paths, journey progress, daily reflections, completed chapters, Life Balance entries, display name, and sign-in session tokens using app storage. The anonymous app identifier is stored using the platform secure-storage API. Device backup behaviour is controlled by your device and operating-system settings.

In your Lorecasts account: after sign-in and account linking, the app stores your Lore profile, selected Lorecasts paths, chapter plan, and Lore Scan status/summary in the Supabase database. Daily reflections and journey progress are not currently synced between devices. The Lore Scan function sends selected images to OpenAI for analysis and does not write those image files into the Lorecasts database. Supabase’s project region determines where its primary project data is stored; provider backups and operational services are subject to Supabase’s own configuration and terms. Information may therefore be handled outside Australia.

6. Sharing

We do not sell personal information or use it for targeted advertising. We share only what is needed with service providers: selected images, instructions and a hashed account identifier with OpenAI for requested analysis; account and profile data with Supabase for sign-in and cloud storage; an account identifier and purchase/entitlement details with RevenueCat; transaction data with Apple for App Store billing; and your email address with Supabase and its configured email-delivery provider, which may include Mailgun, to send sign-in links. We may also disclose information if required or authorised by law.

The reviewed app source contains no advertising integration or dedicated third-party analytics SDK. Provider, operating-system and security diagnostics may still be generated; their contents and retention are being checked.

7. Retention and deletion

You can request deletion of your Lorecasts account using the in-app account controls. The deletion flow asks Supabase to delete the signed-in account and its linked database rows, then clears Lorecasts app data from the device. Selected image files are not stored in the Lorecasts database by the current scan function.

Account deletion does not cancel an Apple subscription; cancel it separately in your Apple Account settings. Deletion from Lorecasts does not immediately remove records that Apple, RevenueCat, Supabase, Mailgun, OpenAI or other providers may retain under their own backup, security, operational or legal retention rules. Provider retention periods vary by service and configuration. Information may also remain in device backups under your device settings.

8. Access, correction and complaints

Email [email protected] to request access to or correction of personal information, or to raise a privacy complaint. We may ask you to verify your identity before responding. Australian users may also contact the Office of the Australian Information Commissioner if they are not satisfied with our response.

9. Children and sensitive information

Lorecasts accounts are for adults aged 18 and over. You must be at least 18 to create or use a Lorecasts account. We do not knowingly permit anyone under 18 to hold an account. If we learn that an account is held by someone under 18, we will take steps to close the account and delete its associated personal information, subject to information we must retain by law or for legitimate security and service records.

Adults may choose to analyse memories that include other people, including children. Only select or submit images you have the right and permission to use. Selected images are sent to our AI service provider for the analysis you request; do not submit sensitive information unless the app clearly asks for it and you choose to provide it. Lorecasts is designed to describe visible patterns, not identify people or infer sensitive personal attributes.

10. Changes to this policy

We will update this policy when our practices change and show the updated date here. Last updated: 3 October 2026.