Layered privacy notice
01Information we may collect
| Category | Examples | Why it is needed |
|---|---|---|
| Account data | Name/display name, email, password hash, learner ID, verification and role status. | Create, secure, verify, and administer accounts. |
| Optional profile data | Phone, country, favorite verse, church/ministry/group, translation, language, age or guardian confirmations. | Personalization, safety, support, and account administration. |
| Gameplay and learning data | Progress, answers, scores, streaks, XP, Coins, Seeds, achievements, reading activity, mini-game state, rewards, and rankings. | Run the games, save progress, award milestones, balance features, and prevent abuse. |
| Community data | Posts, comments, reactions, reports, friend actions, prayer encouragement, versus invitations, and news interactions. | Provide community features, moderation, safety, and requested communication. |
| Technical and security data | Session identifiers, IP address, browser/device information, logs, errors, timestamps, rate-limit events, and security signals. | Keep the service functioning, diagnose bugs, prevent fraud, and protect accounts. |
| Requests and support data | Feedback, issue reports, volunteer forms, Seed Shop requests, admin notes, delivery details when actually required. | Respond to requests, review eligibility, and provide support. |
Do not place sensitive medical, financial, identity-document, precise-location, or confidential pastoral information in free-text fields.
02How and why information is used
- Provide accounts, gameplay, Bible-reading features, progress, rewards, friends, forums, news, and support.
- Verify identity and email, maintain sessions, recover access, enforce safety limits, and prevent unauthorized activity.
- Moderate community content, investigate reports, protect children, and enforce the Terms.
- Measure internal feature use, unique content views, errors, and performance so the service can be improved.
- Send service messages such as verification, security, moderation, invitations, or important update notices.
- Comply with lawful obligations and protect the rights and safety of players, the project, and others.
Depending on applicable law, processing may rely on providing the requested service, legitimate operational and safety interests, consent where required, or legal obligations. The service aims to follow transparency, purpose limitation, proportionality, and data-minimization principles.
03What other players can see
Public identity areas may display your chosen display name, learner ID, badge, title, border, rankings, scores, posts, comments, reactions, and other activity you intentionally share.
Email, password, phone number, country, age confirmations, moderation notes, and private account fields are not intended to be public. Never place private information inside public posts, profile text, prayer messages, or comments.
06Retention, security, and international processing
Information is kept only as long as reasonably necessary for the purposes described, account administration, safety, dispute handling, backups, security, or legal obligations. Retention may differ by record type.
Reasonable technical and organizational safeguards are used, including password hashing, access controls, role restrictions, rate limits, validation, backups, and moderation tools. No online system can promise absolute security.
Hosting, email, or technical providers may process information in another country. Where applicable, reasonable safeguards and mandatory local rights continue to apply.
07Your choices and privacy rights
Depending on your location, you may have rights to know, access, correct, delete, object to or restrict certain processing, receive a copy, withdraw consent, or complain to a data-protection authority.
- Update available profile fields through Profile settings.
- Use account deletion controls when you wish to close the account.
- Ask the project team to review inaccessible, incorrect, or disputed data.
- Parents or guardians may request review or deletion of a child’s information where applicable.
Some records may be retained when necessary for security, legal obligations, fraud prevention, or protecting other users.
08Children’s privacy
Children under 13 must not independently create an account or provide personal information. Where law requires verifiable parental consent, interactive account use must wait until that consent is properly handled.
Players aged 13–17 should use the service with parent or guardian awareness and supervision. The project seeks child-appropriate defaults, limited collection, private account details, clear explanations, and accessible reporting, but parents remain essential partners in safe use.
09Changes and contact
This notice may be updated as features, service providers, safeguards, or laws change. Important changes may be announced through News & Updates or login notices.
Privacy request or concern
Use Feedback or Support after signing in. Clearly state whether you are requesting access, correction, deletion, or a review of a child’s information.