How Skillet protects your data: closed ecosystem, isolation, hosting, and certifications

How Skillet keeps your content and activity secure and on-message (the closed knowledge ecosystem, data isolation, hosting and handling, and Skillet’s compliance posture), and how to run a security or procurement review.

In this article

• The closed knowledge ecosystem

• Your content is never used to train external models

• Data isolation

• Hosting, handling, and retention

• Certifications and compliance posture

• Running a security or procurement review

• Content governance and MLR

The closed knowledge ecosystem

Skillet operates as a closed knowledge ecosystem. The AI’s responses are bounded by the content you load into each scenario, not the open internet.

For your security and compliance teams, this means two things: reps practice only against your approved, cleared material, and the AI does not draw on uncontrolled external sources during a conversation.

Your content is never used to train external models

Your content and your team’s activity are not used to train external or third-party models.

Data isolation

Your content and activity are isolated, kept separate from other organizations and constrained to specific teams or products within your own organization. Groups let you control who can see and practice what (see Roles, members, and groups).

Hosting, handling, and retention

Skillet is hosted in the United States, with relevant regional data-transfer agreements in place for customers located elsewhere.

Retention of your content and activity is governed by your agreement with Skillet; for specific retention terms, contact your Skillet representative.

Certifications and compliance posture

Skillet’s security and compliance program includes the following:

Certification status can change. For the current status and supporting documentation, such as reports and our data processing agreement (DPA), contact your Skillet representative.

Running a security or procurement review

If you are evaluating Skillet, your representative can provide current security and compliance documentation to support your review. Some detailed security and architecture material is shared under NDA or through a secure channel rather than in this public Help Center.

Content governance and MLR

For how your approved, MLR-cleared messaging is turned into scenarios and kept on-message, see How scenarios get built and stay on-message. (That article links back here for all certification and data-handling claims, so they stay accurate in one place.)

Related articles

• How scenarios get built and stay on-message: the content & MLR model

• Welcome to Skillet: AI roleplay for life-sciences commercial teams

• Roles, members, and groups: who’s in Skillet

• Glossary of Skillet and life-sciences terms