Apostolic Faith (WECA) Privacy Policy

Last updated: April 9, 2026

This Privacy Policy explains how Apostolic Faith Mission, West & Central Africa ("AFM WECA", "we", "our", or "us") collects, uses, stores, and discloses information in connection with the AFM Heritage mobile and web application, related services, and supporting backend systems.

AFM Heritage is an offline-first study, worship, heritage, and reference app. Many core features work locally on your device. Some features connect to our online services to provide updates, account mobility, live webcast discovery, announcements, feedback delivery, reactions, diagnostics, and related capabilities.

If you do not agree with this Privacy Policy, please do not use AFM Heritage.

1. Who We Are

AFM Heritage is provided by:

Apostolic Faith Mission, West & Central Africa
Website: https://apostolicfaithweca.org
Contact page: https://apostolicfaithweca.org/form/contact
Support email: support@apostolicfaithweca.org
Support phone: +2347007000800

These channels may also be used for privacy and deletion requests.

2. What This Policy Covers

This Privacy Policy applies to:

the AFM Heritage Android, iOS, desktop, and web apps
the AFM WECA sync and mobility backend at https://ahsync.apostolicfaithweca.org
support workflows directly connected to the app

This Privacy Policy does not govern third-party services that may be opened or embedded from within the app, such as:

YouTube
Google Maps
Wikipedia
dictionary or reference sites
other external links opened by the app

Those third-party services operate under their own privacy policies and terms.

3. Information We Collect

Depending on how you use AFM Heritage, we may collect the following categories of information.

A. Information You Provide Directly

You may provide information when you:

submit feedback
link an account for cloud mobility
use live AI features
create, import, export, back up, restore, or synchronize personal study data

This may include:

your name
your email address
device label or account label
feedback subject and message
notes and note content
reminder details
backup or restore files
linked-account credentials such as an access code

Important note: access codes are used for authentication workflows. They should be handled securely and are not intended to be displayed publicly.

B. Study and User-Generated Content

AFM Heritage stores and may process user-created or user-linked study data, including:

notes
highlights
bookmarks
reminders
reading history
reactions such as stars or thumbs-up
announcement read or dismissal state
cached popular highlight data
linked-account synchronization records

Most of this data is stored locally on your device first. If you enable backup, restore, export, or linked-account cloud mobility, relevant data may also be uploaded to AFM WECA backend services.

C. Account Mobility and Cloud Sync Data

If you enable linked-account mobility, we may process:

linked account identifier
email address
device label
session status and expiry information
synchronized note and study records
mobility snapshots and record state checksums

This data is used to help you back up, restore, or synchronize personal study data across supported builds or devices.

D. Feedback and Support Data

If you send feedback through the app, we may receive:

name
email address
feedback category
subject
message content
technical payload attached by the app for delivery or diagnostics

E. Diagnostics and Error Data

To maintain and improve AFM Heritage, we may process diagnostics or error-report information, such as:

device identifier generated by the app
platform label
app version and release label
runtime mode
error summary
stack trace
crash or diagnostics payload
timestamps associated with the event

F. Push and Notification Data

If push transport or vendor-native push is enabled in your build or on your device, we may process:

app-generated device ID
push registration state
permission status
delivery readiness status
vendor push token
linked-account binding status for push routing

On some platforms or builds, reminders may be stored locally without vendor-native push being active.

G. AI-Related Data

If you explicitly enable live AI features and choose to use them, AFM Heritage may send:

the text you selected
bounded surrounding context
related source labels or anchors

AFM Heritage is designed so that live AI uses only the selected text plus bounded surrounding context, not the whole document by default.

H. Information We Generally Do Not Collect

The current release candidate of AFM Heritage does not require or intentionally collect the following through the app's main code path:

precise location
contacts
call logs
SMS
microphone recordings
camera images
calendar data
advertising ID
installed app list

If future releases add any such capability, this Privacy Policy should be updated before release.

4. How We Use Information

We use information we collect to:

provide and operate AFM Heritage features
store and synchronize personal study data
deliver notes, reminders, highlights, bookmarks, and reading history
provide account mobility, backup, restore, and linked-device continuity
process feedback and improve the app
deliver announcements, refresh events, and related notifications
provide diagnostics, troubleshoot problems, and maintain service reliability
enable optional community features such as reactions and popular highlights
support optional live AI requests when enabled by the user
protect the security, integrity, and proper functioning of the app and backend
comply with legal, operational, or ministry-related obligations

5. When We Share Information

We do not sell your personal data.

We do not share your data with third-party advertisers.

We may disclose or make information available in the following limited situations:

A. Within AFM WECA Systems

Information may be processed within AFM WECA first-party systems and infrastructure used to provide:

backend synchronization
announcements
reactions and popular highlight workflows
feedback handling
diagnostics
account mobility

B. At Your Direction

Information may be disclosed when you deliberately use features that interact with third-party services, such as:

opening or watching live webcasts on YouTube
opening branch addresses in Google Maps
opening external reference pages such as Wikipedia or dictionary resources
sharing exported data or note content using platform sharing features

When you do this, the relevant third party may collect data under its own privacy policy.

C. Service Providers and Technical Operators

We may use hosting, infrastructure, or technical service providers to operate AFM Heritage systems. These providers may process data on our behalf, subject to appropriate operational controls.

D. Legal and Safety Reasons

We may disclose information where reasonably necessary to:

comply with applicable law or lawful process
respond to valid requests from public authorities
protect the rights, property, safety, or security of AFM WECA, users, or others
investigate abuse, fraud, or security issues

6. Legal Bases and User Choice

Depending on where you are located, our use of information may rely on one or more of the following grounds:

your consent
provision of requested services or features
our legitimate interests in operating, securing, and improving the app
compliance with legal obligations

Where consent is relevant, you can often choose whether to use certain connected features, such as:

linked-account mobility
live AI
community signals and synced reactions
notifications
external sharing

7. Offline-First and Local Storage

AFM Heritage is designed to work offline first. Many features store data locally on your device, including:

notes
highlights
bookmarks
reminders
reading history
settings and preferences
cached announcements and popular highlights

Local device data remains on your device unless you choose to export it, restore it, synchronize it, or otherwise transmit it through a connected feature.

8. Data Retention

We retain information for as long as reasonably necessary to:

provide requested features
maintain account mobility and synchronization
support backups and restore flows
investigate issues and protect system security
comply with operational, legal, or administrative obligations

Retention periods may vary depending on the data type and whether the information is stored:

locally on your device
in AFM WECA backend systems
in exported backup files under your own control

Unlinking an account from the app does not necessarily delete all server-side records immediately. Privacy and deletion requests may be submitted through the support contacts listed in this policy. AFM WECA may need to verify the requester's identity and may retain certain records where reasonably necessary for security, fraud prevention, legal compliance, or legitimate operational purposes.

9. Security

We use reasonable technical and organizational measures to help protect information handled by AFM Heritage, including:

encrypted transport for production backend traffic over HTTPS
application and backend access controls
local-first design for many study features
controlled administrative access for supported backend workflows

However, no method of transmission or storage is completely secure. We cannot guarantee absolute security.

10. Children and Child Safety

AFM Heritage includes ministry and teaching resources that may be used by families, guardians, teachers, and church workers, including children's materials such as Picture Rolls and Watch and Pray content.

AFM Heritage is not designed as a social networking or open-user communication platform for children. It does not provide general public chat or user-to-user messaging functionality.

If you believe a child's information has been submitted improperly through the app or any connected workflow, please contact AFM WECA promptly through the public contact page or designated safeguarding/ICT channels.

11. International Transfers

Your information may be processed in jurisdictions where AFM WECA, its infrastructure, or its service providers operate. By using AFM Heritage, you understand that information may be transferred to and processed outside your immediate place of residence, subject to applicable law and reasonable safeguards.

12. Your Choices and Controls

Depending on the feature and platform, you may be able to:

use many core content features offline without linking an account
export local backup data
import or restore local backup data
link or unlink an account for cloud mobility
disable or avoid live AI features
disable community signal syncing
control whether popular highlights are shown
manage notification permissions at the device level
remove notes, reminders, bookmarks, highlights, and other local data inside the app

Privacy and deletion requests may be submitted through:

AFM WECA may request enough information to verify the requester and identify the relevant device, account, or data before acting on a request.

13. Third-Party Content and Links

AFM Heritage may display or open content provided by third parties, including:

YouTube webcast playback
Google Maps address handoff
Wikipedia
dictionary or other reference pages

Your use of those third-party services is governed by their own policies and terms. AFM WECA is not responsible for the privacy practices of third-party services that are not under our control.

14. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect:

app changes
backend changes
legal or regulatory developments
new integrations or content workflows

When we make material changes, we may update the date at the top of this policy and take other appropriate steps to notify users where required.

15. Contact Us

If you have questions about this Privacy Policy or AFM Heritage privacy practices, please contact: