Legal
Privacy Policy
Last updated: 11 November 2026
1. Who we are and what this policy covers
Epiphany Anglican Church operates this website and determines how information is used for its website services. This policy covers visitors, member accounts, contact messages, newsletter subscriptions, prayer requests, testimonies, birthdays, groups, and online giving.
Church participation and the things you share may reveal religious beliefs, health information, or other sensitive personal details. Please share only what is necessary and avoid identifying another person without their permission.
2. Information we collect
- Accounts and profiles: name, email, phone number, login information, and profile fields such as title, nickname, username, address, gender, profile photo, and birthday day and month. We also keep membership approval, account access, and onboarding records.
- Your activity: contact messages, newsletter email addresses, prayer requests, testimonies and their summaries, group applications and answers, birthday wishes, and related visibility or delivery records.
- Preferences: birthday animation choice, reduced motion, AI editing, timezone, chat, pop-up notifications, and avatar visibility selections.
- Giving: amount, currency, purpose, payment reference, payment status, receipt email, optional payer name, account association where applicable, and recurring-giving records and provider identifiers.
- Technical and security information: authentication/session records, operational errors, and administrative audit records. Infrastructure and external services may also process connection information such as your IP address and browser details when handling requests.
If you choose Google sign-in, Google and our authentication provider process the sign-in and provide information needed to establish your account.
Scripture learning and saved verses
For Scripture learning, we use your account identity and the passages you choose to save, including references, translation labels, verse text or notes, tags, related references, and learning progress. These records support your personal study and recall practice. Other website features collect additional information as described elsewhere in this policy.
We do not sell your personal information or share your learning records for advertising. Hosting, authentication, database, and AI providers process information needed to operate the service; this is not a promise that information is never shared with service providers. Authorised church administrators may access records for support and security.
When you request AI lookup, study notes, or answers, the relevant reference, selected translation, remembered words, saved passage or notes, and question may be sent to the configured AI provider. Avoid including sensitive personal details. Browser storage remembers your voice, translation, and recall preferences; study drafts may be cached in the current tab.
Bible API: Scripture reading tools, including bulletin and Sunday school passage popups, use bible-api.com to retrieve Bible text. On a cache miss, our server sends the requested Bible reference and translation code to that service. These requests do not include your account ID, name, email, private notes, or learning progress. The provider can process the request URL, time, server connection IP address and other technical request information under its own privacy policy.
General reading tools offer KJV and WEB; signed-out visitors use KJV, while signed-in members can choose their preference. Retrieved passages may be stored in a shared public database cache using a normalized reference and translation key, without linking that cache entry to the reader's account. Passage popups reuse entries for up to seven days before refreshing them. Cache expiry is separate from scheduled database cleanup and does not promise immediate deletion from logs or backups. Bible text for these popups is retrieved from the verse service, not composed by AI.
This feature saves individually selected passages; it does not import or host complete, unauthorized copyrighted Bible databases. Do not use it to assemble or distribute one. Deleting a saved entry removes it from the active library; normal logs or backups may persist as described in this policy.
3. Why we use information
We use information to authenticate users, administer membership and access, provide the features you request, respond to inquiries, deliver church communications, process and reconcile gifts, support pastoral care, and investigate misuse or payment problems.
The legal basis depends on the activity: your consent where required, providing a service you request, legitimate operational and security interests where permitted, or legal obligations such as financial recordkeeping. Optional publication and sensitive information require particular care. You can contact us to withdraw consent or ask about the basis for a particular use; withdrawal does not undo earlier lawful processing.
4. Prayer requests and testimonies
Prayer requests: public requests can appear on the website. Private and anonymous requests are intended for authorised pastoral and prayer-review access rather than public display. Account-linked requests can be managed from your dashboard. The anonymous submission path omits your account ID, but the words you write may still identify you, and technical service records may exist. Anonymous does not mean that every trace of a visit is erased.
Prayer requests have a selected display period of one to six weeks. Expiry removes them from active display; it is not a promise of immediate erasure from every database, log, or backup. Logged-out or unlinked requests may not be recoverable through your member dashboard.
Testimonies: submitted stories may be published on the website and reviewed by church administrators. Depending on your submission choices, a story may show a name, gender, or profile photo. Anonymous submission omits account association, but details in a story can still reveal identity. An optional confirmation email may contain a management reference; keep that code private because it can be used to manage the submission.
Use the available account or reference-code controls to manage your testimony. Expiry and removal from display do not remove copies someone else has already made. Public content may be copied, indexed by search engines, or shared outside this website.
5. AI-assisted text editing and summaries
The testimony tools can send submitted text and editing instructions to external AI services to improve wording or produce a shorter summary. Submission may also request an automatic summary. The current integration can use Groq, Google Gemini, or OpenRouter and a model provider reached through OpenRouter; a fallback may send the text to another configured service if the first service fails.
AI results can be inaccurate or change your intended meaning. Review suggested wording before using it and avoid sending unnecessary sensitive information. Provider processing is subject to their own policies; we do not promise that all providers use the same retention or training rules.
Writing and submitting a testimony requires an active signed-in account, including when choosing anonymous publication. AI editing also requires sign-in. Turning off AI-assisted text editing in your account preferences prevents new testimony editing or summary requests to AI providers. It does not recall text previously sent.
6. Birthdays, photos, groups, and preferences
Birthday features use your saved day and month for personal greetings and celebrations. Birthday visibility determines inclusion in member-facing birthday lists; a private personal greeting can still appear for you. Birthday wishes record sender, recipient, animation type, and delivery information.
Profile photos can appear with member-facing features and with named testimonies where selected. Uploaded avatars currently use public image URLs: anyone with a URL may be able to retrieve that image. Saving the hide-avatar preference does not yet guarantee that every existing display or image link is restricted.
Group applications may be reviewed by authorised group leaders or church administrators. Account preferences are stored with your account, and authorised administrators can read preferences for support. Preferences control supported birthday effects, reduced motion, event and birthday popups, chat navigation, and event timezone displays. Operational confirmations and error messages still appear. Birthday dates follow the church calendar in Africa/Lagos.
7. Online giving and recurring gifts
Paystack handles payment checkout. We do not collect full card numbers or card security codes through our own forms. We do process payment metadata, transaction outcomes, and provider identifiers to reconcile giving, display account-linked history, manage recurring giving, and send acknowledgements.
Guest giving leaves your member account ID off the gift. It is not an untraceable payment: the receipt email, optional name, payment-provider records, and bank information may identify the payer. Recurring giving is account-linked where offered. Read Paystack's terms and privacy information and our giving guide.
8. Cookies and browser storage
The home page presents a storage notice that stays open until you make a choice. Visitors may continue without signing in. Account creation requires a separate, unticked acknowledgment of the Terms and Conditions and this Privacy Policy; Google registration also requires acknowledgment. Existing-account login does not show the signup checkbox. We record the terms version and acknowledgment time in your authentication account metadata.
Necessary sign-in cookies support account security and are required for account features. Account preferences are stored in the database, while browser preferences such as learning voices, translation choice, and recall mode may be stored in localStorage; not every preference is copied to both places. Acknowledging this notice does not opt you into marketing or unrelated tracking.
Authentication uses session cookies managed through Supabase. Theme preferences may also be remembered in cookies or browser storage. Local storage remembers items such as documentation consent, theme choices, and daily birthday celebration or mute flags; session storage can preserve an in-progress registration form.
A signed-in writer's testimony text can be saved in session storage under their account ID to recover it in the same tab after a refresh or sign-in. This draft is removed after successful submission and is not restored after 24 hours. Closing the tab normally clears its session storage.
The notice on documentation pages does not control all authentication cookies or storage across the site. Clearing or blocking browser storage may reset preferences, remove drafts, or require you to sign in again. Shared-device users should sign out when finished.
9. Access, service providers, and international processing
Cloudflare Turnstile helps protect authentication and email verification from automated abuse. Security checks run in your browser, and verification tokens are validated by Supabase or our server through Cloudflare. Cloudflare processes browser and network information to perform these checks.
Access depends on a person's role and the feature. Administrators manage membership, contact inquiries, content, and operational records. Authorised prayer reviewers access prayer-review content; this does not grant every prayer-team member access to all account or contact records.
We use Supabase for authentication, database and file services; Paystack for payments; Brevo and/or Resend for email; Upstash QStash for background delivery tasks; OneSignal for optional browser push notifications; and configured AI providers for the text tools described above. These services receive information needed for their function. External images, including Unsplash images, and links to services such as WhatsApp may also involve requests to those services.
Browser push notifications require your permission. OneSignal processes an opaque account identifier, browser/device subscription information, and notification content to deliver alerts. You can turn push off in Settings or your browser permissions. This is separate from in-app pop-ups. Notifications may appear on your device’s lock screen, and an alert already queued may still arrive after you sign out.
Service providers may process information outside Nigeria. Applicable data-protection requirements and relevant transfer safeguards must be considered when using those services. We do not sell your personal information.
10. Retention and security
Retention depends on the record and its purpose. Display expiry, account locking, or soft deletion does not necessarily erase underlying records. Financial, security, audit, and backup records may need to remain after content is removed or an account is closed. We have not published one fixed retention period for every category; contact us about a particular record.
We use authentication, role-based checks, and database access controls to limit access. No website or storage system can guarantee absolute security. Please report suspected unauthorised access promptly.
Data Security
We implement appropriate technical and organisational measures to protect personal data against unauthorised access, alteration, disclosure, or destruction. Measures include:
- Encryption: HTTPS/TLS protects data sent to our hosted services. Supabase provides encryption at rest for managed database storage. Browser localStorage is not an encrypted vault; do not store sensitive information in browser preferences. Supabase TLS information.
- Payment processing: Paystack is a PCI-DSS Level 1 certified payment processor. Full payment card numbers and security codes are handled by Paystack and are not stored on our servers. We retain transaction and receipt metadata needed to operate giving. Paystack security.
- Access controls: access is limited by account ownership, roles, and the operational responsibilities of authorised personnel.
- Security assessments and incident response: regular security reviews and incident response procedures are part of our security commitments. We assess reported weaknesses and suspected incidents and take appropriate action; this statement is not a claim of independent security certification.
Under section 40 of the NDPA 2023, we will notify the Nigeria Data Protection Commission within 72 hours of becoming aware of a personal data breach likely to result in a risk to individuals’ rights and freedoms. Where a breach is likely to result in a high risk, we will communicate with affected individuals immediately in plain language, including protective steps, subject to the Act’s provisions. NDPA 2023.
11. Your choices and rights
You can edit available profile fields and preferences, choose content visibility, and use available deletion controls. Contact us to request access, correction, deletion, restriction, objection, portability where applicable, withdrawal of consent, or help stopping newsletter messages. We may need to verify your identity and explain any lawful limits on a request.
You may also raise a complaint with the Nigeria Data Protection Commission. These choices are subject to applicable law and do not require you to give up rights you have under that law.
Parents or guardians should assist children with account registration and submissions. Please contact us if a child has shared personal or sensitive information without appropriate permission.
12. Contact and changes
Contact Epiphany Anglican Church, Evo Diocese, Port Harcourt, through our contact page or email epiphanyanglicanevo@gmail.com. Please describe your request without sending passwords, payment security codes, or unnecessary sensitive information.
We will publish revisions here and update the date when the policy changes. Significant changes may require additional notice or consent where applicable.