Start here
Choose the exact deployment and workflow under review. List data categories, devices, users, providers, destinations, retention expectations, and required approvals. Use a harmless sample to verify behavior.Copy this prompt
Use this in Screenpipe chat or an assistant with the required connections. Replace the brackets with your details. If the assistant lacks access, provide a reviewed excerpt; a prompt alone does not connect it to your history.Check the result
Reconcile the worksheet with settings on an actual pilot device and current vendor materials. Assign an owner to each unanswered question before expanding the workflow.See a worked example
See a worked example
Go deeper: setup choices and edge cases
Go deeper: setup choices and edge cases
Use the privacy data-flow reference as a starting map. Verify the chosen configuration rather than applying a general product statement to every integration. Redaction is a mitigation with coverage limits, not a guarantee that sensitive information cannot appear.Agent and scheduled task capabilities may include file access or external actions depending on their tools and runtime. Review those permissions separately from what the local Screenpipe API allows. Keep contracts, certifications, and organization-specific approvals in the appropriate procurement or security process.