Frequently asked questions.

Embargo searches a registry assembled from supported sanctions, export-control, and watchlist sources across 10 regulatory jurisdictions. The Coverage page names the configured sources and distinguishes screening-registry data from regulatory-change monitoring.

Not by itself. A result is an identity-review candidate based on the submitted name and the evidence available in the registry. Review names, aliases, addresses, identifiers, source records, and transaction context before deciding whether the listed record and your counterparty are the same party.

No. It means no candidate appeared in the completed Embargo search at that point in time. It is not clearance, authorization, or proof that the party is absent from every relevant source. Coverage, spelling, transliteration, ownership, end use, and transaction-specific rules may require additional review.

Cadence depends on the source and processing path. Priority regulatory feeds are polled every four hours, while consolidated registry sources and enrichment pipelines generally refresh daily. The Status page shows recorded receipts and flags stale, missing, or unavailable evidence; polling cadence is not a delivery guarantee.

No. Embargo supports restricted-party review and preserves evidence. It does not determine item classification, end use, licensing, ownership aggregation, programme scope, jurisdiction, or whether a transaction is authorized. Those decisions remain with the customer and, where appropriate, qualified counsel.

You can save counterparties that matter to your process. Embargo re-screens the saved set after registry updates and records listed, no-current-listing, and incomplete outcomes. A notification is sent only after a relevant result is detected and processed; timing varies by source and processing status.

Paid plans can upload up to 500 names in one CSV. Embargo records the batch, searches each submitted identity, and returns candidate results and source-linked evidence for review. A name counts against the applicable screening allowance, and completion time depends on file size and service conditions.

For an eligible paid-plan screening, Embargo can issue a signed, timestamped record bound to the stored screening evidence and decision state. The certificate describes what was checked and what the evidence showed at that time. It is not a legal opinion, clearance, authorization, or substitute for the underlying source records.

Embargo withholds a current certificate if required matching, registry, or ownership evidence is incomplete, invalid, or predates the current evidence contract. A lifecycle correction can invalidate a screening and revoke its certificate; the identity must then be screened again.

Professional and Business include email alerts, a daily digest, and delivery of processed regulatory alerts to a configured Slack incoming webhook. Delivery depends on a valid destination and successful provider processing; the audit record distinguishes successful, failed, and retried delivery attempts.

Free is a permanent $0 plan with 25 individual screenings per month, 5 saved counterparties, registry access, and the weekly regulatory digest. It does not require a payment card.

Professional is $99/month or $990/year and supports 250 monitored counterparties. Business is $299/month or $2,990/year and supports 2,000 monitored counterparties, REST API access, guided onboarding, and priority support.

Yes. Professional and Business include a 14-day trial started through Stripe Checkout. A payment card is required for that trial; cancel before it ends to avoid the first paid charge. The permanent Free plan does not require a card.

Yes. Public screening is available without an account, and the guided demo is a focused 30-minute evaluation of screening, monitoring, evidence, coverage, and implementation fit. The demo is not a subscription plan or free managed casework.

Use Manage billing in dashboard settings to open the Stripe customer portal. Cancellation takes effect at the end of the applicable trial or billing period. For a monthly-to-annual change that is not available in the portal, contact billing@getembargo.com before renewal.

The Security page describes application controls, operational safeguards, service providers, responsible disclosure, and current procurement limitations. Provider trust links are included for their own control and certification materials; those attestations belong to the providers and do not certify Embargo.

The Privacy Policy lists account, screening, product-profile, preference, billing-reference, and standard usage data, together with purposes, subprocessors, retention, and customer rights. Payment-card details are processed by Stripe and are not stored on Embargo servers.

Configured Google AI services assist with source-grounded enrichment, classification, drafting, and evaluation using public regulatory or entity evidence where appropriate. Generated customer-visible intelligence is evidence-bound and review-gated. Account credentials, payment details, and private customer files are not presented as source evidence for public entity notes.

A standard customer DPA is still being prepared. Contact hello@getembargo.com with your requirements and Embargo will confirm which documents are currently available. Do not treat a DPA as agreed until both parties approve it in writing.

Business includes REST API access. SSO and SCIM are not standard self-service capabilities today. Discuss identity, procurement, security, and implementation requirements during a guided demo before treating them as committed scope.