How Skill Coach handles training data.
Last updated June 17, 2026. Skill Coach is in private beta and keeps data collection narrow while pilot workflows are reviewed by human operators.
Information we collect
Skill Coach may collect contact details, beta request answers, learner goals, training submissions, proof artifacts, operator notes, support messages, and basic analytics needed to operate the product.
How we use it
We use this information to provide coaching workflows, manage pilot access, review learner progress, improve templates, respond to support requests, and protect the product from abuse.
What not to submit
Do not submit passwords, payment card numbers, regulated medical or legal records, private customer records, or confidential shop information that is not required for training review.
Retention and requests
Private beta records are retained only as needed for pilot operation, support, audit, and safety review. You can request access, correction, export, deletion review, or consent withdrawal by emailing support@skillcoachhq.com.
Subprocessors and service providers
During beta, Skill Coach may rely on hosting, analytics, email, payment, monitoring, and AI infrastructure providers to run the service. Access is limited to what is needed for operations, support, abuse prevention, billing readiness, and reliability checks.
Data processing agreement status
This is the current sub-processor disclosure and data processing agreement status. During private beta, Skill Coach does not offer a separate enterprise data processing agreement. If a paid production customer needs a DPA, subprocessor list, or contractual data-processing terms, that request must be reviewed before production rollout.
Third-party services
Skill Coach may use hosting, analytics, email, payment, and AI infrastructure providers. Production billing remains gated until operational readiness checks are complete.
Contact
Privacy and support requests go to support@skillcoachhq.com.
Data processing notes
Skill Coach does not need full customer records, repair orders, passwords, or payment card details to coach a learner. The safest pilot examples are rewritten samples, checklist answers, anonymized scripts, and short training artifacts that show the skill without exposing unnecessary customer or employee data.
Operators are expected to review submissions before using them as examples outside the workspace. If a pilot later moves to paid production use, the privacy policy and data processing disclosures will be reviewed again alongside billing, monitoring, backup, and support readiness.