Security

Last updated: 11 October 2026.

Skippr builds the Skipprd engine and delivers data insights. The security-relevant split is simple: self-hosted Skipprd runs in your environment; consulting work uses only the access you grant.

Product facts

• Self-hosted pipelines keep source and destination credentials, and the data they move, in the environment you control.
• We prefer read-only source access to start.
• You own the models, outputs, and reports Skippr helps you build.

More on personal information handling is in the Privacy Policy. Processors we use are listed under Subprocessors.

How to report a vulnerability

Email security@skippr.io. Include enough detail to reproduce the issue. Do not include live customer data.

Please:

• Give us a reasonable window to fix a valid issue before public disclosure.
• Do not use the finding to access other customers’ data, or to disrupt the service.

We will acknowledge the report and tell you when it is fixed or why we do not treat it as a vulnerability.

What we will not publish here

We do not post network diagrams, internal runbooks, or fake badge walls. If your procurement questionnaire needs a named control, email security@skippr.io from a work address and we will answer it.