ClockIN uses outside infrastructure only where a product feature needs it. This page describes the main providers currently represented in the product code. Payment providers will be added here before live paid checkout is enabled.
Core infrastructure
Why we use it
Database, authentication, private/public file storage and server-side/Edge Function infrastructure used by ClockIN.
Data involved
Account identifiers, profile/application records, uploaded files and product records as required by each feature.
Core infrastructure
Why we use it
Web application hosting, deployment and request delivery.
Data involved
Web requests and the application data needed to render or process a request.
Used when email workflows are enabled
Why we use it
Email delivery for configured ClockIN notification and digest workflows.
Data involved
Recipient email address and the email content needed for that message.
Used when the relevant AI feature is configured
Why we use it
Language-model processing for configured AI-assisted features such as project-specific verification and interview support.
Data involved
Only the feature context needed for the configured AI task, such as relevant source excerpts, questions, answers or hiring context. ClockIN should not send unrelated profile data.
ClockIN's planned payment stack is Razorpay for India and Paddle for international checkout. They are intentionally not listed above as live processing providers until merchant configuration and checkout are actually enabled. We will update this page before that happens.
Provider terms, locations and subprocessors can change over time. ClockIN should review this list whenever infrastructure changes and before entering a market that requires additional transfer or processor documentation.