01Slack data we access
When an administrator connects Slack, Docpipe uses the granted bot permissions for configured capture, Q&A, channel, identity-linking, and approval workflows. We do not read channels that have not been explicitly configured for watched-channel history access.
02What we store
The Slack bot token is stored with additional column-level encryption. Captured messages are stored as organization-scoped inputs with provenance needed for review and deletion workflows.
03Retention and deletion
Disconnecting Slack clears the stored token and Slack user-ID links for the organization. Contact support@docpipe.co for access or deletion requests.
04Payments and merchant of record
When you buy a paid plan, Paddle (Paddle.com Market Ltd) acts as our merchant of record and, as an independent controller, collects and processes the billing information you enter at checkout—card details, billing name and address, and tax information—to take payment, manage your subscription, calculate tax, and issue invoices. Docpipe does not receive or store your full card details. See Paddle's privacy notice at paddle.com/legal/privacy.
05Subprocessors
Docpipe currently relies on providers including Paddle (payments and merchant of record), Supabase, Trigger.dev, OpenAI, PostHog, Vercel, Railway, and Resend to operate relevant parts of the service.
06Your rights
You may request access, deletion, or restriction of personal data by emailing support@docpipe.co. Applicable rights depend on your location and relationship with Docpipe.
07Who we are and how to reach us
Docpipe Labs is the controller for the personal data we collect about users of our product and site. Principal place of business: Apartment 5A, Building 81, Sector B, Askari 11. For privacy questions or to exercise your data rights, email support@docpipe.co.