e-volv

Compliance playbook

PIIDataFlowAudit

Traces personal data end-to-end through ingress, storage, egress, and logging, flagging any divergence from the published security page.

Monthly, traces personal data end to end — where it enters the system, where it is stored, where it leaves, and how long it is retained — and compares the trace against the claims made on the published security and data-handling page. Any divergence is filed as a ticket.

Identifier
pii-data-flow-audit
Version
1.0.2
Steps
4
Triggers
1
  • pii
  • data-privacy
  • security
  • compliance
  • audit
  • automated

When it runs

Scheduleschedule.monthly
Schedule
Day 1 of each month at 06:00 UTC 0 6 1 * *
Timezone
UTC

The pipeline

The graph below is the one the workflow opens with in the builder — same steps, same layout, drawn on the same canvas. The run playing through it is a simulation; the branches and conditions are real.

React Flow
  1. 01
    Monthly Schedule (1st, 06:00 UTC)trigger

    The event that starts the run.

  2. 02
    Clone Repository ⚠️ SET YOUR REPOgit.clone

    Shallow-clones the repository at the right ref.

  3. 03
    Run PII Data Flow Auditagent.session

    A coordinator delegates to specialist agents.

  4. 04
    File Audit Ticket ⚠️ SET YOUR TICKET INTEGRATIONticket.create

    Opens a ticket on the connected tracker.

The agent

PII Data Flow Auditor

Base type
Senior Developer
Temperature
0.2
Max iterations
50
Tools
4

Filesystem · 2

  • read_fileRead File · read
  • list_dirList Directory · read

Code search · 1

  • code_searchCode Search · read

Status · 1

  • update_statusUpdate Status · write