Privacy Policy
Effective November 9, 2026
This policy explains what Drape collects when you use drape.io, app.drape.io, the Drape GitHub App, the Drape CLI and GitHub Action, and the Drape API (together, the “Service”), and what we do with it. Questions go to group-support@drape.io.
What we collect
- Account details: your email address, name, and a hashed password, or the identity your company’s single sign-on provider sends us.
- GitHub data: when your organization installs the GitHub App, we read what it grants: repository names, pull requests, commits, CI workflow runs and jobs, security alerts, and the GitHub usernames and IDs of the people who author and review that work.
- CI data you upload: test results, coverage reports, and security and lint scan results your pipelines send us. These can include file paths, test names, and test output.
- Source code, for code review only: when code review is on, we check out the pull request in a short-lived, isolated container to review it. The container is destroyed when the review ends. We keep the findings and the code excerpts they quote.
- Billing details: Stripe collects and stores your payment card. We keep your plan, invoices, credit balance, and the count of active users we bill for. We never see or store full card numbers.
- Technical data: IP addresses and request logs, and error reports with personal data removed. We use them to run, secure, and fix the Service.
- Waitlist and contact details: the name, company, and email you give us when you join a waitlist or write to us.
Cookies
We set only the cookies the Service needs to work: to keep you signed in, to complete a single sign-on, to show a one-time notice after an action, and to protect forms against cross-site request forgery. We use no advertising or third-party analytics cookies.
How we use it
We use this data to provide the Service: to analyze your CI, review your code, bill you, send you account and billing emails, keep the Service secure, and fix problems. We don’t sell personal data, we don’t use it for advertising, and we don’t train AI models on your code or CI data.
Who processes it for us
We share data only with the providers that run parts of the Service, and only for that purpose:
- Amazon Web Services: hosting, storage, and email delivery, in the United States.
- Anthropic: the AI models that perform code review. Anthropic does not train its models on the code we send.
- Stripe: payments and invoices.
- Sentry: error reports.
- GitHub: the source of your repository data, under your organization’s own agreement with GitHub.
We may also disclose data when the law requires it, or to a successor if Drape is acquired, under this policy.
Your organization’s data
Your organization controls the repository, CI, and contributor data it connects to Drape, and we process it on the organization’s behalf. If you are a contributor to a repository that uses Drape and want your data removed, contact that organization, or write to us and we will pass the request on.
How long we keep it
We keep your data while your account or organization is active. CI history is kept for the retention period of your plan. When you close your account or ask us to delete your data, we delete it within 30 days. Database backups expire on their own shortly after that. We keep billing records as long as tax law requires.
Your rights
You can ask us for a copy of your personal data, or ask us to correct or delete it, by writing to group-support@drape.io. Depending on where you live (for example in the EU, the UK, or California), you may have further rights, including the right to object to processing and to complain to your data protection authority. We respond to every request within 30 days.
Security
Data is encrypted in transit and at rest. Access is limited to the people who run the Service. Code review runs in isolated containers that can’t reach other customers’ data.
Children
The Service is for businesses and is not directed at anyone under 18.
Changes
If we change this policy, we’ll update the date above. If a change is significant, we’ll also email account owners before it takes effect.