Private by default
Every new project is strictly private: only you and the people you share it with can view or edit its contents. Projects appear in the public Library only if the owner manually makes them public, and they can be switched back to private at any time. See Share & Roles.
Passwordless sign-in
Pacpio uses one-time codes sent to your email. We don't store passwords, so there is no password to guess, reuse, or leak. Each code works once, expires after a few minutes, and allows only a few attempts.
Assistant access & safeguards
When you connect an assistant, you approve it on a Pacpio sign-in screen. It gets access only to the projects you can open — yours and the ones shared with you — and nothing else.
- On-demand file reads: Assistants retrieve file content only when relevant to your current request.
- Full version history: Every change creates a new version. You can see what changed and restore an earlier version at any time. See Versions & History.
- Confirmations: Pacpio tells assistants to ask for your explicit approval before sharing a project, revoking access, restoring a version, or moving or deleting a folder. Tools that delete or move files are marked so your assistant asks before running them.
- Questions about tables: Your assistant's questions about a table run in a separate sandbox. It can only read the tables of that one project, and it has no network access. Every change to rows goes through the same checks and version history as any other save.
- Granular controls: Switch any assistant to view-only mode or disconnect it entirely with immediate effect.
What Pacpio can and cannot access
Pacpio is a storage layer for your projects:
- What we store: Your project files, their version history, and records of which tools your assistants used. For quick answers about tables, Pacpio also keeps a prepared copy of them. It can always be rebuilt from your files.
- What we never see: Your chat conversations outside the requests your assistant sends to Pacpio, or your AI provider API keys. Pacpio never runs or hosts your model.
- Feedback from assistants: If a tool fails or gets in the way, your assistant may send us a short note about it to help us fix the problem, and it tells you in the chat when it does. These notes say only what did not work: never your request or your file contents.
Prompt injection protection
Projects copied from the Library might contain text written by someone else. Pacpio explicitly instructs connected assistants to treat stored file contents as data, not as instructions. This helps keep text inside a file from overriding what you asked your assistant to do.
Secret scanning
To protect your accounts, Pacpio rejects files that contain private keys or API keys of well-known services (such as OpenAI, Anthropic, AWS, GitHub, and Stripe), and files meant for secrets, like .env. Store credentials in a password manager or your assistant's own settings, not in project files.
Privacy & vulnerability reports
For details on data retention periods and data removal requests, read our Privacy Policy.
If you discover a security vulnerability or bug, please report it responsibly via our contact page.