SD CVPortal Use terms

Prototype use boundary

Terms Placeholder

This page documents expected use for the current prototype. It is not a final commercial terms agreement and should be reviewed by counsel before public production use.

Allowed use

Hiring managers and recruiting agents may use a valid access code or access link to review a candidate's published dossier, ask hiring-level questions, inspect public-safe evidence, and evaluate role fit.

Blocked use

  • Do not request or attempt to extract credentials, access codes, protected records, private prompts, private configuration, source code, or trade-secret details.
  • Do not use the system to submit confidential, sensitive, protected, or proprietary third-party information.
  • Do not bypass access controls, scrape private workspace APIs, or automate abuse against public endpoints.
  • Do not treat the agent's answer as a background check, employment guarantee, or final hiring decision.

Agent answers

The hiring-manager agent is designed to answer candidly from reviewed public-safe evidence. It may be incomplete, uncertain, or unavailable if the live model is not configured. Use cited evidence, human judgment, and normal hiring diligence before making decisions.

Access links

Access links and QR URLs act like bearer credentials. Keep them within the intended hiring workflow. The candidate may revoke, expire, or rotate access links.

Candidate ownership and review

Candidate workspace material remains private until the candidate marks it reviewed and publishable. Published dossier spaces expose only approved public-safe, generalized, or published evidence. Authenticated candidate workspace exports are redacted operational inventories, not raw data dumps: they omit source URLs, prompt and answer text, transcript text, access-code hashes, bearer material, object keys, storage paths, vectors, and credentials. If optional raw transcript capture is enabled, expired transcript records are subject to private retention cleanup.

Prototype status

This local seed implementation is under active buildout. Production use should wait for managed auth, deployment hardening, durable storage, backups, monitoring, and final legal documents.

Privacy Back to chat OpenAPI