Lorea / Privacy & Support
Privacy Policy
Lorea Privacy Policy · Effective and updated September 25, 2026. Lorea is operated by Kewen Wang. This policy explains information handling in the current app and privacy/support website. Contact: wangkewen20011@outlook.com.
Optional Lorea AI
AI requests require sign-in and consent. Your question, recent conversation, archive identifier, relevant published content and approximate map viewing area are sent through Supabase to OpenAI. Precise device location is not automatically sent. Avoid sensitive information. Lorea does not store chat text in its database; conversations are held in this app session's memory, can be selected or deleted in the conversation menu, and are not persisted after closing the app. We request no Responses application-state storage, but provider security and abuse-monitoring retention may still apply. Supabase stores daily request counts linked to your account identifier for rate limits. Counts older than seven days are cleared when requests are processed; deleting your account also removes its counters. You may skip AI or withdraw consent on the AI screen without affecting archive browsing. Generated conversation titles, manual renaming and deletion also apply only to the current app session. Deleting a local conversation does not retroactively erase provider security logs.
Accounts and sign-in
Lorea uses Supabase to create accounts and sign in with email verification codes. The account service processes your email, account ID and chosen display name. Your profile and session are stored on this device to keep you signed in. The current sign-in flow does not ask you to set an app password.
Local records and favourites
Favourites are stored on this device, do not currently sync between devices and are not separated by account. Language preferences, onboarding state and a local story index are also stored on the device. Signing out does not automatically clear favourites. Appearance preferences, reading progress and downloaded public archive caches may also be stored locally for reopening content and offline browsing.
Server archives and images
Published Cases, UMA and Lorea Cases are delivered through Supabase database and Storage services. Requests may involve IP addresses, request times and error or security logs for delivery, troubleshooting and service protection. Memory of Places groups archive locations, not your movement history. Current favourites are not uploaded as cloud favourites.
Location and third-party maps
With permission, Lorea uses precise foreground location for your position, nearby places and routing. On iPhone, the current position, archive destination and travel mode are sent to Apple MapKit. After Start navigation, foreground updates support remaining routes, estimated time and visual turn guidance; deviation can trigger recalculation. Heading, speed and accuracy support on-device camera following and route matching. Lorea does not upload your journey as account history or request background location. Location listening pauses when the relevant screen loses focus or the app enters the background. There is no voice guidance. Time and arrival detection are estimates, not guarantees of current road conditions. Map and geocoding providers may receive location and network information such as IP addresses. Choosing external navigation passes the destination and travel mode to the selected provider under its own privacy rules. You can browse archives without granting location access.
Astrum motion controls
Astrum maps existing archives to stars. Motion permission is requested only when you enable motion controls. Rotation and tilt data are used on this device to change the view; they are not saved to archives or uploaded to the Lorea account service. Listening stops when the screen loses focus or the app enters the background. You can disable motion and drag to explore.
Sharing archives
The detail-page share button opens the system share sheet with the archive title, a short description and a Lorea app link. Content is sent through your chosen service only when you complete sharing. That service processes the content under its own rules. Opening the app link requires Lorea to be installed.
Notifications
This version does not provide book-release push notifications or upload device push tokens. Ask About This Book only opens your email app; you decide whether to send. If an earlier version requested notification permission, you can turn it off in system settings.
Email submissions and public content
The submission button opens your email app. Your sender address, message and attachments reach the submission mailbox only when you send the email. Include only information you intend to share. Submissions undergo manual review and are not automatically public; selected material may be edited and published under an agreed name. Your email provider and the recipient mailbox provider process the email. Emails and edited publications are not automatically deleted with an app account. Contact the email below to request their removal or correction. Applications to join SSSP also use email. Interests, experience and contact details you choose to provide are used to respond and communicate about the organisation; tapping the button does not submit an application automatically.
Account deletion and retention
Choose Delete account below Sign out in Profile and confirm to request permanent deletion of your account and account profile from the server. After confirmation of success, the app clears this device’s favourites, local story records for the account and sign-in session. Failures or interrupted requests are reported as unconfirmed, not as completed deletion. Local records on other devices are not remotely erased. Language and onboarding preferences remain. Provider backups and security logs may not be removed immediately with the active account and follow provider retention rules; this does not keep the deleted account available for use.
Third parties and your choices
The current app code does not integrate advertising tracking or behavioural analytics SDKs. Account verification, email, maps and archive image requests still involve the providers described above. Revoke location, motion and notification permissions in system settings. Contact the email below to request access, correction or deletion of personal information.
Retention and security
Account information is used to provide the service while your account remains active; see deletion instructions above. Emails are retained to handle applications, support, submissions and necessary follow-up; you can request deletion. Providers may retain limited records for security, backups or legal obligations. Data is transmitted over encrypted connections; no system can guarantee absolute security. Providers may process data outside your country or region. We do not sell personal information or use it for cross-app advertising tracking.
This website
This website provides privacy and support information without requiring registration. We have not added advertising, analytics scripts or forms. Hosting services (Cloudflare Pages and its infrastructure) may process IP addresses, browser information and request logs to deliver and protect the website. Your email app handles sending after you select an email link.
Requests and policy changes
Contact wangkewen20011@outlook.com to request access, correction or deletion, or ask about information handling. We may verify your identity to protect your account. Requests are handled under applicable law; do not send passwords or verification codes. This policy will be updated as features change, with the revision date shown above.
Continue reading and widgets
The continue-reading bar temporarily holds the archive identifier, scroll position and, for Lorea Cases, chapter and unlocked progress in this app session’s memory. Dismissing it removes the shortcut without deleting favourites. Widgets retrieve public archives and cover images and read appearance preferences through on-device shared settings. They do not read AI conversations or device location. Public content and image requests may still involve normal server or hosting network logs.
AI, research and content statement
AI can generate archive explanations, search suggestions, conversation titles and SSSP model explanations, and may make mistakes or omit sources. Check original archive sources; an AI answer is not independent verification. SSSP models and results support exploration and research explanation, not validated predictions or professional advice. UMA folklore and sightings are not proof that a creature exists. Lorea Cases marked as original are fiction. Illustrations, reconstructions and generated images should not be treated as primary evidence.
Visiting places and navigation statement
Archive coordinates may be approximate and routes may lead to a nearby public area rather than the exact event location. Routes, time estimates, turns and arrival indications are aids only; follow road signs, access restrictions and actual conditions. Set up your route before departure and do not operate the app while driving. Do not enter private, closed or unsafe locations.
Content Safety
Cases, UMA and Lorea Cases include historical cases, unresolved accounts, legends or creative writing. Read each archive’s classification and sources. Personal accounts are not automatically independently verified facts. Stay aware of your surroundings while using Navigate or Astrum, and do not keep watching the screen while driving or walking. Also read the navigation and visiting statement above.