Developer FAQ
Technical answers for engineering teams evaluating and integrating the Circadify rPPG SDK. From platform support and data handling to pricing and production deployment, find the details you need to make integration decisions with confidence.
Frequently Asked Questions
Most teams have a working proof-of-concept within one day and ship to production within one to two weeks. The SDK installs via standard package managers, and sample projects cover common patterns for telehealth, wellness, and underwriting use cases.
Native frameworks are available for iOS (Swift and Objective-C via Swift Package Manager), Android (Kotlin and Java via Gradle), and Web (TypeScript and JavaScript via npm). Each module is optimized for its platform runtime with Metal, GPU compute, or WebGL acceleration respectively.
No. All rPPG inference runs on-device. The SDK needs a network connection only for initial license validation and periodic usage reporting. Scan data never leaves the user's device unless your application explicitly transmits it.
Because biometric data is processed locally and not transmitted to Circadify servers, the SDK simplifies HIPAA and GDPR compliance. You control whether vitals data is stored, transmitted, or discarded. We provide a compliance brief that maps SDK data flows to common regulatory frameworks.
You can configure server-side webhooks to receive scan-complete payloads, error events, and aggregated usage metrics. Each event is signed with HMAC-SHA256 so your backend can verify authenticity before processing.
Pricing is based on monthly active scans. We offer a free sandbox tier for development and testing, with production tiers scaled to your volume. Contact our team for a quote tailored to your expected scan volume and deployment model.
Have a Technical Question?
Our developer relations team is available to help with integration planning, architecture reviews, and production deployment.