A transparent privacy page for the SKILLSETRA evidence workflow.
SKILLSETRA is designed to make the boundary between learner-provided information, observed evidence and AI interpretation visible. This notice explains the current application behavior; a production operator should replace the deployment-specific placeholders with its own legal and retention details.
What SKILLSETRA stores
Depending on the deployment, the workspace can contain a name, target role, goal, assessment attempts, challenge/project activity, learning progress, evidence records, self-declared claims, AI Coach history, settings and contact messages. Demo workspaces use a generated session identifier rather than an account password.
Why it is used
The information is used to run the competency workflow: target a role, assess, identify gaps, learn, create evidence, practice, and retest. It is not intended to silently infer a hiring decision or sell a learner profile.
AI processing
Some AI features process prompts and the content you submit in your browser through the configured AI provider. Evidence-review details are sent only after you enable the optional evidence-review consent. AI-generated assessment questions are labelled as practice when they are generated in the browser.
AI limitations
AI output is untrusted assistance. It can be wrong, incomplete or manipulated by input. SKILLSETRA keeps AI interpretation separate from recorded evidence and does not treat an AI opinion as independent proof of mastery.
Repositories and links
The current GitHub Intelligence workflow analyzes a public repository URL supplied by the user; it does not require a GitHub account connection. Repository content is treated as untrusted external data and AI interpretation is not allowed to become an independent evidence claim.
Files and resumes
Resume extraction is processed in memory by the extraction endpoint and is not intentionally persisted there. A later AI analysis request can send extracted text to the selected provider only after the applicable consent step. Do not upload secrets, passwords, tokens or confidential material that the deployment is not approved to process.
Demo versus production
The supplied demo build stores workspace snapshots in its configured local/demo store and may expire them after the configured session lifetime. A production deployment can use different storage and retention controls. Operators should publish their actual legal entity, retention period, deletion process, support contact and applicable jurisdiction before public launch.
Your controls
You can change the target role, application settings and evidence workflow from inside the product. Reselecting a role can intentionally start a fresh evidence journey. Production data-access or deletion requests should be sent to the operator responsible for that deployment.
Security
The application uses allowlisted URL validation, server-side answer keys for server-generated assessments, explicit AI provider selection, browser-safe rendering of AI responses and security headers. No application can guarantee absolute security; protect credentials and do not place secrets in evidence or chat prompts.
Children and sensitive data
Do not submit unnecessary sensitive personal information. A deployment intended for children, schools or regulated environments should complete its own privacy, security, accessibility and legal review.
External providers
AI service, GitHub and other external services have their own terms and privacy policies. Using a provider through SKILLSETRA does not replace those policies.
Changes
This notice describes the supplied application build and can change as features, storage, providers or integrations change. The deployment operator is responsible for keeping its published policy accurate.
