Money. Identity. Technology.
Follow the money. Find the decision.
Classification supplier with distinct ordinary-data and feedback terms
Sightengine is a content-analysis service owned and operated by Kozelo SAS, a French company identified in its terms. Its classifiers can supply scores to Checkstep, where a customer applies its own moderation policy.
The coauthored integration guide describes Sightengine scores entering Checkstep workflows. Ordinary subscriber data uses a processor arrangement. Voluntary Feedback API submissions instead carry a licence for training, testing and development, subject to necessary rights and consents; the data-processing addendum assigns Sightengine a controller role for feedback and a separate retention exception subject to law and policy. The published terms establish permissions, not proof of particular media retention, training or automatic forwarding of routine scans into feedback.
Sightengine (Kozelo SAS) → Voluntary Sightengine feedback data
Effective interval unknown; public record observed 9 September 2026.
Terms 9.3 raw-media licence covers voluntary Feedback API submissions for training/testing/development with necessary rights/consents. General-suggestion sentence is distinct; its perpetual/irrevocable adjectives are not imported. Routine scanning or Checkstep forwarding not established.
Sightengine (Kozelo SAS) → Voluntary Sightengine feedback data
Effective interval unknown; public record observed 9 September 2026.
DPA2.3 assigns controller role for Feedback Data with lawful basis/privacy law;4.4 permits perpetual retention subject to policy/law and exempts automatic return/deletion. Does not erase privacy rights or prove actual retention/training.
Customer platform / subscriber role → Sightengine (Kozelo SAS)
Effective interval unknown; public record observed 9 September 2026.
Ordinary subscriber-data uses processor arrangement, requiring controller authority if subscriber itself processor. Correction/deletion assistance and law limits differ from feedback exception. Particular execution unknown.
Sightengine (Kozelo SAS) → Checkstep
Currentguide observed 9 September 2026; historical version unknown. PUBLICpublished 26 March 2026 citesguideas 2025.
Coauthored guide describes scores entering Checkstep workflow; PUBLIC calls example signal sharing. Not shared offender list, universal no-external-processing guarantee or observed customer deployment.
The advisory route into a government-funded safety-technology programme ↗
Checkstep / Sightengine: classification, enforcement and reuse are separate interfaces ↗
Sightengine (Kozelo SAS) → describes supplying classification outputs → Checkstep
Currentguide observed 9 September 2026; historical version unknown. PUBLICpublished 26 March 2026 citesguideas 2025.
Coauthored guide describes scores entering Checkstep workflow; PUBLIC calls example signal sharing. Not shared offender list, universal no-external-processing guarantee or observed customer deployment.
Sightengine (Kozelo SAS) → may use voluntarily submitted media for model work → Voluntary Sightengine feedback data
Effective interval unknown; public record observed 9 September 2026.
Terms 9.3 raw-media licence covers voluntary Feedback API submissions for training/testing/development with necessary rights/consents. General-suggestion sentence is distinct; its perpetual/irrevocable adjectives are not imported. Routine scanning or Checkstep forwarding not established.
Sightengine (Kozelo SAS) → acts as independent controller under feedback exception → Voluntary Sightengine feedback data
Effective interval unknown; public record observed 9 September 2026.
DPA2.3 assigns controller role for Feedback Data with lawful basis/privacy law;4.4 permits perpetual retention subject to policy/law and exempts automatic return/deletion. Does not erase privacy rights or prove actual retention/training.
Customer platform / subscriber role → instructs ordinary processing under published DPA → Sightengine (Kozelo SAS)
Effective interval unknown; public record observed 9 September 2026.
Ordinary subscriber-data uses processor arrangement, requiring controller authority if subscriber itself processor. Correction/deletion assistance and law limits differ from feedback exception. Particular execution unknown.