Frequently asked questions

Does it affect my app’s performance?

Impact depends on the application, configuration and devices. Measure it during integration, including startup, resource use and user experience. Our team supports that assessment.

What if the device has no internet?

Local detection and response can continue with the available policy. Attestation, policy updates and report delivery require connectivity. Pending reports are sent when connectivity returns.

What data does it collect about my users?

Processed data includes security reports, technical application, device and network data, attestation data and the report’s IP address. A user identifier is included if configured by your application. Pulse does not independently access application content; reports should not be considered anonymous.

Do the App Store and Google Play allow it?

Integration must be reviewed against your application’s distribution requirements. Apple and Google make the final call on each app; using Pulse does not guarantee approval.

How does Pulse respond to a risk signal?

The policy can record the signal, notify the application or trigger termination. Other actions, such as requesting additional verification, require implementation in your application. Assess the impact before enabling restrictive responses.

How long does integration take?

Timing depends on the platforms, flows that need a response and backend integration. An initial assessment defines scope, tests and production acceptance criteria; there is no single timeline for every application.

Evaluate Pulse for your application

Discuss coverage, integration requirements and deployment options with our team.

Request an evaluation