DocPro is built on memory — the team remembers you so it can do real work across sessions. That only earns trust if you can see exactly what's stored and remove it on demand. This is the straight version: what we do, what we don't, and where the line is. No varnish.
To remember your project and pick up where you left off, DocPro stores the working material of your sessions. All of it lives in our database, scoped to your account:
Your conversation content and team memory are stored in our database so the team can recall them — isolated to your account and protected by access controls, but not individually field-encrypted. We encrypt the things that must never leak: keys, tokens, and credentials. We'd rather tell you exactly where that line sits than imply more than we do.
When you connect a service like GitHub, that token is encrypted at rest and decrypted only for the moment an action runs — never cached between operations.
Right now, the team provisions and runs your infrastructure under DocPro's AWS and Cloudflare accounts — the AWS line in your plan is paid to us, in good faith, for the pipes that run your work. You never hold the keys, and you never get a surprise cloud bill. In July 2026, bring-your-own AWS and Cloudflare API keys arrive: run it all under your own accounts and your own billing, whenever you choose to switch.
We don't auto-expire your data — it stays until you remove it, because the memory is the whole point. A one-click data export isn't built yet; it's on the roadmap. Until then, deletion is fully in your hands through the controls above.
That the team knows your name, your project, and the decision you made last quarter is the product, not a side effect. The deal is simple: it's yours, it's isolated to your account, and you can wipe it whenever you want. If anything here raises a question, ask — a real person answers.
Last reviewed June 2026 · Reflects the platform as it runs today.