The church
In general, the church is the controller of member records, contributions, prayer requests, care conversations and other pastoral records because it decides the purposes and how this data will be used.
Data protection in practice
Data protection for churches: clear responsibilities and real care
Technology helps protect and organize information, but compliance does not come from a button. Every church needs to know why it collects each piece of data, who may access it, how long it will be kept and how it will serve its members' requests.
Religious data is sensitive
The church defines pastoral purposes
AI is optional and requires transparency
People keep their rights
Who does what
Controller, processor and vendors
Roles should be evaluated per processing activity, not just by the name on the contract.
Sanctuware
Sanctuware typically acts as a processor when handling pastoral data under the church's instructions. It may act as controller for data needed for the account itself, billing, security, fraud prevention and support.
Other vendors
Hosting, payments, email, Meta/WhatsApp and the enabled AI provider may take part in processing. Contracts, purpose, location and safeguards must be considered in each flow.
Important: this page explains how the product was designed and does not replace legal analysis of each church's own situation.
What requires more care
Religious data is sensitive personal data
Data protection laws such as Brazil's LGPD treat religious belief as sensitive personal data. Health information, counseling and family situations can raise the risk even further. Where the GDPR or US state privacy laws apply, similar care is expected.
Identification and contact
Name, phone, email, address, birthday, family and location.
WhatsApp communications
Specific consent, number, individual messages, delivery states and opt-outs. The church must respect the stated purpose and requests to stop.
Community life
Memberships, attendance, events, ministries, history and follow-up.
Pastoral data
Prayer requests, notes, conversations, personal needs and information that may relate to health.
Financial data
Offerings, tithes, expenses and records needed for accountability.
Security and audit
Access events, user role, administrative actions, IP address and technical data when necessary.
Artificial intelligence
In the Online Pastor, the message and recent session history support the answer. Behavior reports use aggregate counts only.
Before registering anyone
Purpose, necessity and legal basis
For each category of data, the church should document a specific purpose, collect only what is necessary and identify an appropriate legal basis. Consent is not a blanket authorization and is not the only basis available under data protection laws.
Sensitive data follows stricter rules. The correct basis depends on the concrete context; that is why the system does not automatically choose the church's legal justification.
- Explain to the member what will be collected and for which purpose.
- Avoid excessive notes, judgments or data without a defined pastoral use.
- Restrict access according to each user role.
- Periodically review records, permissions and old entries.
- Document vendors, data sharing and relevant decisions.
Online Pastor and reports
How artificial intelligence uses data
AI features stay disabled until they are enabled. The individual table is calculated and displayed only inside Sanctuware. In behavioral reports, only aggregate counts are sent to the AI model.
Names, contacts, notes, prayer texts, messages, conversations and individual histories are not sent to the model in these reports.
In the Online Pastor, only the current message, the recent session history and content approved by the church are sent.
AI output should be reviewed by a person and does not replace pastoral, psychological, medical or legal care.
Across borders
International transfers
Some infrastructure or AI providers may process data in other countries. In those cases, the parties involved must observe applicable data protection law, adopt a valid transfer mechanism and give people clear information.
Rights and lifecycle
From collection to deletion
People's rights
Confirmation and access, correction, information about sharing, review of automated decisions and, where applicable, portability, objection, withdrawal of consent or deletion.
Retention
The church should keep each piece of data only for the period necessary for the stated purpose or to meet an applicable obligation. Conversations follow automatic retention configurable by the church. The organization can export the records and request correction or deletion through the responsible channels, where applicable.
Requests
The church answers requests related to its own members. Sanctuware provides technical support to locate, correct, export or delete data when the measure is legally applicable.
Security and incidents
Protection is a continuous process
Sanctuware uses organization separation, authentication, role-based permissions, administrative logs and secret protection. The church remains responsible for individual accounts, strong passwords, removing access and using the information appropriately.
See also member management, finance management and security.
Suspected unauthorized access, loss or exposure should be reported immediately for investigation. When an incident may cause relevant risk or harm, the controller should assess the notifications required by applicable law and to the people affected.
Exercise rights or report an incident
Identify the related church or account, describe the request without including unnecessary sensitive data and provide a secure way to reply.
Talk to SanctuwareEmail: contato@sanctuware.com
Organize your church data responsibly
Explore member management, role-based permissions and the privacy controls of Sanctuware.
Official references
Version 2026.07 · Effective July 19, 2026.