Data protection

Every outbound path as configured right now (model providers, mail, team chat, connectors, speech, the web, the platform, updates, analytics), each with its destination, whether personal data can travel on it and whether the privacy shield covers it; and the technical and organisational measures with whether each is in place.

curl "$SANDBOX/compliance" \
  -H "x-intentic-control: $INTENTIC_TOKEN"

import { sandbox } from "@intentic/sandbox-client";

const result = await sandbox.compliance.report();

The record of processing activities entry, the data protection impact assessment draft, or the list of technical and organisational measures, in Polish or English, as Markdown or a Word document. What the sandbox knows is filled in; what only the office can say is left as a marked blank.

curl "$SANDBOX/compliance/document?kind=ropa" \
  -H "x-intentic-control: $INTENTIC_TOKEN"

import { sandbox } from "@intentic/sandbox-client";

const result = await sandbox.compliance.document({
  "kind": "ropa"
});

Each stricter setting the preset proposes, with the value this sandbox has now beside it. Reading it changes nothing.

curl "$SANDBOX/compliance/preset" \
  -H "x-intentic-control: $INTENTIC_TOKEN"

import { sandbox } from "@intentic/sandbox-client";

const result = await sandbox.compliance.preset();

Applies only the items named, each to its proposed value, and leaves everything else as it is. An item already at its value, or one this sandbox cannot take (a name model that is not installed), is skipped and said so.

curl -X POST "$SANDBOX/compliance/preset" \
  -H "x-intentic-control: $INTENTIC_TOKEN" \
  -H "content-type: application/json" \
  -d '{"items":["…","…"]}'

import { sandbox } from "@intentic/sandbox-client";

const result = await sandbox.compliance.applyPreset({
  "items": [
    "…",
    "…"
  ]
});