App Rejected – Need Guidance on 4.3(a) Spam

Hi everyone,

Our matrimonial app Bandhan Setu was rejected under Guideline 4.3(a) because Apple stated that the app duplicates existing dating/matrimonial apps.

Bandhan Setu is specifically focused on marriage-oriented matchmaking, and we also have a QR Code Validation feature that provides an additional layer of profile authenticity and trust.

Has anyone faced a similar rejection, and what would be the best way to demonstrate to App Review that these features provide a sufficiently differentiated experience?

Any guidance would be appreciated.

Thank you.

Has anyone faced a similar rejection

Yes. Dating app rejections are a top rejection complaint.

what would be the best way to demonstrate to App Review that these features provide a sufficiently differentiated experience?

Apple has decided enough is enough. Come up with a better app idea.

Has anyone faced a similar rejection

What's stopping you from running a search with 'dating app' or equivalent at this site? There are a dozen similar topics of the same nature this year alone.

Hello everyone,

We are developing a matrimony app called BandhanSetu and are currently preparing our App Store submission. I would like to get advice from other Apple developers who have experience with matrimony or dating applications.

BandhanSetu is specifically designed as a matrimony platform, rather than a conventional dating or social networking app. Our focus is on privacy, consent, family involvement, and AI-assisted matchmaking.

Some of our key features are:

  1. Consent-based profile privacy

Certain detailed information on a female user's profile is protected by default. A male user cannot view the protected information unless the female user accepts his request. After acceptance, access is granted according to our authorization rules.

  1. AI-assisted matchmaking

Our AI system analyzes profile information, preferences, interests, and compatibility factors to recommend potentially suitable matrimonial matches. The AI is intended to assist users and does not guarantee compatibility or marriage.

  1. Guest / Relative Access

Matrimonial decisions in India often involve family members. BandhanSetu therefore provides a Guest/Relative Access concept that allows a user to give a trusted family member or relative controlled access to assist with the matchmaking process.

The relative does not receive unrestricted access to the account. Access is controlled by the primary user and is subject to the permissions and privacy settings defined by the platform.

  1. QR-based profile discovery

Users can share their BandhanSetu profile through a QR code. The QR functionality continues to follow the application's privacy and authorization rules and does not bypass restricted profile information.

  1. Consent-based communication

Users can express interest in another profile, and communication becomes available according to the connection/acceptance workflow.

Our main product philosophy is:

Matrimony + Privacy + Family Participation + Consent + AI-assisted Compatibility

We would like to hear from developers who have built or submitted similar applications:

How would you recommend positioning these features? Have you faced challenges differentiating a matrimony application from existing dating/matrimony apps? Does a Guest/Relative Access model provide meaningful differentiation for a matrimony-focused application? Are there any Apple guidelines or considerations we should be aware of when presenting these types of features? What information would you recommend including in our App Store listing to clearly explain that this is a matrimony/family-oriented platform rather than a conventional dating app?

I'm primarily looking for developer experiences and practical suggestions, rather than an App Review appeal.

Any feedback from developers who have gone through a similar process would be greatly appreciated.

Thank you!

App Rejected – Need Guidance on 4.3(a) Spam
 
 
Q