When a pull request opens on a repo running the DocDrifter Action, the Action sends your PR diff (the changed source and docs hunks) and the PR title to DocDrifter's backend for evaluation. Nothing else in your repository is read or transmitted — not the full checkout, not unrelated files, not commit history beyond the diff itself.
The diff and title are forwarded, for that single evaluation, to DeepSeek (deepseek.com), the third-party LLM provider that judges whether the change needs a docs update. That request is DeepSeek's standard API call — DocDrifter does not fine-tune models on your code, and does not control what DeepSeek itself does with API traffic beyond their own published terms. If you need code that never leaves infrastructure you control, DocDrifter is not the right tool for that repo.
DocDrifter's own database does not store your diff, your code, or the LLM's reasoning text beyond the single response returned to your PR. What is persisted, per request, is limited to:
owner/repo)This is enough to run billing and basic abuse monitoring — it is not enough to reconstruct what your code does.
Signing in to the DocDrifter dashboard uses GitHub OAuth. We store your GitHub login, avatar URL, and numeric GitHub ID to show you which repos you've installed DocDrifter on. We do not request access to your repository contents through this login — the dashboard only reads installation metadata GitHub provides directly.
Private-repo subscriptions are billed through Paddle, who act as merchant of record. DocDrifter never sees or stores your card details — Paddle handles checkout, receipts, and card storage under their own privacy policy. DocDrifter's database stores only your Paddle subscription and customer IDs, needed to check license status and open the customer portal.
Uninstalling the GitHub App or removing the workflow file stops all data flow immediately — there's nothing further to delete on our side beyond the request log described above, which you can ask to have cleared by emailing h.f.ilhan@gmail.com.