—

## SECTION 1: Hero

**Headline:** Common Questions. Direct Answers.

**Subheadline:** Compliance officers and engineering teams ask us the same questions before integrating Diliguard. The answers are here.

—

## SECTION 2: Data Sources & Accuracy

**Q: Where does Diliguard source its data?**

Diliguard connects directly to primary government databases, official registry endpoints, and regulatory authority APIs. The system does not rely on third-party data aggregators. Every output reflects the live state of the underlying registry at the time of the query.

**Q: How often are sanctions and watchlist data updated?**

Diliguard monitors OFAC, UN, EU, HM Treasury, and 140+ regional watchlists continuously. The engine processes regulatory updates within minutes of publication. There is no 24-72 hour lag introduced by third-party cache intermediaries.

**Q: Does Diliguard access data from the dark web or deep web?**

Yes. The OSINT architecture accesses archived news, localized language media, and select deep web sources for adverse media and executive person trace investigations. This data is used solely for risk intelligence outputs and is never resold.

**Q: How does Diliguard handle language barriers in international registries?**

The system uses natural language processing to standardize unstructured legal filings in multiple languages. International corporate documents — including those in Mandarin, Arabic, Russian, and Portuguese — are processed and normalized into English-language intelligence reports.

—

## SECTION 3: Platform & Features

**Q: What is the difference between the portal and the API?**

The Diliguard portal is a browser-based interface for compliance officers and analysts who run investigations manually. The Developer API exposes the same intelligence capabilities as structured JSON endpoints for engineering teams building automated workflows.

**Q: Can Diliguard monitor existing client relationships continuously, or only during onboarding?**

Both. Diliguard supports point-in-time screening during onboarding and continuous monitoring for existing client and vendor portfolios. Automated alerts are generated when a risk profile changes materially.

**Q: Does Diliguard support cryptocurrency compliance alongside traditional KYC/KYB?**

Yes. Diliguard processes both fiat and on-chain intelligence within the same workflow. The crypto forensics engine correlates wallet transaction history with traditional identity records and delivers unified risk reports.

**Q: What is the entity resolution model and why does it matter?**

Standard AML tools use name-string matching, which generates large volumes of false positives. Diliguard’s entity resolution model cross-references biographical markers, corporate network graphs, registered addresses, and digital footprints to calculate a deterministic match probability. This is why Diliguard customers report significant reductions in false positive workload.

—

## SECTION 4: Integration & API

**Q: How long does API integration take?**

The Diliguard REST API follows standard conventions and returns structured JSON. Most engineering teams complete their initial integration within one to two business days. Full documentation and sandbox access are provided immediately upon account creation.

**Q: What endpoints are available?**

Available endpoints include: Corporate KYB scan, AML & PEP screening, Executive Person Trace, Transaction Risk Scoring, Crypto Wallet Investigation, IP & Network Intelligence, and Vendor Risk Monitoring. Full documentation is at [/developers](/developers).

**Q: Does Diliguard offer webhook support for continuous monitoring alerts?**

Yes. Engineering teams configure webhooks to receive real-time alerts when a monitored entity’s risk profile changes. The payload includes the updated risk score, the specific data point that triggered the change, and the relevant registry source.

**Q: Is there an MCP server integration available?**

Yes. Diliguard operates a Model Context Protocol (MCP) server that exposes intelligence capabilities directly to AI agents and agentic workflows. Full MCP documentation is at [/mcp-server](/mcp-server).

—

## SECTION 5: Pricing & Contracts

**Q: How is Diliguard priced?**

Diliguard uses a usage-based pricing model. Pricing is calculated per query for API integrations and per seat for portal access. Enterprise contracts include volume-based discounts and dedicated support. Contact the sales team for a custom quote.

**Q: Is there a free trial or sandbox environment?**

Yes. Engineering teams receive sandbox API access for integration testing before going live. The sandbox environment returns realistic structured responses using non-live data.

**Q: Are there long-term contract requirements?**

No minimum contract length is required for standard plans. Enterprise clients typically operate on annual agreements with SLA guarantees and dedicated account management.

—

## SECTION 6: Security & Privacy

**Q: How does Diliguard handle GDPR compliance?**

All data processing adheres to GDPR and applicable jurisdictional privacy law. Sensitive client data is never used for model training. All intelligence outputs are retained under configurable data retention policies. Full details are at [/security-compliance](/security-compliance).

**Q: Where is data stored and processed?**

Diliguard’s infrastructure is hosted on compliant cloud infrastructure with data residency options for EU-regulated clients. Data is encrypted in transit and at rest.

**Q: Is Diliguard data used to train AI models?**

No. Client-submitted data and intelligence outputs are not used for any model training, internal analytics sharing, or third-party data enrichment.

—

## SECTION 7: Support

**Q: What support options are available?**

Standard accounts include documentation access and email-based support. Enterprise accounts include a dedicated Customer Success Manager, priority SLA response, and quarterly compliance reviews.

**Q: Is there human expert support available for complex investigations?**

Yes. Enterprise clients can engage Diliguard’s analyst team for custom OSINT investigations beyond standard platform capabilities. Contact the sales team for managed investigation services.

—

## SECTION 8: Final CTA

**Headline:** Still have a question?

**CTA 1 (Primary):** Contact the Sales Team

**CTA 2 (Secondary):** Read the Technical Documentation