What did we actually sign up to?
The obligations are real, they are enforceable, and they are spread across three hundred agreements written by three hundred counterparties. Ragextract reads them once and returns a register, with every entry citing the clause it came from — including the rows where nothing was found.
Free credits on sign-up. No card, no subscription.
| Row | Documents | Breach notification | Audit rights | Sub-processor consent | Data location |
|---|---|---|---|---|---|
| Payments processor DPA.pdf | 24 hours of becoming aware cl. 7.2 | Yes, annual with 30 days’ notice cl. 9.1 | Prior written cl. 5.3 | EEA and UK only Sch. 2, p.1 | |
| Analytics vendor DPA.pdfSCC annex.pdf | 72 hours cl. 6.4 | Report only, no on-site cl. 8.2 | General, with objection right cl. 4.1 | US, SCCs in place SCC annex, p.2 | |
| Facilities services MSA.pdfAmendment 3.pdf | Without undue delay cl. 12.1 | Yes Am. 3, cl. 7 | Not stated | Not stated | |
| Legacy hosting agreement.pdf | Not stated | No cl. 11 | Not stated | Not specified in the agreement cl. 3 |
A register you can be audited on.
A register is only worth keeping if every line can be traced to the document it came from. An entry that says “72 hours” with nothing behind it is a claim somebody will have to re-derive under exactly the conditions where re-deriving is hardest.
Every cell carries the clause it was read from and a confidence score. Corrections are recorded rather than overwritten — type over a cell and the original answer stays underneath, with who changed it and when — so the register carries its own history instead of quietly becoming a different document.
| Document | Breach notification | Audit rights |
|---|---|---|
| Legacy hosting agreement | Not stated | No cl. 11 |
A list of what to check, not a certificate.
This builds a register from what the paperwork says. It does not tell you whether you are compliant with anything, it does not know which obligations apply to you, and a blank cell means the answer was not found rather than that no obligation exists. Those distinctions are the difference between a useful register and a dangerous one.
What it changes is the starting point. Three hundred agreements become a table with forty rows worth opening, instead of a project nobody has time to begin — legal reads the same documents for what was agreed, and this table asks what has to be done about it now.
Bundle each agreement with its amendments and annexes. An audit right added by an amendment, or a transfer annex signed a year later, is exactly the entry a register built on the original document gets wrong.
Where it fits.
A row is whatever the obligation attaches to — usually an agreement, sometimes a policy or a certificate.
| The work | What a row is | Start from |
|---|---|---|
| Obligations register | An agreement, with its amendments | |
| Data-processing review | A DPA, with its transfer annexes | |
| Policy and certificate checks | A policy or certificate | |
| Incident and audit response | An agreement in scope of the incident |
Every column on this page is one you write — no compliance preset ships in the app, and the register is a set of questions only you know the shape of. The closest starting point is contract review, which quotes the Legal & Procurement preset verbatim over the same documents, and columns covers how to write a prompt that returns a clause rather than a paraphrase.
Reading is charged once.
The obligation nobody thought to track until the audit asked about it costs one column, not another pass over three hundred agreements. That is the property that makes a register maintainable rather than a thing that was accurate in March.
| A 300-agreement register | Volume | Cost |
|---|---|---|
| 300 agreements, 20 pages each — read once | 6,000 pages | 6,000 credits |
| 4 obligation questions asked of all 300 | 1,200 cells | 1,200 credits |
| A fifth obligation, added after an audit | 300 cells | 300 credits |
Start with the obligation you were last asked about.
Upload five agreements you know the answer for, write that one column, and read every citation. If the table agrees with you on five, it is worth pointing at the other two hundred and ninety-five — and if it does not, you have learned that in an afternoon.
Nothing on this page is legal, regulatory or compliance advice, and a table built this way is not evidence of compliance with anything.