Marriage-Partner Emporium privacy policy

Policy version: 16 October 2026. Effective when this version is first published.

Operator and contact

Marriage-Partner Emporium is operated by Joshua, based in Lagos, Nigeria. For privacy questions and requests, contact marriagepartneremporium@gmail.com. Our developer website is https://marriagepartneremporium.com.

Information used by the app

Authentication: Clerk provides account registration, sign-in and session management. Depending on the sign-in method, Clerk processes account details such as email address, name, credentials or connected sign-in-provider information, together with session, device and network information needed to operate and secure authentication. Authentication information is not stored solely on your device.

Local and published profile information: The app keeps profile information, selected photo references, preferences, swipe history, matches, chat content and support/report records in local app storage on your device or browser. Profile fields may include name, date of birth, birthplace, gender, biography, education, occupation, income range, marital status, religious denomination, testimony, genotype and blood group. Religious and health information is sensitive; avoid entering information you do not want stored or disclosed.

If you explicitly choose to publish your profile, the app uploads your selected profile fields and photos to our server and private hosted photo storage, associated with your account identifier. Published profile information, including religious and health fields you include, is available to other signed-in members permitted to view it under the app's discovery access rules. Photo access uses short-lived links; recipients may still save copies. The server also stores account-linked likes, dislikes and Super Likes to support discovery and reciprocal matching. Publishing or unpublishing does not erase your local profile or chat history. Local demonstration profiles and matches may remain on your device. In-app support/report records are local; email the privacy contact for a request that must reach the operator.

Ad reward verification: If you choose a rewarded ad, our server stores your Clerk account identifier, a reward attempt, random verification tokens, the ad unit, timestamps and verified access expiry. Google receives random per-attempt identifiers, not your Clerk identifier or dating profile, to verify ad completion. Our server keeps transaction identifiers and receipt timestamps to prevent duplicate rewards.

Audio/video calls and call alerts: On calling-supported versions, the app sends your account identifier, display name, calling-enabled status and connected-chat contact references to our server. Contact references include profile and chat identifiers and, where available, email addresses sent for conversion into email hashes. The server stores your verified email as a hash and stores hashed contact emails rather than raw contact emails in its calling records. These hashes are linked to accounts and are not anonymous. Private contact mappings, calling-enabled status and block records help restrict calls to mutually connected contacts and prevent blocked calls; they are not a public contact directory.

LiveKit transports microphone audio and, for video calls, camera video between participants. LiveKit receives the call-room identifier, participants’ account identifiers and display names, and network and connection information needed to deliver calls. The other participant receives your live audio/video and room participant information. This implementation does not record calls or save call audio/video on our app server. This does not prevent another participant from recording or saving what they receive.

If you enable remote call alerts, our server stores your device’s Expo push token linked to your account. It sends that token, an incoming-call alert, the call type and call identifier through Expo’s push service and the applicable Apple or Google notification service. Notifications may be visible on your device’s lock screen. Alert delivery and calling while the app is backgrounded or closed are not guaranteed.

Subscriptions and billing: Installed iOS and Android versions use RevenueCat to support monthly subscriptions purchased through Apple's App Store or Google Play. We use your Clerk account identifier as the RevenueCat customer identifier to associate purchases and subscription access with your Marriage-Partner Emporium account. This identifier is pseudonymous, not anonymous: it can be linked to your account. RevenueCat processes store purchase receipts or purchase tokens, transaction and product identifiers, purchase history, subscription and renewal status, and entitlement and expiry information. Its subscription dashboard also provides purchase-history reporting and analytics. Our server requests subscription and entitlement information through our hosting provider's integration to verify paid access and purchase ownership. RevenueCat and the stores may also process app, device, network, locale and currency information needed to operate their services. Payment-card details are handled by Apple or Google, not collected by our app or billing server. We do not send dating profiles, religious or health fields, messages, photos, email addresses or names to RevenueCat as billing customer attributes, or use purchase history for ad targeting.

Service operation: Hosting, authentication and advertising providers may process network and technical information, including IP addresses and request/device information, to deliver, secure and troubleshoot their services.

Why information is used

We use information to authenticate accounts, provide profile and discovery features, publish profiles you choose to share, record discovery choices and reciprocal matches, maintain preferences and chats on your device, show ads where available, verify voluntary ad rewards, prevent reward fraud and handle privacy correspondence. Camera/photo-library access supports choosing profile photos. Notification permission supports app alerts; notification previews may be visible to someone using your device. You can change permissions in device settings.

We also use account-linked purchase and subscription information to verify monthly paid access, restore eligible purchases to the original Marriage-Partner Emporium account, check renewal and expiry status, prevent purchase fraud and support subscription reporting. Billing verification may occur when you sign in or return to the app, and periodically while the subscription check is active, even if you have not started checkout. Browser previews do not take payments or grant paid access from simulated purchases.

We use calling information to connect and authorize audio/video calls, show invitations, enforce contact and blocking restrictions, deliver optional call alerts, and limit call abuse. Microphone permission supports audio calls; camera permission additionally supports video calls. You can manage microphone, camera and notification permissions in your device or browser settings.

Google advertising and choices

Installed native versions may use Google AdMob for banners, browsing-break interstitials and optional rewarded ads. Browser previews and Expo Go do not request AdMob ads. We request non-personalized ads and do not supply dating profiles, religious preferences, health fields, chat content, photos or location as ad-targeting parameters.

Non-personalized ads do not mean no data collection. Google may process IP addresses, device or advertising identifiers, app interactions, diagnostic information and consent choices to deliver and measure ads and prevent fraud, subject to applicable permissions and settings.

The app checks Google's consent status before requesting ads and displays applicable consent forms configured for the app. Where Google requires privacy-choice re-entry, use Profile → Ad privacy → Manage ad privacy choices. You can also manage device advertising/tracking settings. Refusing tracking permission does not prevent ordinary app use.

Read Google's advertising privacy information, how Google uses information from partner services and Clerk's privacy policy.

Read RevenueCat's privacy policy, Apple's privacy policy and Google's privacy policy for information about their respective services.

Read LiveKit’s privacy policy and Expo’s privacy policy for information about their respective services.

Storage, retention and deletion

Calling retention and deletion: Our server stores operational call records containing call identifiers, both participants’ account identifiers and display names, chat references, audio/video call type, status, creation and expiry times, and acceptance time where applicable. Completed, declined or missed call records become eligible for automatic deletion seven days after creation once no room shutdown is pending. Maintenance checks every 30 seconds while the server is running; outages, backlogs or pending room cleanup may extend retention. Calling registrations, contact/email hashes, push tokens and block records do not have a seven-day automatic deletion schedule. The account-deletion process attempts to close active call rooms and remove the account’s calling registration, call records involving the account and related block records. Deletion may remain pending and retry if a service is unavailable. This does not guarantee deletion of provider-held technical records or copies kept by another participant.

Local information generally remains until you remove it using available app controls or clear the app/browser storage. Signing out does not erase stored information. Device/browser backups may retain copies independently of the app.

The Delete Account control requests deletion of your sign-in account and linked app-server records, including published profile, uploaded photo and swipe records. It removes account-owned local records only after server confirmation. Deletion may remain pending and retry if a service is unavailable. It cannot erase copies saved by other members, and does not automatically delete RevenueCat records or cancel store subscriptions. Do not treat it as complete erasure from every provider or device.

Registered devices can remove account-owned local data after reconnecting and receiving confirmation of completed account deletion. Private cleanup-token hashes are linked to your account while it exists. After deletion completes, the account link is removed, and the hash and deletion status are retained for up to 180 days, or until cleanup is acknowledged, whichever comes first. Devices that were not registered or remain offline beyond this period may retain local copies. Local data without verified ownership is not automatically erased.

For account or server-data deletion, email marriagepartneremporium@gmail.com. We may need to verify that a request concerns your own account. For remaining device-local copies, clear app/browser storage on each device where you used the app.

Published profile retention: Published profiles remain in the server directory until you unpublish them or account deletion removes them. Unpublishing removes the directory entry but does not itself delete uploaded photos or account-linked swipe records. Uploaded photos, including uploads not attached to a successfully published profile, and swipe records have no fixed automatic deletion schedule in the current implementation; account deletion attempts to remove the account-linked records and uploaded photo objects. Short-lived photo links are access controls, not a photo-retention deadline. Device backups and copies retained by other members are outside our remote deletion control.

Account-linked ad reward attempts become eligible for automatic removal 24 hours after attempt expiry. Expired rewarded-access records become eligible 24 hours after access expiry, once no retained reward attempts depend on them. Reward account records with no earned access become eligible 24 hours after creation, once no retained attempts depend on them. The server checks hourly while running and removes eligible records in bounded batches; outages, busy records and backlogs may extend retention. Transaction identifiers and receipt timestamps without a stored account identifier are retained without a fixed deletion date to prevent replay. No fixed retention schedule or guaranteed deletion-response period has been established for privacy correspondence. Clerk and Google also retain information according to their applicable policies and settings. We do not promise immediate or complete provider deletion.

Purchase history and subscription deletion: RevenueCat retains account-linked purchase history and subscription records to provide verification, restoration and reporting. No fixed automatic deletion schedule has been established for these RevenueCat records in this integration. Our billing server reads this information to verify access; it does not maintain a separate purchase-history database. Short-lived app access checks and catalog caches are not deletion of RevenueCat's records, and the RevenueCat SDK may cache subscription information on your device. The current account-deletion process does not automatically delete your RevenueCat customer record. To request deletion of billing-related personal information, email marriagepartneremporium@gmail.com; we may need to verify account ownership and handle the request separately with RevenueCat. Apple and Google retain store records under their own policies and legal requirements. Deleting app data, a Marriage-Partner Emporium account or a RevenueCat customer does not cancel an App Store or Google Play subscription or automatically issue a refund. Manage or cancel renewal in the store account used to purchase the subscription. We do not promise immediate or complete deletion by providers or a guaranteed deletion-response period.

Rights and security

Depending on applicable law, you may have rights to request access, correction, deletion or restriction of processing, object to processing, withdraw consent where processing relies on consent, or complain to the relevant data-protection authority. Email the privacy contact to make a request. Local profile information can be edited in the app. Withdrawing consent does not undo processing that has already occurred.

Information processed by service providers may be handled outside Nigeria. Local app storage should not be treated as encrypted confidential storage. Protect your device and browser access; no storage or transmission method is completely secure.

Changes

We will update this policy when the app's data practices change and identify the effective date on the public policy.