Data Processing
Last updated: 11 October 2026.
Skippr Data Ltd is a UK company. This page describes how we handle customer data when you use Skippr. Website visitor data is covered by the Privacy Policy.
Roles
| Situation | Your role | Skippr’s role |
|---|---|---|
| Self-hosted Skipprd in your environment | Controller of the data in your sources and destinations | Not the processor of that data. The engine runs where you put it. |
| Skippr consulting / insights delivery | Controller of data in your systems | Processor only for the access you grant during an engagement |
| skippr.io marketing site, contact, and booking | — | Controller of the personal data you send us |
We do not sell customer data. We do not use customer pipeline data to train public models.
Instructions
When we are a processor, we process personal data only on your documented instructions — connecting to the systems you authorise, building the reports and models you asked for, and stopping when the engagement ends, unless UK law requires us to keep a copy.
Security and people
Access to customer systems during an engagement is limited to people who need it to do the work. We use the technical and organisational measures described on Security.
Subprocessors
We use the subprocessors listed on Subprocessors. We will keep that list current. If you need prior notice of a material new subprocessor, say so in the order or email privacy@skippr.io.
International transfers
If a subprocessor is outside the UK, we use a lawful transfer tool (UK IDTA / Addendum, or an adequacy decision) where UK GDPR requires one.
Assistance
We will help with data-subject requests, DPIAs, and breach notice where UK GDPR requires a processor to help — within the product’s design. Self-hosted customers handle those obligations in their own environment.
A signed DPA for an engagement is available on request: privacy@skippr.io.