Privacy Notice

Who operates Zionel

Zionel is operated by Zionel LLC ("Zionel," "we," "us").

For privacy questions, contact privacy@zionelchurchapp.com. For product or account support, contact support@zionelchurchapp.com.

Age eligibility and children’s church records

Independent Zionel accounts require age 13 or older. We use an existing valid birthdate or account age declaration to assess eligibility, without showing an age range in the church directory or using it for advertising or analytics. Missing age information does not by itself block ordinary church activities. We request age information before care conversations, shared prayer and testimony, and AI interactions. In app versions with Apple age-sharing support, those features also use Apple age sharing and parental restriction signals on supported devices. An unavailable result does not count as an adult result. Regional or parental requirements may impose additional restrictions.

Children under 13 may remain in church-managed household and attendance records without an independent Zionel login. Those records are separate from permission to use shared feeds or private care conversations. Churches are responsible for lawful collection and any required guardian authorization for their records. This is not a claim that every jurisdiction permits the same access at age 13.

An account age declaration is retained with the account without a routine 90-day expiry and is removed when global account deletion is processed. A changed policy, conflicting birthdate or platform restriction can require another check. Restricted legal or security audit records and backup copies follow the retention rules below. Contact support to correct inaccurate age information; do not send identity documents or a child’s private details in an ordinary support message. Privacy information, sign-out and account deletion remain available when workspace access is restricted.

Scope and roles

Zionel currently serves churches in the United States. This notice covers information Zionel determines how to use for operating the service, securing accounts, supporting customers and administering the business. Zionel includes church-scoped workflows for member, visitor, donation and pastoral records; review the separate Church Data Privacy Notice.

What we collect and how it reaches Zionel

The information collected depends on the features you and your church use. You supply information when creating or updating an account, sharing content, asking for care, contacting support or using giving. Authorized church staff may enter records or import a spreadsheet about members, visitors and households, including people without a Zionel login. Zionel also generates operational records as features are used and receives relevant sign-in or transaction information from configured providers.

No advertising tracker was identified in the reviewed public application. No advertising-data sale feature was identified in the reviewed product. Zionel will reassess any location-specific sale or sharing disclosure when the service or applicable requirements change.

Payment-card entry is handled on Stripe-hosted checkout when that configured workflow is used. This does not mean Zionel receives no payment information: transaction references and retained provider events can contain payment-method metadata.

• Account and profile: name, email address, phone number, account and membership identifiers, optional profile photo and dates, preferences, and account age-range or eligibility information.
• Church records: membership and ministry roles, household relationships and addresses entered by authorized users, religious information such as baptism, attendance and service assignments. Attendance at a known church venue can reveal approximate location. A configured location-assisted check-in evaluates a foreground location reading; that workflow stores the attendance outcome rather than the raw coordinates.
• Shared and private content: prayers, testimonies, announcements, uploaded photos or videos, reactions, safety reports, and private care messages with participant and case references. An illness or hospitalization category and information voluntarily included in care messages may reveal health information; a financial-hardship request may reveal financial circumstances. Zionel does not need full medical records or bank credentials for those workflows.
• Giving and billing: donation amount, fund, recurrence, donor contact details, transaction status, receipts, refunds, disputes and provider payment references. Retained payment events can include bank or payment-method metadata even though card or bank entry takes place with Stripe. Zionel does not separately request optional payout bank-label fields. This does not mean earlier retained records or provider copies have already been erased.
• Enabled AI: the prompt, selected task context, output references and safety reports. Do not include confidential care, financial or safeguarding information in an AI prompt. A separate in-app choice governs sharing with an external AI provider where that feature is enabled.
• Operations and support: sign-in and security events, sessions, notification preferences and device push tokens, delivery results, interactions such as announcement acknowledgements, request timing and device/network diagnostics, support messages and the evidence you choose to provide. Device push tokens are not advertising identifiers.

Why information is used

Zionel uses account information to provide and secure sign-in, maintain church memberships and respond to account requests. Church-directed records support the church activities selected by authorized users, with access limited by church and role. Shared content, private care and safety reports support their stated communication, care and moderation purposes.

Transaction data supports giving records, reconciliation, refunds, disputes and applicable financial obligations. Notification data supports enabled communications and delivery handling. Operational diagnostics and interaction records support security, reliability and feature operation; the App Store disclosure separately identifies product-interaction analytics. Age eligibility is used for access and safety, not advertising or analytics. Enabled AI uses are explained before external-provider sharing.

Some information is necessary for an account or a requested workflow. Profile details, content, device permissions and optional features should be provided only where relevant. Declining an optional permission does not by itself grant or remove a church role. Applicable legal bases and additional jurisdiction-specific requirements still require review before any broader compliance claim.

Who receives information

Authorized church users receive church-managed information only through their permitted workflows. An administrator does not automatically receive every private conversation. Zionel uses providers for hosting, storage, security and selected features; not every listed provider is used by every church.

Render supports application and database hosting; Amazon Web Services supports configured private media and audit storage. Stripe handles configured giving and transaction services. Resend supports transactional email; Google Workspace handles email sent to Zionel’s privacy and support addresses. Cloudflare supports configured anti-abuse challenges. Twilio SMS, Google or Apple sign-in, and external AI processing are feature-dependent. OpenAI is the configured external AI adapter where enabled. Review the provider notice for the relevant purposes and limitations.

Service providers processing information on our behalf are required under applicable service and data-processing terms to use it for authorized purposes and provide the same or equivalent protection described in this notice. These obligations address confidentiality, security, protective subcontractor terms, and return or deletion subject to applicable retention requirements. Standard terms may incorporate those obligations without a separate signed document.

Some providers also act independently for defined purposes under their own privacy notices. Stripe processes certain payment information for its legal, fraud-prevention and financial-service responsibilities. Cloudflare processes Turnstile browser and network signals both to protect the site and to improve its own bot-detection service. Hosting providers may separately process service-account and usage information for security, billing and service operation. Those roles do not authorize Zionel to disclose private care content for unrelated purposes.

Retention and account deletion

Active account and church records are retained to provide the requested service, subject to the record’s workflow, church instructions, account deletion, safety needs and applicable legal obligations. Removing a post from publication or ending a church membership is not the same as deleting a global Zionel account.

Start global account deletion from Profile. The workflow revokes sign-in and memberships, removes directly addressable identity information, redacts the deleted person’s authored prayer, testimony and care-request content, and queues applicable processor or media deletion work. Separate church records, financial records, security evidence, legal holds and backup copies may require restricted retention. The account-deletion status explains pending work; a request being accepted is not proof that every provider copy has already been erased.

Retention depends on the record’s purpose, the account or church relationship, outstanding requests or disputes, applicable financial and legal obligations, and any documented hold. Restricted backups and audit records can remain after active account data is removed. A configured retention target or an accepted deletion request does not establish that every retained copy has been erased. Contact privacy@zionelchurchapp.com for help understanding the applicable record category or the progress of a deletion request.

Your privacy choices and requests

Use Profile to update your contact information and start account deletion. Email changes require confirmation; the current address remains active until the new address is confirmed. Use available notification preferences and your device settings to manage optional push, camera, photo or location permissions. Withdrawing a permission stops the corresponding optional device access; it does not itself delete records already submitted.

For a consent-based feature, stop using that feature and contact privacy@zionelchurchapp.com if you need help withdrawing a choice or understanding the effect on existing data. Account or church records may still be retained for another applicable purpose. Privacy rights and any response or appeal procedure depend on the law and Zionel’s role; no unsupported universal deadline or blanket exemption is promised.

Email privacy@zionelchurchapp.com for privacy questions, access or correction requests, or help with account deletion. For church-managed records, contact your church administrator first; if you cannot reach the church or the issue concerns Zionel itself, contact Zionel directly. Describe the request and the relevant church without sending passwords, verification codes, identity documents, payment credentials or private pastoral narratives. We may ask for proportionate verification through an established account channel before disclosing or changing records.

Version and material changes

The version and effective date identify the applicable notice. Before material changes take effect, Zionel will provide the notice or obtain consent required for the change through the appropriate in-app or email communication. A policy edit alone does not authorize a new use of information. Ask privacy@zionelchurchapp.com for the applicable notice or help locating a prior version.