What ClockIN processes, why we use it, what stays private and how to make a privacy or human-review request. Updated 5 October 2026.
This can include account details, profile information, projects, posts, skills, applications, messages, community activity, opportunity information, settings, feedback, preferred beta username requests and files you intentionally upload.
The public ATS + Tools collection can be used without an account. Resume files, pasted resume text and job-description text are processed to generate the requested result and are not stored by the public career-tools service. The service can keep a short-lived salted network fingerprint, tool identifier, request count and timestamp for abuse prevention. It does not store the raw network address in that ledger.
Your sign-in email is account data held through the authentication service and is not copied into the public profile simply to display it in Profile Studio. Secondary email and phone fields have separate visibility controls.
A resume used in the public tools is processed transiently as described above. A resume imported into Profile Studio is processed to extract profile and ATS-style fields and is not intended to become public automatically. A resume intentionally submitted with a ClockIN job application can be stored privately so authorized hiring-side users can review that application. These workflows have different storage and access behavior.
Skill Proof can process assessment answers, timing, work products, scores and levels. Standard v3.3/v4 verified attempts can also process integrity signals and require fullscreen and camera access. Quick Math is excluded from that monitored path and does not use camera, MediaPipe, fullscreen enforcement or semantic AI grading. During a verified attempt, ClockIN can record fullscreen exits, tab or window focus changes, blocked clipboard or capture actions, camera interruptions and coarse camera-derived signals such as whether a face appears present, whether multiple faces appear, whether a phone is visibly present, or whether the visible head is repeatedly oriented away. ClockIN does not use these checks for biometric identity matching or to infer protected or sensitive traits. Verified Skill Proof camera integrity now uses MediaPipe locally in the browser for face presence, extra-person, visible-phone and calibrated eye/head attention signals. Raw camera frames are not sent to ClockIN or a paid vision API by this integrity path. ClockIN serves the pinned MediaPipe runtime and model assets from its own deployment rather than fetching those files from a third-party CDN during the assessment. MediaPipe documentation states that input frames stay on-device, but the MediaPipe Tasks SDK can send performance and utilization metrics to Google; those metrics do not contain the raw camera frames. The current hybrid Skill Proof does not provide ClockIN Copilot during either the v3.3 chain flow or the v4 real-work flow. Objective workspaces can be graded directly from protected deterministic rules. Work that cannot be judged safely by a deterministic oracle, such as code reasoning or professional judgement, can be sent after the attempt to a model-processing provider for semantic rubric evaluation. That evaluator is instructed to judge the submitted work and task constraints rather than keyword overlap, writing style, or protected traits. Public proof surfaces use derived results rather than exposing the private question bank, answer rubrics, model evaluation traces or raw assessment history. When a member has an awarded Skill Proof badge, the linked ClockIN-issued certificate and public verification page may show their public profile name and username, assessed skill, medal, score, award date, expiry date and certificate ID. Private answers, raw integrity events, evaluator traces, institutional verification files and contact details are not published on certificates. Practice sessions can use temporary server-side question and scoring records while you take the mock; mock scores are not retained in attempt history. Real certifying assessments save account-linked starts, answers and results. If you delete real attempt data, a minimal private access receipt can remain to enforce free starts and cooldown.
When a role uses a ClockIN interview, the current candidate runner can process webcam video, answer audio, answers, transcripts where available, timestamps, device/session events and integrity telemetry. The current runner does not record the candidate's screen. Before browser media permissions are requested, ClockIN shows a feature notice describing the configured recording, transcription and AI-assisted review. Interview media is private to authorized review surfaces. Integrity telemetry is review evidence, not proof of dishonesty, and is kept separate from competence scoring.
Project Defence v3 does not send answers or project evidence to an LLM and does not use BM25 or a synthetic answer bank as a correctness judge. It builds project-specific challenges from deterministically extracted evidence facts and automatically scores only project-fact checks, ownership consistency and a structured verification plan. Automatic approval also requires a passing ownership-boundary challenge, failure-injection structure, cross-answer consistency and verification plan. The failure-injection response is retained for review rather than semantically graded by a model. Uncertain substantive cases require human review. Other ClockIN features, including AI Interviews, can use language-model or automated systems to summarize job-relevant evidence and assist hiring teams. These systems can be imperfect. ClockIN does not present them as an undisclosed autonomous final hiring decision. Signed-in members can use Privacy & Data to ask for an explanation, contest an AI-assisted result or request meaningful human review of a specific ClockIN application or interview.
Job and candidate recommendations can use job-relevant data such as skills, Skill Proof, profile text, work evidence, stated role preferences, location, remote preferences and work mode. Candidate discovery only includes people who opted in. ClockIN does not intentionally use protected traits as candidate-ranking inputs.
If you submit a college or work verification request, ClockIN can process the organization name, optional institutional email, optional private proof document, reviewer note, verification status and review history. Uploaded proof is not public. The verification form records which Privacy Notice version was shown when the request was submitted.
Projects can include your description, personal contribution statement, project context, optional AI-use disclosure and supported evidence you intentionally attach, such as public links, documents, spreadsheets, presentations, images, datasets, repositories or other permitted artifacts. You can mark evidence public or verification-only. Verification-only evidence is restricted to you, authorized ClockIN operations or review surfaces, and systems used to provide the verification workflow; it is not shown as a public project attachment. A verified Project Defence can require fullscreen and camera access. MediaPipe locally checks face presence, extra people, visible phones and calibrated eye/head attention; raw camera frames are not sent to ClockIN or a paid vision API by this integrity path. These signals are integrity evidence, not biometric identity matching or protected-trait inference.
Source-control verification is optional. If you verify a public GitHub repository or deployed project, ClockIN can store the source URL, verification challenge state, verification timestamp and public metadata needed for the project record. Project Defence can process the project description, contribution statement, evidence labels and notes, bounded verified public website structure, bounded public GitHub structure and source excerpts, and bounded contents of supported uploaded PDF, DOCX, XLSX, PPTX, CSV, JSON, TXT or Markdown artifacts. The automatic fingerprint uses facts actually extracted from inspectable evidence; user-entered evidence labels, notes and unsupported-file metadata can remain available to reviewers but do not become automatic scoring facts. Project Defence also processes the selected challenge set, your written answers, browser-reported camera/fullscreen preflight state, integrity events, review record and verification outcome. The v3 Defence path does not send project evidence or camera frames to an LLM or paid vision API. The self-service data export includes your Defence answers, outcomes and session records but excludes hidden challenge definitions, private evidence fingerprints and internal scoring traces because exposing those internals could compromise future verification attempts. Source verification demonstrates control of that source at that time; it does not by itself prove authorship.
ClockIN can process public or community text and supported public images through automated safety checks, including OpenAI moderation and narrow first-party language rules used to catch targeted abuse or threats that generic moderation can miss. Reports, quarantine signals and human review remain separate safety controls. Automated moderation can make mistakes. Hiring evidence such as private application answers, resumes and Skill Proof responses is not treated as ordinary social-content moderation material.
When you join the beta waitlist, ClockIN can store your email, name, audience selection, source, join history and an optional preferred username request. A preferred username is a request, not a guarantee. If you are approved, the request can be carried into Pre-Beta access and applied only if it is still available when your account is activated.
ClockIN can store follows, threaded replies, reactions and mentions so conversations and network features work. A follow notification may include a short public-profile summary of the follower. Mention records are visible only as needed to the author, the mentioned person and product operations.
ClockIN may process sign-in events, page interactions, notification state, security signals, timestamps, rate-limit state and other operational data needed to provide features, prevent abuse and understand reliability. For product-health analytics, a signed-in member can also create a coarse daily active marker and update a last-seen timestamp. Aggregate admin and investor metrics are derived from these markers and from product records that already exist, such as posts, comments, Skill Proof attempts, applications and completed payments. ClockIN does not currently rely on third-party advertising cookies, keystroke logging, mouse-trail recording or private-message content to calculate these metrics.
We use information to provide accounts and profiles, run feed and messaging features, recommend opportunities or talent, operate communities, provide public career tools, run project and hiring workflows, maintain security, respond to support and privacy requests, improve the product and comply with applicable obligations.
Public profile, project, public Project Proof evidence, post and community information can be visible to other people according to product controls. Application data, account-security information, private contact data, interview media, direct messages, identity-verification documents, verification-only Project Proof evidence, Project Defence submissions and other restricted records are handled through feature-specific access rules.
ClockIN relies on service providers for web hosting, database and authentication infrastructure, Cloudflare R2 object storage, email delivery, model processing, meetings, feedback forms and payment processing where a feature requires them. Supabase provides the primary database, authentication, row-level authorization and protected backend-function layer, while Cloudflare R2 stores uploaded binary files. Depending on the provider and feature, data can be processed outside your country. ClockIN maintains a public service-provider page and updates it as material production providers change.
Signed-in members can open Settings → Privacy & Data to request access/export, correction, account deletion, restriction or objection, withdrawal of an optional permission, or another privacy action. The same page shows the status of submitted requests. Some deletion requests can require separation or limited retention where records are needed for security, another person's records, dispute handling, hiring accountability, a legal hold or another applicable obligation.
Different records have different retention needs. ClockIN maintains an internal retention catalog and is progressively moving data classes toward explicit retention handling rather than indefinite storage. Raw interview media has a role-closure-based deletion schedule, while structured interview evidence, applications, payment records, security records and dispute material can have different retention needs. Other categories use provisional review periods until jurisdiction-specific and contractual requirements are finalized.
ClockIN uses access controls, row-level security, authentication assurance checks, private storage, rate limits and platform security features intended to protect data. No internet service can guarantee absolute security. Use a strong password, enable two-factor authentication when available, and report suspicious activity promptly.
As currently designed, ClockIN does not sell personal information to advertisers or give advertisers access to private conversations. If the business model materially changes, this notice will be updated before that change is applied.
ClockIN is evolving, so this notice may change as features, providers and applicable obligations change. Material updates will be reflected here and, where appropriate, surfaced at the point where the relevant data is collected.
For a tracked privacy request, use Privacy & Data after signing in. You can also contact info@goclockin.com.