Career Test
Checking account…

Policies and transparency

AI Policy

How AI-assisted processing is bounded. AI Career Test is operated by an individual operator.

Effective August 9, 2026

This page describes the current service scope. Product behavior and provider availability may change only with corresponding policy and implementation updates.

01Defined route

AI Career Test uses AI-assisted processing for defined report-generation and Career Coach functions. The current intended route is AI Career Test directly to the official DeepSeek API using deepseek-v4-pro with thinking disabled and no OpenRouter or OpenAI fallback. Report workflows send restricted aggregate assessment inputs; Coach workflows send only locally mapped intent and session-stage codes, categorical aggregate score buckets and career-match identifiers.

02Prohibited model payloads

The model path must not receive raw 40-question answers, OAuth/email/session/order identifiers, resume or job-description source material, employment/education/contact/export data, or raw free-text Career Coach messages. A future mapping, provider, model or tool requires separate technical, privacy and legal review.

03Output and claim limits

AI output may be incorrect, incomplete, inconsistent or inappropriate. Users must review output and must not use the service to create false credentials, employment history, claims or material misrepresentations. The service does not promise suitability for an application, ATS, employer, visa or other decision.

04Retention claims

Provider agreements, no-training commitments, retention and ZDR routing are separate safeguards. Current evidence is limited and does not support a general promise of zero retention for all processing.

05Career Journey

Career Journey tools do not use an AI model for private resume, job-description, answer, offer, compensation, negotiation, or private-reflection text unless a separate technical, privacy, and legal review approves a specific workflow before release. Until then, those materials must not be sent through a model route. Any later approved workflow must use the exact approved provider, endpoint, data category, and fail-closed controls, and must not enable web search, plugins, external tools, or an unapproved fallback for private content.