App Marketplace Compliance Rejection — Inconsistent Enforcement based on country?

Apps Third-Party Apps
1

Hi HubSpot Developer Community,

I’m reaching out because I’ve hit a wall with my app LeadCRM.io being rejected from the HubSpot Marketplace on compliance grounds, and I’m genuinely confused by what appears to be inconsistent enforcement.

What LeadCRM.io does:
LeadCRM.io offers contact enrichment (pulling professional data) and LinkedIn message sync — syncing LinkedIn conversations directly into HubSpot CRM records. That’s it. No automation, no bulk outreach, no scraping beyond what the user explicitly triggers.

What’s already listed in the Marketplace:
Several apps that go significantly further in LinkedIn automation are currently live and approved:

All three of these apps perform LinkedIn-related actions — which is a superset of what LeadCRM.io does. Yet LeadCRM.io, which does less, has been flagged for non-compliance.

My ask:
I’m not trying to bypass any rules — I want to comply fully. But I need clarity on:

  1. Which specific requirement does LeadCRM.io violate that the above apps do not?
  2. Is there a documented standard being applied consistently across all LinkedIn-integration apps or this is country based?

Has anyone else faced a similar situation? Would love advice on how to get a meaningful, specific response from the Ecosystem Quality team.

Thanks in advance.

Org Chart.png
Org Chart.png1120×834 132 KB

OrgChart
Workflow.png
Workflow.png1120×834 146 KB

Workflow Enrichment
image (4).png
image (4).png1833×905 168 KB

Contact Enrichment

2

Here’s what makes this even harder to understand:

Our app listing does not contain the word “LinkedIn” anywhere — not in the app name, not in the description, not in the feature list, not in the screenshots, not in the tagline. Nothing.

So the compliance rejection is for a feature that:

  • Is not mentioned in our listing
  • Is not visible to any HubSpot user browsing the Marketplace
  • Would never be encountered by someone discovering us through the Marketplace

Meanwhile, the three apps referenced above openly advertise LinkedIn automation, LinkedIn outreach, and LinkedIn sync — front and center in their listings — and all passed compliance review without issue.

We are genuinely asking: how does a feature that doesn’t exist in a listing become the basis of a listing compliance rejection? And how do apps that prominently advertise the same feature pass the same review?

We also want to raise something openly:

All three approved apps appear to be from US or European developer teams, while LeadCRM.io is built by an India-based team. We genuinely hope geography isn’t a factor — HubSpot’s terms don’t differentiate by developer location — but given the feature-by-feature evidence above, it’s a question we feel we have to ask publicly as Team is not able to provide any proper response and suspended our app for asking questions.

3

Hello @AShah64,

Welcome to the Community!

Thank you for taking the time to lay this out so thoroughly. The frustration of receiving a rejection without a specific reason is completely understandable, and your question about consistent enforcement is a fair one to raise.

The good news is that I was able to confirm our internal team is already engaged on your submission and it appears you should expect to hear from them directly with more specifics about your app’s situation. Also, if you do have more specific questions from the email reply you’ve already received, I’d suggest reaching back out on the thread you mentioned you have going with our Ecosystem team.

To your broader question ‘Has anyone else navigated the app review process and found a way to get clearer feedback from the Ecosystem Quality team?’

I’d love to tag in some of our community experts to see if anyone has first-hand experience getting apps published in the Marketplace!

Hi @zach_threadint, @RubenBurdin, @evaldas -- Do you have any additional suggestions for @AShah64 on getting feedback on their app?

Thank you!

Sam, Community Manager

4

Thanks @SamTassey for taking time to respond, after posting here I got email from team, hope to see a working path so we can publish the app.
I have conveyed the same thing which I have listed here and offered to make changes same as other apps to make things work.
Will keep you posted on the progress.

5

Hey @AShah64,

That’s great to hear! Thank you - we’d appreciate any updates you can share. Your solution could be a valuable resource for others facing the same issue in the future!

Thanks,

Sam, Community Manager