Privacy Policy

How we use information

App Functionality includes operating accounts and access controls, displaying profiles and community content, reviewing applications, processing registrations and payments, enabling messages and calls, delivering transactional and community communications, moderating abuse, and preventing fraud or security incidents. Administrative access is used to operate and support these features.

Analytics helps us understand usage, reliability, and performance. Our published purposes are shown for each category above: Other Usage Data is Analytics only; User ID, Device ID, Product Interaction, Crash Data, Performance Data, Other Diagnostic Data, and Other Data Types are used for both App Functionality and Analytics. The remaining categories are disclosed for App Functionality. We do not describe the service as collecting no data or having no analytics.

Information you choose to provide

You choose whether to apply for membership. The current application requires faith and church-related answers to complete that application; these questions are not optional individual fields. If you do not wish to submit sensitive religious information, do not submit the application and contact us to discuss your options. Application answers are stored with your account for administrative review, not automatically published in the member directory.

Profile photos, banners, social links, biographies, posts, media, messages, reports, calls, and event participation depend on your use of those features. Event registrations can include additional attendees' names, email addresses, phone numbers, and questionnaire answers. Only provide information about other people that you are authorized to share.

Passwords and login credentials are handled through Base44's authentication system or the selected login provider. A password is not stored as a plaintext member-profile field. This is not a claim that authentication systems collect no credentials or security information.

Payments and purchase history

Event and membership payment forms use embedded Stripe Elements Payment Element fields with PaymentIntents and subscriptions. They are not an outside-app Stripe Checkout flow. Stripe may redirect for authentication or a selected payment method, but that does not make all payment entry external to the app.

Stripe-hosted fields handle sensitive payment details. The reviewed application code does not store full card numbers, CVCs, or raw bank credentials in our app-controlled records. This does not mean we can never access payment information: Stripe merchant tools and APIs expose payment-related information, including payment-method references and, where available, masked details. Billing fields default to automatic and vary by method; full billing-address collection in the native app has not been verified.

Separately, we keep purchase history needed to fulfill registrations and memberships: purchased event or membership, amount, payment and registration status, Stripe customer, PaymentIntent and subscription references, and membership or renewal dates. Membership subscriptions can renew automatically. Stripe also processes device and activity information for payment authentication, security, and fraud prevention.

Who can see your information

• Member directory: active members can view directory-visible profiles, including names, business details, general location, interests, bio, contact information, social links, photos, and banners. Account settings provide a Directory Visibility switch. Hiding a directory profile does not erase previous views or independently shared posts, messages, or event previews.
• Community content: posts, comments, and associated author information are shown to the audience of the relevant community or event area. Direct messages are intended for their participants; administrators have access for operation, support, and moderation. Reports can contain a snapshot of reported content, reporter and reported-user identifiers, reasons, and details. Blocks affect supported directory and interaction features, not copies already received by someone else.
• Events: public event previews can display a limited selection of registrants' names, photos, titles, and businesses. Named previews for member-only events are restricted to active members and administrators. Registration details and questionnaire responses are available for event administration; public previews do not publish the full registration record.
• Uploads: current profile, post, and message-media uploads use publicly reachable file URLs. Anyone holding a file link can open that file even if the screen displaying it requires login. Do not upload confidential media on the assumption that the file URL itself is access-restricted.
• Communications and notifications: emails and notification requests may include recipient identifiers, sender or registrant names, event information, message text, and destination links. Where device notifications are enabled and supported, content may appear on a lock screen according to device settings. A message should not be treated as hidden from the notification processor simply because it is an in-app direct message.

Service providers and other sharing

Information is sent to services used to deliver the features below. The information involved depends on the feature used, build, configuration, and permissions. Provider SDK capabilities alone are not evidence that all possible data is collected. We may also disclose relevant information to address a legal requirement, a dispute, fraud, abuse, or a security incident.

• Base44 provides hosting, authentication, databases, uploads, and analytics. It processes account, content, operational, identifier, and usage information associated with those services.
• Stripe processes payments, subscriptions, authentication, fraud prevention, and related payment or device information, as described above.
• SMTP.com handles transactional and community email delivery, including recipient addresses and names when supplied, subject lines, and message contents. Platform authentication emails may instead be handled by Base44's authentication email service.
• Daily.co provides live calls. When you use calling features, it processes display names, room or connection information, and the live audio, video, chat, or screen content you choose to transmit. Other call participants receive shared media. No call-recording implementation or retention of call recordings was verified; live transmission does not itself establish a retained recording.
• The reviewed iOS binary includes SDK privacy manifests for Sentry, Firebase Installations, Google Maps, Google Sign-In, and reCAPTCHA. These support the disclosed native identifier, usage, crash, performance, diagnostic, and other SDK categories. A manifest's presence does not establish that every SDK feature, precise location capability, or sign-in option is active. Data linkage and purposes follow the category summary above rather than a blanket claim that all diagnostics are anonymous.
• Server-side notification requests can send user identifiers, notification or message content, and links to OneSignal. Conditional OneSignal/Median bridge support also exists, but installation of those native SDKs in the reviewed WixOneApp iOS binary has not been verified. This policy does not assume they are installed or that every notification attempt reaches a device.
• Google Fonts supplies web fonts; loading them sends network requests and associated connection information to Google. If YouTube or Vimeo content is embedded in a page you open, its player can receive network and device information and use provider cookies or similar technologies. As of October 16, 2026, no published video-content records matched the app's YouTube or Vimeo embed paths. These embeds are conditional, not evidence of current advertising tracking.

Cookies, identifiers, analytics, and tracking

Operational cookies and local storage support authentication, saved preferences, sessions, and analytics. Web analytics uses account identifiers when signed in and a persistent local app-instance or browser identifier. Native SDKs can use installation and device identifiers. Stripe uses device or browser identifiers and activity signals for fraud prevention; its standard script can load before a payment is submitted. These functions are not automatically advertising tracking.

Web analytics can receive referral, campaign, and advertising-click parameters if present in an incoming link. Their capture alone does not establish cross-company targeted advertising or ad measurement. Web collection does not prove that the native wrapper sends every identical event; the iOS disclosure also accounts for native SDK manifest categories.

Our published App Store disclosure declares no advertising or marketing purpose and no Apple-defined tracking. Apple-defined tracking concerns linking app data with data from other companies' apps or websites for targeted advertising or advertising measurement, or sharing it with data brokers. No such flow, IDFA/ATT advertising implementation, or data-sale integration was demonstrated in the reviewed app. Operational analytics, diagnostics, or payment fraud prevention alone do not establish that tracking. This finding is not a guarantee about every unverified provider capability or the separate practices of external sites you visit.

Your choices and permissions

• Review or edit the available profile fields in your account settings and use the Account tab's Directory Visibility control. Login-provider-managed fields may need to be changed through that provider. Contact us for assistance with information you cannot change in the app.
• Choose whether to submit applications, upload media, register additional attendees, send messages, or use calls. Use available report and block controls for unwanted interactions. Do not share information you do not want the intended audience or relevant service provider to receive.
• Manage camera, microphone, photo selection, screen-sharing, and notification permissions in the device, browser, or feature controls where offered. Refusing permission can prevent the associated feature from working. Revoking permission does not remove media or records already submitted.
• Browser cookie and storage controls can clear local preferences or identifiers and may sign you out. They do not delete server-side records or necessarily stop provider-side security processing. No in-app switch that disables all analytics is currently provided; contact us with privacy questions or requests rather than assuming device permissions disable all analytics.

Retention and account deletion

We retain information for the operation for which it is needed, including maintaining accounts and community content, fulfilling registrations and memberships, handling support or disputes, preventing fraud and abuse, and meeting applicable billing, accounting, legal, or security requirements. Different app records and providers have different retention needs; we do not promise a single retention period or immediate erasure from every system.

To use the current deletion flow, open your account settings, select the Account tab, find Delete Account, type DELETE, and choose Delete My Account. The request applies to the signed-in account. On success, the app clears its local storage and signs you out.

The current flow removes your authored posts and their dependent comment/like/save records, your comments, likes and saves, messages you sent, notifications addressed to you, reports you filed, block relationships involving you, and event registrations and seat holds matched by your linked account or registrant email. It then requests deletion of your user account through the platform. Shared conversations keep other participants' messages and can retain participant identifiers; your stored conversation name is changed to Deleted member and a last-message preview authored by you is cleared.

Deletion does not cancel a paid Stripe subscription or erase Stripe customer, payment, invoice, or subscription records. Cancel any subscription before deleting your account; contact support for help. Billing, dispute, legal, fraud-prevention, and security information may remain where required or needed for those purposes. Removing an app record also does not ensure deletion of the original uploaded file, sent email or notification copies, other people's messages or reports, or records retained by providers. The current flow does not directly purge upload storage, analytics, or every SDK/provider system. Contact us about these records; we will assess what can be removed and what must be retained.

Contact us

For privacy questions, account-deletion assistance, or questions about retained information, contact Redemptive Real Estate:

• Email: Contact@rhemaweb.biz
• Phone: 910-400-2090
• Support: https://app.redemptive.exchange/support

We may update this policy when our features or data practices change. The date at the top identifies this version.