Trust & Safety

Data handling

What PIILOT stores, sends to AI, sends to integrations, and keeps locally.

PIILOT processes account data, profile context, workflow content, integration records, notifications, logs, and browser-local workflow state. The product uses this data to create, validate, save, connect, and refine automations.

The Privacy Policy is the controlling legal document. This page is the practical product explanation of where data moves while using PIILOT.

Data flow across PIILOT

flowchart TD
  A[User request] --> B[PIILOT app]
  B --> C[Workflow planner]
  C --> D[AI provider]
  C --> E[Workflow validation]
  E --> F[Saved workflow in database]
  B --> G[Browser local storage]
  B --> H[Composio]
  H --> I[Connected application]
  B --> J[Notifications and logs]

Stored by PIILOT

Account and user records.
Profile and onboarding personalization fields.
Saved workflow JSON, names, summaries, and timestamps.
Integration connection metadata and connected-account identifiers.
Notifications, approval state, and compact operational records.
Rate-limit and session records needed for service protection.

Stored locally in the browser

PIILOT stores workflow drafts and selected workflow state in browser local storage to keep the app responsive and preserve draft state. Local storage remains on the user device until cleared by the user, browser, or app behavior.

Sent to AI systems

PIILOT sends AI systems the task context needed to generate or refine an automation, including user messages, workflow context, profile context, connected-integration context, workflow JSON, and tool results when relevant.