1. Local data
DPAI stores session state, configuration, and a local audit log in a config directory on
your machine (by default ~/.dpai, or a rebranded equivalent for whitelabelled
builds). This data does not leave your machine unless a tool you invoke explicitly sends
it somewhere — for example, a bash command you asked the agent to run.
2. Data sent to the gateway
Prompts, tool outputs, and file contents you include in a session are sent to the Dual Path Intelligence gateway so it can route them to the model you selected. The gateway applies your configured access policy and budget rules but does not inspect content for purposes beyond routing, billing, and abuse prevention.
3. Telegram integration
If you pair a Telegram bot for remote control, messages you send are relayed through Telegram's infrastructure to reach your local DPAI session, and voice notes are transcribed through the gateway's speech-to-text endpoint. Telegram's own privacy policy governs data handled by Telegram itself.
4. No sale of data
We do not sell session content or prompts to third parties. Aggregate, de-identified usage metrics may be used to improve the gateway's reliability and routing.
5. Retention & deletion
Local data persists until you delete your config directory or a configured retention window expires it automatically — see the Compliance Guide for how to configure enforced retention in regulated deployments. To request deletion of data held at the gateway level, contact us using the details below.
6. Contact
Privacy questions or deletion requests can be sent to privacy@dpai.sh.