Jarvisby TheSEO
EN
Language · same pageNLNederlands/jarvis/vertrouwen/verwerkersovereenkomst/ENEnglish (UK)/en/jarvis/trust/data-processing-agreement/ESEspañolnot translated yetWe do not remember your choice and never redirect you automatically.
LEG.J03 · explanation The text that applies is the data processing agreement of TheSEO
JarvisTrustData processing agreement
LEG.J03 · data processing agreement with jarvisexplanation · annex B covers Jarvis

One agreement, with an annex for Jarvis.

The data processing agreement of TheSEO sets out what personal data we process on your behalf. Annex B deals specifically with Jarvis and TheSEO Brain. That text leads and you can read it here in English; this page is explanation.

Read the data processing agreement To the trust centrethree chapters have their own piece of evidence here, three do not
FIG.V01: What the agreement promises, and where the evidence sitsLEG.J03 · promise and evidence

Three chapters have a piece of evidence of their own on this site, three do not

This page puts it in one sentence: the agreement promises measures, the trust centre shows how we demonstrate them. That sentence only becomes usable when you can see, per chapter, where that evidence sits. Here it stands next to every row, including where the answer is that it only sits in the agreement itself.

~/jarvis/trust/data-processing-agreement · annex-B[ok] the document leads
one agreement, two partsmain text and annex
Main textthe arrangements that apply to every product of TheSEO
Annex BJarvis and TheSEO Brain: organisation memory, documents and tasks, agents, connections and support
the chapters you are probably afterevidence on the right
what we use the data for and on whose instructionin the agreement itself
who may get in and how we keep it shutin the agreement itself
what happens when it goes wrong, and how a report runsin the agreement itself
the parties we bring insub-processor list
return, export and erasure at the endoffboarding
checking that we actually do itsecurity evidence
and running through all of itthe logging protocol describes what gets recorded and therefore belongs to more than one of these chapters at once
# the six chapters are in the list below; three of them have a piece of evidence of their own on this site, the other three sit only in the agreement

What you find in annex B

Annex B describes the purpose, which data subjects are involved, which data it holds and how we handle it. Think of organisation memory, documents and tasks, agents, connections and support. Read it together with the main text, because that is where the arrangements common to all products sit.

The chapters you are probably after

  • what we use the data for and on whose instruction;
  • who may get in and how we keep it shut;
  • what happens when it goes wrong, and how a report runs;
  • the parties we bring in, with the full list on sub-processors;
  • return, export and erasure at the end;
  • checking that we actually do it.

Which text wins

Under the order of precedence in the terms, the data processing agreement sits above the product terms and above public explanation such as this page. Where this explanation differs, the agreement applies. One thing we will not fill in on a page: if your organisation sits in the United Kingdom, a transfer of personal data out of the United Kingdom needs the right instrument, and which instrument that is is a question we have put to our lawyer rather than answered ourselves. Ask us before you sign, and you get the answer in writing or you get a plain no.

How the evidence fits

The agreement promises measures; the trust centre shows how we demonstrate them. The security evidence tracks per control which evidence exists, the logging protocol describes what gets recorded and the offboarding describes the route when you leave.

Section · Next stepreachable 24/7
Book a call