01 / Problem
An SME that wins customers through a website, WhatsApp, a CRM, a newsletter and tracking pixels builds up processing activities and suppliers without noticing. GDPR is usually dealt with once, with a set of templates, and then nobody updates them. When an access request or a breach arrives, there is no record of what data exists, where it is or who is responsible.
02 / Context
Context
The market offers two extremes: generic documents that end up in a drawer, or legal advice that a small SME cannot pay for every quarter. Something in between was needed: a tool that organises day-to-day operations and says clearly when a professional is required.
03 / Solution
How we solved it
RGPD Ops is a server-side workspace, not a form in the browser. Every change goes through SQL functions that only accept tables and columns from a closed list, always filter by the session's workspace and record the change in an audit log that cannot be edited. Access is bought through Stripe and delivered by magic link, with no passwords.
Flow
- 01
Payment through Stripe Checkout and a signed webhook with idempotency in the database
- 02
Access by single-use magic link and an HMAC-signed session
- 03
Writes only through SQL functions with an allowlist of tables and columns
- 04
Optimistic versioning on every record so two tabs do not overwrite each other
- 05
An audit log that rejects edits and stores which field changed, never its value
Workstreams
An ongoing operation, not a document
Each module has statuses and due dates. The tool is meant to be opened every quarter, not filled in once.
- Eight modules on a closed list in both code and SQL
- Tasks seeded once when the workspace is created
- Guided quarterly review
Data minimisation applied to the tool itself
A data protection tool cannot become one more place where personal data piles up. That is why it has no fields for data subjects' names or documents.
- Free text rejects emails, phone numbers and DNI/NIE numbers
- Owners by role, evidence by reference, no file uploads
- No AI on the workspace content
Stated limits
The tool does not decide legal bases or whether a DPIA is needed. When it detects signs of higher risk, it recommends a professional review instead of improvising an answer.
- It is not legal advice or certification
- A free diagnostic first to check whether it fits
04 / Scope
What it does
- Records processing activities and generates a draft Record of Processing Activities (RoPA)
- Organises suppliers, data collection points, rights requests and incidents
- Proposes an action plan with tasks, owners by role and evidence
- Guides a quarterly review and shows the maturity level by area
- Exports each module as CSV and a full copy as JSON
05 / Impact
What it solves
The SME goes from loose documents to a living record: eight modules with their due dates, a task plan with evidence, a guided quarterly review and the option to export everything as CSV and JSON. It also knows what the tool does not do: it gives no legal advice, certifies nothing and does not decide whether a breach must be notified.
Security and confidentiality
- Every private request checks again in the database that the order is paid, active and within its term.
- The workspace ID always comes from the session: someone else's ID returns a 404.
- Logs with closed fields, no email, token, IP or content. Workspaces are purged 90 days after access ends.
06 / Questions
Frequently asked questions
Does it replace a lawyer or a DPO?
No. It organises day-to-day operations and produces drafts, but it does not decide legal bases, does not determine whether a DPIA or a DPO is needed and does not decide whether a breach is notified to the AEPD. When there are signs of risk, it says so and recommends a professional review.
Why does it not use AI?
Because the workspace content describes how a company processes personal data. Sending it to an external model would add one more processor for no reason. The guidance and alerts are written, reviewed rules.
What happens when the year of access ends?
Everything can be exported as JSON and CSV at any time. After access ends, the workspace is kept for 90 days for export and then deleted.