FAQs

This section includes frequently asked questions about the Digital Intelligence (DI) SDKs.

General product behavior

Does Digital Intelligence collect and maintain device-based or hardware-based identifiers like IMEI, MAC address, or SIM card numbers?

Digital Intelligence SDKs do not collect or expose hardware identifiers such as IMEI, SIM, or eSIM information.

No IMEI or SIM/eSIM identifiers:
Modern iOS and Android platforms restrict access to these identifiers. As a result, our SDKs neither collect nor expose SIM/eSIM details, and IMEI is not collected.
No hardware MAC address:
Mobile operating systems and modern browsers obfuscate or block access to hardware MAC addresses. Our SDKs therefore do not collect or expose a device’s hardware MAC. Instead, our signals rely solely on OS-permitted attributes to ensure privacy compliance and reliable device intelligence.

SDK blocking and ad blockers

We've previously had trouble with a similar vendor's SDK being blocked by ad blockers. Are there any known issues or best practices we should be aware of to prevent this with your SDK if needed?

Mainstream ad blockers (using default settings) typically do not block the Digital Intelligence (DI) Web SDK.

However, most SDK failures we observe are caused by:

Enterprise firewalls
VPN configurations
Strict Content Security Policies (CSPs)
Network restrictions that block SDK scripts or ingestion endpoints

Required endpoints

The DI SDK requires access to the following endpoints from the browser or application:

Endpoint	Purpose
`https://ingestion.dv.socure.io`	Device and behavior data ingestion
`https://network.dv.socure.io`	Network telemetry collection
`https://analytics.dv.socure.io`	Analytics and session data

Best practices to prevent blocking

1. Allowlist Socure DI endpoints in your Content Security Policy (CSP) and network egress

Add Socure DI endpoints to your CSP allowlist:

CSP connect-src: https://ingestion.dv.socure.io https://network.dv.socure.io https://analytics.dv.socure.io

If loading the SDK via script tag, also allowlist the SDK host:

CSP script-src: https://sdk.dv.socure.io

2. Use NPM package installation (recommended)

Installing the Web SDK via NPM (instead of script tags) provides several advantages:

Avoids content filters targeting third-party script hosts
Improves load reliability in JavaScript frameworks (React, Angular, Vue)
Reduces dependency on external CDNs

3. Optional: Use a reverse proxy (advanced)

For highly restrictive environments, configure the SDK to route through a customer-owned reverse proxy using the configBaseUrl parameter. This makes traffic appear as first-party requests.

Please coordinate with Socure before enabling this setup.

4. Implement graceful fallback and retry

Retry mechanism: Add retry logic with exponential backoff for session initialization

Timeout handling: Handle transient network issues (DNS resolution, mobile network hiccups)
Fallback strategy: Ensure your application continues to function when session tokens are unavailable

This approach ensures other verification checks can proceed even if the DI SDK encounters issues.

Updated 3 months ago