Host product
The person authorizes an action in Jira or Confluence.
Follow data from its source to deletion.
The Data packet shows the expected full flow: input, processing, possible storage, output, retention, and deletion. The app concepts use no remote product backend; both public forms remain closed until their privacy information is complete.
Two distinct scopes
Demos use fictional browser data. A form can write to Prisma only after server opt-in, consent, and publication of the controller, rights contact, and retention.
A readable flow without an opaque compliance diagram.
App function
The minimum data is read and transformed for the task.
Possible storage
Necessity, region, and retention must be documented.
Output and deletion
The result returns to the flow; deletion remains controllable.
The inventory required before publication.
Every category must state its purpose, location, duration, and deletion mechanism. ‘We take security seriously’ fills no field.
| Category | Example | Purpose | Current state |
|---|---|---|---|
| Host context | Authorized issue, project, or page | Required for the function | No active remote storage |
| App configuration | Criteria, preferences, relationships | Make the experience persistent | Model still to define |
| Technical logs | Error, correlation, version | Diagnostics and security | Retention still to define |
| Sensitive content | Minimize and classify | Never collected by default | Processing requires justification |
| Evaluation brief | Name, email, company, and context | Process a voluntary request | Writes blocked by default · conditional activation |
| Editorial updates | Email and consent evidence | Prepare future field-note delivery | Writes blocked by default · no active delivery |
Data without an explicit purpose does not enter the app.
Now connect the data flow to application scopes and documented configuration steps.