Trust
How dpaperwork handles your data
You are trusting us with client work, so here is the plain version: what we read, what we keep, who can see it, and what we do not have yet. If something here is not clear, write to sam@dpaperwork.in.
A person says yes before anything becomes Canon
The AI can suggest facts, tasks and changes. Nothing becomes part of your Canon, and nothing is sent to a client, until a person on your team accepts it. Every suggestion shows where it came from, and every accepted change is recorded.
Your email
- Read-only. A connected mailbox is asked for read access only. Sending is a separate connection that only the founder can make, and only for sending documents you choose to send.
- Full message text is not stored. We read a message once to write a short summary, then discard the text. Your team sees the summary, the sender, the date and who owns the mailbox. When the AI suggests a task or fact from a message, the suggestion keeps a short quote from it as the reason, so a person can check it before saying yes.
- You decide what is off limits. The mailbox owner can mark a sender, a domain or a single thread as private at any time. Private items are not mapped, and they are not brought back by a later sync.
- Personal mail stays out. Mail from people who are not clients or teammates is skipped. Leave requests and similar admin mail do not become work items.
- Disconnecting works. When you disconnect, we delete the stored tokens and ask Google to revoke the access.
Who can see what
- Access follows each person’s role. A workspace can also be set to scoped access, so people see only the clients they are assigned to.
- Access rules are applied in the database itself, not only in the app screens. Search, Chat and the MCP connection follow the same rules, so a person never gets an answer built from a client they cannot open.
- When someone is removed or their role changes, their access to the Canon changes in the same step.
Protecting stored credentials
- Google access tokens are encrypted before they are saved (AES-256 with authentication).
- Passwords and sign-in are handled by Better Auth. Email verification is required before you can sign in.
- Responses from our server are checked by automated tests so that passwords, tokens and keys are never included in what the app sends back.
AI processing
Chat, drafts and suggestions use Anthropic’s Claude. Only the part of your workspace needed for a question is sent. Under Anthropic’s API terms, that data is not used to train their models. We do not send your data to any other AI provider. Mail text is treated as untrusted: the step that summarises it has no tools and cannot act on instructions hidden inside a message.
Deleting and recovering
- Deleted deals, companies, contacts, tasks, documents and projects go to Trash for 30 days. You can restore them, or delete them forever.
- Removing a client’s data from the Canon can be done completely, including facts that mention them by name. Ask us and we will do it.
- Changes to records leave a trace on the Timeline, and Canon changes keep their history.
Who handles your data
The full list of providers is in our Privacy Policy: Anthropic for AI, Resend for email delivery, Razorpay for payments, Better Auth for sign-in, and Google if you connect Gmail. We do not sell your data.
What we do not have yet
We would rather tell you now than have you find out in a security review.
- No SOC 2 report yet. We have not been audited by a third party.
- No single sign-on (SSO) or SCIM yet. People sign in with email and password.
- No downloadable audit log yet. The trail exists inside the app, but you cannot export it as a file.
- No Slack, Drive or CRM connections yet. Work mail and Calendar are what we read today.
- Early product, one-person company. dpaperwork is run by its founder in India and is in early access.
Ask us anything
Sending a security questionnaire or have a concern about your clients’ data? Email sam@dpaperwork.in and you will get a straight answer from the founder.