Privacy Agreement Review
Checks data processing agreements and vendor privacy terms against the standard positions and records the answer.
Every day at 8:00am, list the open data subject requests and email privacy a warning for any deadline inside five days.
The job, and what good looks like.
What breaks: data processing agreements reach the company through procurement and get signed as part of a vendor bundle. Nobody confirms that the subprocessor list, the transfer mechanism, or the deletion promise matches what privacy agreed to, and the review is never written down. Six months later the records of processing cannot explain what we promised a vendor, because nobody recorded the answer. What the workflow does: it reads the signed agreement and lists the subprocessor list, the transfer basis, the breach notice window, the deletion terms, and any audit right, then compares each to the standard positions. Differences come back as a short list with the clause and a suggested wording. The approved answer is written into the records of processing with a date, and each new subprocessor raises a change record that privacy has to acknowledge. What a person still approves: privacy approves the transfer basis and the subprocessor change, and legal approves any clause that departs from the standard wording.
When it is handled
- Every agreement reviewed against standard terms
- Subprocessor changes recorded with a date
- Records of processing updated at signature
- Transfer gaps closed before go-live
Works with tools like
- OneTrust
- TrustArc
- FairNow
- Icertis
Ready-made automations. Pick the one that fits.
Each one is a plain-language document. Run it as it is, or change the timing, the rules and the tools to match your team.
Data Request Deadline Watch
Every day at 8:00am, list the open data subject requests and email privacy a warning for any deadline inside five days.
Every day at 8:00am
Records of Processing Draft
When a data processing agreement is signed, draft the records of processing entry and email it to privacy for approval.
When a data processing agreement is signed
Retention Schedule Check
When a contract states a retention period, compare it with the company schedule and post every mismatch for privacy to resolve.
When a contract states a retention period
Subprocessor Change Review
When a vendor adds a subprocessor, name the new recipient, post the change to privacy, and record the approval date.
When a vendor agreement lists a new subprocessor
You stay in charge.
At every step.
It compares and flags. Every legal call stays yours.
- It never signs or advises
It quotes deviations against your playbook. Accepting, signing and advising stay with a lawyer.
- Every flag shows its source
Each deviation quotes the clause it is about, every step is recorded, and a file change can be put back.
- Confidential stays contained
Each automation reaches only the folders you connect for it, and a local model keeps processing on your machine.
Data Request Deadline Watch
Approve before it sends the email?
Before you download.
- Where does it run?
- On your Mac or Windows computer, in the background. It keeps working after you close its window, and only reaches the folders and apps you connect for each automation.
- How does it connect to our CRM and other tools?
- Through each app's own connection where it offers one, signed in once by you, or by using the app in a browser the way you would. Each automation gets only the connections you give it, and the tools a page names are examples you can swap for your own.
- Does it run when my computer is asleep?
- It keeps your computer awake while a job runs and just before a scheduled one. While the computer is closed or off, nothing runs; when it wakes, it checks the inbox, calendar and other sources it watches for anything that arrived meanwhile.
- How does my team use it?
- Each person who runs automations installs the app. Keep a project in a shared folder, such as Google Drive or a network drive, and teammates can open it and follow every run, while one person owns it and runs it.
- Do I need anyone technical to set it up?
- No. Download the app, add an automation in plain words, and connect only what that job needs. Nothing runs until you switch it on.
Already have tools for this? Here is the difference.
Contract management systems
Storing signed contracts and running approval routes.
Their rules can't read new paper against your playbook or explain a deviation in plain words.
Flowchart automation tools
Moving records between apps.
Clause-level judgment does not fit into branches, and every exception becomes another one to maintain.
AI chat assistants
Summarizing a contract when you paste it in.
Nothing happens until someone asks, and the playbook lives in a chat instead of a document you control.
AUTOMATE.md
Your routine, written in plain words. It runs on its own, follows your rules, handles the exceptions a flowchart can't, and asks you when it matters. The file stays yours, whichever AI model runs it.
Related workflows.
Contract review
Compares incoming clauses against the recorded positions and returns the exceptions as a short list, so a reviewer opens a document with the argument already framed.
1 automation
Compliance tracking
Holds every regulatory obligation with a named owner, a due date, and a current status, so a requirement that went overdue cannot sit unnoticed.
Write your own
Contract Intake Triage
Routes every contract request to the right lawyer with the type, value, and risk already read off the document.
3 automations
Start with one job.
Make it your own.
macOS — coming soon- 1
Get the app
It runs on your computer, next to your files.
- 2
Add the automation
Paste the instructions into the app, or save them as a file next to your work.
- 3
Try it, then turn it on
Run it once and check the result. It only runs on its own once you switch it on.