"Why can't we export the contacts as a list to use in our own platform?"
Three reasons documented. Reason 1 legal basis preservation: the Ley 81 Article 7.2 legitimate interest basis is documented for outbound through EMP infrastructure with EMP's clear opt-out mechanism. Export to third-party infrastructure breaks the documented compliance chain and would require the receiving party to establish their own legal basis from scratch. The export-then-use pattern that ZoomInfo, Apollo, Cognism, Lusha, LeadIQ ship hands compliance responsibility to the buyer; EMP keeps the responsibility on the operator side, which procurement teams in regulated industries typically prefer. Reason 2 data quality preservation: the quarterly verification cycle requires EMP control over the verification infrastructure and the list state. Export creates fragmentation where exported data ages without verification while the canonical repository continues to verify; the buyer ends up with stale data they paid for and cannot easily refresh. Reason 3 pricing model preservation: list providers charge per-contact precisely because exported lists generate revenue once but ongoing verification costs are not covered by the one-time fee. EMP charges for ongoing platform access including ongoing verification. About 18 percent of discovery calls surface this design boundary as a procurement question; about half proceed with platform fit confirmed once the design boundary is understood; half choose list providers when standalone export is the priority requirement. The honest verdict matters: when standalone export is the requirement, list providers win and we say so.
"How do we audit the data quality before signing? We need to verify the 96-97% accuracy claim."
Two audit patterns supported during evaluation. Pattern 1 ICP query with sample export under NDA: the ICP query returns contact count and freshness statistics; under NDA, a 100-contact sample export from the queried segment can be released for buyer-side verification. The buyer runs the sample through their own email verification tool (NeverBounce, ZeroBounce, BriteVerify, etc.) and confirms MX validity rate independently. The 100-contact sample is destroyed after verification per NDA terms. About 14 percent of discovery calls request this pattern, primarily from data ops engineers who want independent verification before procurement signs. Pattern 2 sample campaign with full delivery metrics: the 30-day Pro tier subscription returns full delivery metrics including hard bounce, soft bounce, complaint rate, unsubscribe rate measured at the SMTP level. The metrics give buyer-side measurement of actual repository quality on real campaigns rather than relying on EMP's published numbers. Both patterns are diagnostic, not promotional; the purpose is to verify the published numbers hold for the buyer's specific ICP and use case. About 8 percent of audit results show numbers slightly below the published averages (typically 4-5 percent bounce on niche verticals where the repository depth is thinner); when this happens, EMP discloses the segment-specific calibration honestly during the conversation rather than waiting for the audit to surface it.
"Our compliance team flagged the legitimate interest basis as risky. What's the actual ANTAI enforcement track record?"
Honest enforcement context. ANTAI (Autoridad Nacional de Transparencia y Acceso a la Información) became enforcement-active under Ley 81 since the 2021 Decreto Ejecutivo 285 regulation activation. ANTAI enforcement actions across the broader Panama market since 2021 have averaged 12-18 per year, primarily targeting consent-based platforms operating without documented basis or without functional opt-out mechanisms. The enforcement pattern targets two categories: platforms claiming consent without documentation (most common), and platforms offering opt-out but not honoring opt-out within reasonable timeframe (second most common). Legitimate interest basis under Article 7.2 is structurally outside the enforcement pattern when properly documented with balance test plus functional opt-out. EMP track record: zero ANTAI sanctions recorded against EMP or any tenant operating within the documented framework since 2019 effective date. The framework documentation is available under NDA for review by tenant compliance counsel; the documentation carries the balance test template, the opt-out mechanism specification, the quarterly review protocol, and historical correspondence with ANTAI on framework clarification questions. If your compliance team requires consent-based basis instead of legitimate interest: EMP supports tenant-managed consent-based lists imported into the platform with EMP infrastructure handling delivery and reputation, but the verified repository access feature does not apply to consent-based mode. About 6 percent of tenants operate in consent-only mode; they pay the same platform tier price but use only their own consent-based contacts. The honest tradeoff is documented during onboarding.
"How does the 250K+ count compare to ZoomInfo's 320M? Isn't EMP just much smaller?"
Honest scale comparison. ZoomInfo at 320M+ records globally is genuinely larger; the comparison is meaningful when the use case is global B2B outbound where database breadth matters more than segment depth. The breadth-vs-depth tradeoff matters for Latin B2B specifically: ZoomInfo's 320M total covers approximately 4-7 percent Latin coverage based on published research, which calculates to 13-22 million Latin contacts in raw count. Filtered for active corporate email with verification, the practical Latin pool drops to 3-6 million per Apollo and Amplemarket published verification rates. Filtered for the ICP that any specific buyer cares about (size band, role, vertical, country), the practical pool typically drops further by 70-90 percent depending on ICP narrowness. EMP at 250K+ is built specifically for the Latin segment with depth that mainstream platforms cannot match per-record because the sourcing methodology is Latin-specific. The honest framing for procurement: if the use case is global outbound where you also want US plus EMEA plus Latin from one provider, ZoomInfo wins on breadth. If the use case is Latin-only outbound where the practical pool you actually use after ICP filtering is the metric that matters, EMP and ZoomInfo ship comparable practical pool counts but with EMP at meaningfully better bounce rates and lower cost. About 22 percent of discovery calls end with the recommendation to use ZoomInfo for US plus EMP for Latin as a hybrid stack rather than EMP standalone for global; the hybrid pattern is the honest answer when global scope matters.
"Can we get phone numbers? Most of our outbound is dial-heavy."
Phone-number coverage is intentionally not part of the EMP repository. Three reasons. Reason 1 legal basis differs: phone outbound under Ley 81 Article 7.2 legitimate interest is significantly harder to defend than email outbound because phone calls are higher-intrusion than email and the balance test result tilts differently. The EMP framework does not extend to phone numbers because the framework would not survive ANTAI scrutiny at the same documentation depth. Reason 2 verification economics: phone-verified mobile numbers require human verification at the depth Cognism Diamond Data hits in EMEA at 98 percent accuracy. The verification cost is substantially higher than email verification, and the operational team required to ship phone verification at quality differs from the team that ships email verification. EMP focuses on email; phone is outside the operational scope. Reason 3 use case alignment: EMP tenants are typically running email-first outbound at scale rather than dial-heavy outbound at smaller volume. The use case where phone matters more than email is typically enterprise sales targeting Fortune 500 decision-makers; that use case is better served by Cognism (EMEA), ZoomInfo (US), or specialized phone data providers (Lead411 for direct dials). About 9 percent of discovery calls surface phone-number requirement as a deal-breaker; we redirect to Cognism or Lead411 honestly and the call ends without conversion. The redirect matters more than the conversion.
"What happens to our access if we cancel the platform subscription? Do we lose the contacts?"
Two distinct categories of contacts at cancellation. Category 1 repository contacts you outbounded but never engaged with: access stops at cancellation. The contacts are not yours; they are EMP's repository made available during the subscription. The legal basis for outbound under Ley 81 Article 7.2 was documented for outbound through EMP infrastructure during the subscription period. After cancellation, you do not retain rights to outbound to those contacts through other infrastructure because the documented basis does not transfer. Category 2 repository contacts you outbounded and engaged into your own consent-based list: remain yours after cancellation. Contacts who opened your campaign, clicked your link, replied to your message, downloaded your asset, requested information, or otherwise engaged with your messaging through EMP infrastructure represent a separate consent layer that you obtained from the recipient. The consent you obtained creates a separate legal basis under your own controllership and you can export those engaged contacts anywhere, use them with any platform, treat them as your standard CRM contacts. About 30-40 percent of repository contacts that a typical tenant engages with first-touch convert to engaged-list status within 6-12 months of regular outreach; the engaged list grows over time and remains yours regardless of platform subscription status. This distinction matters legally and operationally; the design is intentional. The terms documentation at /terminos-condiciones.html section 10 covers the data portability commitment in detail.
