Legal
Privacy Policy
Last updated: October 1, 2026
1. Who we are
ITChurch is operated by IGEARS TECHNOLOGY LIMITED ("we", "us", "our"). This policy explains what personal data we collect when you or your church uses ITChurch (the "Service"), how we use it, and the choices you have.
2. Data we collect
- Account data: name, email address, password (hashed), role, and organization you belong to.
- Church member data: names, contact details, group memberships, attendance records, baptism and join dates — entered by your church administrator.
- Usage data: IP address, browser type, pages visited, and timestamps, collected for security and analytics.
- SSO identifiers: if you sign in with Google, Facebook, or Apple, we receive your email address and basic profile information from that provider.
3. How we use your data
- Provide, operate, and maintain the Service for your church.
- Authenticate you and protect your account.
- Send transactional emails (password resets, security alerts, invoices).
- Measure and improve the product using aggregated analytics.
We do not sell your personal data or use church member information for advertising.
4. How we use AI
ITChurch offers optional AI-assisted features that your church or platform administrator can turn on or off. When enabled, these may include sermon preparation and study tools, pastoral-care and follow-up suggestions, member engagement and risk insights, donation and ministry analytics, volunteer matching, and multilingual translation of content.
What data is processed. CIS uses duckbot.hk technology to replace known personal and church details and detected identifiers in text requests with temporary placeholders before sending them to the configured AI API. The placeholder mapping stays locally in CIS for that request and is not sent to the provider. Recognized placeholders in the response are restored locally before the result is displayed to authorized users or saved in your church's draft history; the mapping is not retained with that history.
Limits of masking. The checks cover data known to CIS and patterns they recognize, and cannot guarantee detection of every sensitive detail in arbitrary prose. Review source text before submitting it. If supported checks detect sensitive content that cannot safely be masked, CIS blocks the external request and requires the input to be reviewed. Local tools remain available where supported.
Where it runs. The configured endpoint may be on infrastructure managed by your team or operated by an external AI provider. Masked text sent externally is processed under the provider's terms and account settings. The Duckbot privacy layer runs locally in CIS; the mapping is not sent to duckbot.hk or the AI endpoint. Administrators must review the endpoint and provider policies before enabling it.
Image analysis. Text masking cannot remove faces, documents, or text inside image pixels. CIS restricts vision requests and their image URLs to local CIS endpoints until image redaction is available. Text prompts for image generation and text sent for embeddings also pass through the local masking layer.
Provider policies and advertising. We do not sell church member information or use it for advertising. AI provider retention and model-training policies depend on the selected service terms and account configuration; local masking does not itself control these policies.
Human oversight. AI outputs are drafts. A model can be wrong, incomplete, or alter a placeholder. Staff must review restored names, facts, and meaning before acting or sharing. Your church remains responsible for decisions made with AI assistance.
Your choices. External AI processing requires administrator configuration and can be disabled by your administrator. See our AI Usage & Disclosure page for more details. For questions about AI processing, email privacy@itchurch.online.
5. Data sharing
We share data only with service providers strictly necessary to run the Service (hosting, email delivery, error monitoring, analytics) under confidentiality obligations. We may disclose data if required by law or to protect our rights.
6. Data retention
We keep your data while your church's account is active. You can request deletion at any time via our User Data Deletion page.
7. Security
We use industry-standard measures — encryption in transit (HTTPS), hashed passwords, role-based access control, and regular backups. No online service can be 100% secure, but we continually work to protect your information.
8. Your rights
Depending on your jurisdiction, you may have the right to access, correct, export, or delete your personal data. Contact us at privacy@itchurch.online to exercise these rights.
9. Children's privacy
ITChurch is not directed at children under 13. If a child's record is stored in the Service by a church, it is done under the responsibility of that church's administrator, and you should direct any request about such records to the church.
10. Changes to this policy
We may update this policy from time to time. We will post any changes on this page and update the "Last updated" date above.
11. Contact
If you have questions about this Privacy Policy, email privacy@itchurch.online.