Trust

Responsible local B2B discovery for teams that care about trust.

Munjam is built for legitimate business discovery, qualification, team review, and export. This page explains the guardrails customers should understand before using exported lists in commercial workflows.

Proper use
step.01
Define the market

Start with a clear city, category, and business reason for the list.

step.02
Qualify carefully

Review available fields and fit before selecting records for action.

step.03
Hand off narrowly

Move only the records that match the team’s intended workflow.

step.04
Follow up responsibly

Use lawful messaging, respect preferences, and remove businesses when required.

Proper use

A practical trust guide for using Munjam lists, exports, credits, and integrations with clear expectations and lawful commercial intent.

Legitimate business purpose

Use Munjam to understand local markets, qualify businesses, plan team review, and organize commercial work that your team has a valid reason to perform.

Data availability is contextual

Fields can vary by market, record, and plan. Teams should review what is actually available before relying on any field in a discovery workflow.

Quality before volume

The strongest workflow is not the largest possible list. It is a smaller, better-qualified list with clear ownership and context.

Respectful team review

Customers are responsible for honoring opt-out, consent, privacy, and commercial communication rules that apply to their market and recipients.

Trust

Ready for public and payment review

This page summarizes how Munjam works commercially and operationally, so customers and reviewers can understand the product before creating an account.

Review lists before use

Teams should check fit, category, location, and available fields before moving records into team review or CRM systems.

Use exports appropriately

Exported files and integrations should be shared only with people and systems that need them for the intended workflow.

Keep internal ownership clear

Assign who owns team review, what message is appropriate, and when the business should be removed from a discovery workflow.

Comply with applicable laws

Munjam provides workflow software. Customers remain responsible for discovery workflow compliance in their jurisdiction and target markets.

Proper use

Build company lists with total market clarity.

Stop guessing about data quality. Munjam sets clear expectations for what’s available across every market, from Riyadh to Cairo.

boundary.01

No guarantee of complete fields

Munjam does not promise that every business will include every contact or context field.

boundary.02

No use for harmful targeting

Do not use Munjam to support harassment, discrimination, deception, or activity that violates privacy or team review rules.

boundary.03

No resale of exported data as a raw dataset

Munjam is intended for your team’s legitimate workflow, not for repackaging raw exports as a standalone data product.

boundary.04

No bypassing plan limits

Credits, exports, API access, webhooks, and advanced destinations must be used within the plan and billing terms.

Trust FAQ

Proper use

Can Munjam be used for team review?

Munjam can help prepare qualified business lists, but customers are responsible for using those lists in lawful, respectful commercial workflows.

Does proper use affect exports?

Yes. Exports should preserve context, stay within plan limits, and be shared only with the people or systems that need them.

Who decides whether a discovery workflow is compliant?

The customer. Munjam provides software and public guidance, but customers must evaluate the laws and rules that apply to their discovery workflows.

Build qualified lists with context, then use them with care.

Munjam gives your team a clearer workflow for local market work while keeping expectations, limits, and responsibilities visible.