CounselStreamDocs

Docs

For engineering

Your privacy team needs one file from you. This page is everything you need to produce it.

  • One JSON or CSV file
  • No account or key needed
  • Contract version 0.4

1Choose the format

JSON: one object with four keys. CSV: one row for each record, with schema_version, producer and snapshot_at as columns. Each file can be up to 4 MB.

{
  "schema_version": "0.4",
  "producer": "<the name of your system>",
  "snapshot_at": "2026-11-02T08:00:00Z",
  "records": [
    { "platform_id": "...", "name": "...", "kind": "agent" }
  ]
}

2Fill every column

Every cell holds a value, or n/a, or undeclared. An empty cell is not an answer. The Data Dictionary gives the format and the values for each column.

3Give every row a stable identifier

platform_id is your own identifier for the row. It is the same in every export for the life of the row and is never reused. A record without one is turned away. It is the only identifier you keep for CounselStream.

4Name the rows that start or use another row

In starters, write trigger <platform_id> for each trigger that starts the row, and step of, delegated by or tool of with the platform_id of each row that uses it. Always the identifier, never the name.

5Send the file to your Privacy Program Manager

They upload it. If a record cannot be read or a row cannot be placed, they get the reason in plain words and pass it to you.

6Send a new export when systems change

Rows are matched on platform_id, so a renamed system is still the same system.

These pages describe a data contract: what to send and how it is read as data. They do not describe how any legal determination is reached. Determinations are made by privacy counsel inside CounselStream.