Apologia Sancta Privacy Policy
Effective 24 August 2026
Information used by the service
When you create or use an account, Apologia Sancta processes account information such as your email address, display name, optional phone number, account role, account timestamps, and authentication/security state. The learning service can also store lesson progress, bookmarks, assessment attempts and answers, unlocks, review schedules, derived mastery records, and research journeys you deliberately save to your learner profile.
Saved research journeys and sharing
A saved research journey contains canonical Knowledge Engine identifiers, a title, lens, visibility choice, navigation metadata, and timestamps. It does not copy the underlying theological claims or source texts into the journey record. Private journeys are account-only. If you choose an unlisted share link, anyone who obtains that opaque link can view the saved sequence of canonical identifiers until the journey is deleted or made private.
Device data
Some interface preferences, saved learning state, bookmarks, and live-quiz convenience data can be stored locally on your device or browser. Clearing app/browser storage removes that local copy but does not by itself delete an authenticated account or research journeys deliberately saved to the account.
How the information is used
Account and learning information is used to authenticate users, operate account security, preserve learning progress, score governed assessments, derive evidence-based concept mastery, unlock learning content, support saved resources and research journeys, and operate quiz and competition features.
Account deletion
Learner accounts can be permanently deleted from the app or from the web account-deletion page. Deletion removes the authenticated learner account and account-linked learning records, including learner-owned saved research journeys through the learner-profile deletion cascade. Historical live-quiz participation may be retained only in anonymised form so aggregate competition results remain consistent; the learner account link, display name, participant key, and participant metadata are removed from those retained records.
Delete an accountSecurity
The production Android app requires HTTPS for its configured web service, uses authenticated sessions and CSRF protection for account mutations, and does not request Android permissions beyond network access in its application manifest. Learner-owned journey rows are additionally protected by database row-level security; anonymous clients have no direct table access.
Policy changes
This policy may be updated when the app, its data handling, or store requirements change. The effective date above identifies the version currently published with the application.