Wallace Ridge app Privacy Policy
Effective October 22, 2026.
Wallace Ridge Pentecostal Church, with developer Aaron Spence, provides the Wallace Ridge app so you can watch services, listen to sermons, view events, and choose to receive church updates. You can use public content without creating an account.
Information we use
When you opt in to church notifications, the app sends a randomly generated installation identifier, an Expo push token, and your device platform to our notification service. We store subscription status and timestamps, along with records of notification submissions and delivery results. These records support church updates and troubleshooting. They do not tell us whether you read a notification.
An installation secret is kept in secure storage on your device. Our service stores a hash of that secret to verify registration changes and deletion requests. We do not ask for your phone's hardware identifier, a member login, or an email address to register for updates. Device registration and delivery records are not used by the church for advertising or sale.
Requests for sermons, events, artwork, and videos share network information, such as your IP address, with the services handling those requests. Embedded Vimeo video may also involve cookies, playback information, or other technical information under Vimeo's practices. If you contact the church, we receive the information you include in your message.
Services involved
Base44 hosts notification administration and backend functions. Google Firestore stores notification registrations and delivery records. Expo relays notifications through Apple Push Notification service and Firebase Cloud Messaging. Vimeo provides video; the church's podcast provider supplies audio, and Google Calendar supplies public church events.
Giving opens Tithely's giving form in your browser. The app does not collect card details or process donations. The giving provider handles information you enter on its form.
Adding an event opens your device's event editor. You choose whether to save or cancel. We do not upload your personal calendar to the notification service.
Retention
We apply these periods to the church notification database:
| Record | Retention |
| Active registration | Until opt-out, an invalid-token response, deletion, or 365 days without an authenticated app check-in. Sending notifications or receiving delivery receipts does not extend this period. |
| Inactive registration | The usable registration token and token mapping are removed when we process opt-out or invalidation. Minimal credential and opt-out/security information is kept for 30 days. |
| Device-level notification delivery details | 90 days from creation, unless removed sooner through device deletion. Copied usable tokens are removed after submission processing; older copies are removed by cleanup. |
| Announcement text and aggregate totals | 365 days from creation. Totals retained after detail removal do not contain device identifiers. |
| Deletion completion record | 365 days from completion. This record contains an unlinked receipt number, completion status and time, without the device identifier or push token. |
The existing five-minute maintenance schedule scans bounded retention pages every 15 minutes, including while notification sending is paused. Expired records and older token copies are removed over successive runs. A backlog or service interruption may delay physical cleanup; registration expiry is also checked before new sending. Minimal security markers for completed deletion requests are kept for 30 days after completion to prevent stale registration requests.
Notifications and device deletion
Notifications are optional. Open the app's bell button to manage Church updates. Device settings also control whether notifications can appear or make a sound. Turning notifications off disables the subscription after our service receives the change; existing delivery records remain subject to the retention periods above.
Choose Delete this device's notification data in Church updates to request deletion for that installation. After confirmation and successful authentication, we disable the registration first. We remove its token mappings and associated delivery records in batches. A completion message appears only after those records have been removed. The minimal security marker and unlinked completion record described above remain for their limited periods.
If your phone is offline, it saves the pending request securely and retries when you reopen the app. Our service cannot stop sending until it receives the request. Keep the app installed and reconnect/reopen it until completion is confirmed. Deleting the app alone does not submit a deletion request. Secure local preferences may survive reinstalling on iOS.
Watching, listening, and viewing events remain available after deletion. Updates remain off until you explicitly enable notifications again; this creates new installation credentials. Notifications already handed off to a delivery provider cannot be recalled.
Contact and email requests
Email wallaceridge18@gmail.com or use our Contact page for privacy questions or help with a deletion request. If available, include the device support code shown in Church updates. This code helps locate a record but does not prove ownership by itself. Do not send installation secrets, passwords, payment information, or identity documents.
Because the app has no member account, an email address alone does not identify a registration. We may ask you to complete the authenticated request in the app or use another proportionate verification step. If you no longer have access to the installation, contact us for help; we will not delete another device's information merely because someone knows its support code.
We aim to acknowledge email requests within seven days and complete verified requests within 30 days. In-app requests normally complete sooner. These are operational targets, and applicable legal requirements still apply.
Providers, backups and restoration
The in-app deletion process removes the specified records from the live church notification database. Hosting logs, infrastructure copies, and records held by delivery/content providers may have separate retention. We do not promise immediate deletion from all provider systems. Contact the church for information about a specific request.
Any restoration of the church notification database must occur with sending paused. Completed deletions must be reapplied before sending or registration resumes. Provider-managed logs and backups follow the applicable provider’s retention practices; we do not specify a single expiration period for those systems.
Provider information: Base44 privacy, Google privacy, Expo push delivery, Apple privacy, Vimeo privacy, Spotify privacy, and Tithely privacy.
Changes
We will update this policy when the app's data practices change. The effective date appears at the top of this policy.