Privacy is part of the operating model.

Every engagement should make clear what data is required, where it moves, who can access it, what providers are involved, what is retained, and what evidence exists afterward.

Ask About a Workflow →Read the Security Model

Position

Collect less. Expose less. Retain deliberately.

Privacy cannot be repaired solely through website language after a system has been designed. It must appear in data classification, workflow design, permissions, provider selection, logging, retention, and deletion behavior.

Practical commitments

What that means in practice.

Collect only what the engagement or workflow requires.
Classify sensitive, confidential, regulated, and customer-controlled data before use.
Prefer local-first or customer-controlled execution where technically and commercially appropriate.
Grant integrations, workflows, agents, and people the least authority required.
Make external model, infrastructure, payment, and service providers explicit.
Define retention and deletion behavior rather than leaving it accidental.
Never expose stored credentials through ordinary agent output.
Keep auditability, approval, incident response, and operational review part of system design.

Shared responsibility

Two parties, clearly divided obligations.

Clients are responsible for disclosing relevant data categories, systems, policies, access restrictions, and unauthorized parallel workflows. ProxyScout is responsible for designing and operating the agreed controls within the covered system.

Questions about data?

Ask how a specific workflow would handle it.

If privacy, retention, or provider exposure is your concern, bring the workflow and we will walk through how it would be designed.

Ask About a Workflow →Read the Security Model