Privacy & your account.
A practical explanation of how this LIFE release handles your information.
When you join
We store your email, name or nickname, age at registration, LIFE edition, and a record that you have read this information. Passwords are stored as hashes by WordPress. Your age selects Junior (13–16), Youth (17–24), or Advanced (25+).
Your learning
Your account stores program enrollments, completed activities and days, quiz attempts, achievements, and bookings. Authorized LIFE team members can see learning progress and manage services.
Your journal and what you share
Journal entries are private to your account in the app and are not displayed in portal progress reports. Authorized website administrators can technically access stored data. Stories, community posts and prayer requests you submit for the community are reviewed before publication. Do not post private contact details or information you do not want shared.
Young members
LIFE registration is for people aged 13 and over. If you are under 18, ask a parent or guardian for permission before joining. The permission checkbox records your declaration; it is not an independent verification of your guardian’s identity. Never share your password, location or private contact details with other members.
Cookies and infrastructure
Essential cookies keep you signed in and protect forms. The website uses essential session cookies. Optional Google Analytics on public information pages is off until visitors confirm they are 25 or older and choose Allow analytics. Use Privacy choices in the footer to change your decision. This records general page views and program/start-journey clicks, approximate location, browser/device information and a browser-instance identifier. Form fields, account identifiers, detailed program identifiers and private content are not sent. Advertising personalization and Google signals are disabled. Account forms, staff pages and member app screens do not load this website tag. Consent choices expire after 180 days. The Android and iOS apps include Google Firebase Analytics, disabled by default. Eligible Advanced-edition members (25+) can opt in through Settings → Usage Analytics and can turn it off there. When enabled, Google processes basic app events (app ready, sign-in and account creation), app-instance/device information and usage data. LIFE does not send journal text, prayers, feelings, assessment answers or your account identifier to analytics. Advertising identifiers and personalised advertising are disabled. The Meta SDK is included but automatic collection and app events are disabled; this release sends no Meta advertising events. Hosting and Cloudflare process network requests to deliver and protect the site. Linked media may open on another provider’s website, under that provider’s privacy practices.
When you contact LIFE
The contact form stores your name, email, topic, message and permission to reply. Authorized LIFE managers can read these messages and save replies. If email delivery is connected, replies are sent through the configured Zoho mailbox. Your message is not published on the website.
Keeping and managing your information
Delete your account from My LIFE → Settings → Delete Account or use the LIFE account deletion page without the app. Confirmation requires your current password. Deletion removes your account and associated app content from the active database. Contact-form conversations and emails are handled separately; contact us to request their removal. Backups may retain earlier copies until they are replaced, and infrastructure security logs have a separate retention cycle. Safety reports and block preferences are stored to support moderation and are accessible only to authorized staff and the relevant account. For access, correction, export or help with deletion, contact [email protected]. Email ownership is not verified automatically in this release. Do not use LIFE to share urgent or highly sensitive personal information.
Last updated 7 November 2026. This page describes the current implementation and should be reviewed as the service develops.