What we collect, and what we do with it.

What we collect

• Account details. Your GitHub user ID and login, and your email address if GitHub provides one with your profile. We use these to identify your account and to contact you about the service.
• GitHub App installation. The installation identifier and the account it belongs to, so we know which repositories you have granted access to.
• Project configuration. The repositories you select, the documentation branch, your application URL, an optional login URL and test-account username, and an optional test-account password stored encrypted.
• Run data. The pull request analyzed, the run’s status and timings, the generated Markdown draft, the impact and summary reports, the screenshots captured, a trace of the agent’s steps, and token usage totals.
• Billing records. Your Stripe customer and subscription identifiers, the plan you are on, its status, and the current billing period. Card details are entered on Stripe’s own pages and never reach us.
• Operational logs. Ordinary server logs used to keep the service running and to investigate faults.
• Usage analytics. The pages visited and standard browser and device information, used to understand how the product is used and improve it. We collect this through PostHog.

What we do not do

• We do not use advertising tools, automatic click capture, or session recording.
• We do not sell or rent your data, and we do not share it for advertising.
• We do not use your repository content, documentation, or screenshots to train models.
• We do not write to your repositories, and we do not publish anything on your behalf.

How your content is used

When you start a run, DocsUpdater reads the pull request and the documentation files in the repositories you selected, and opens the application URL you configured. That content is analyzed automatically in order to produce the draft, the reports, and the screenshots you receive. Producing a result involves third-party model infrastructure operating under a commercial agreement.

The result is stored against your account and served only to you. It is never used to answer another customer’s run.

Cookies

Browsing this site uses PostHog analytics stored in local storage, not analytics cookies. Signing in with GitHub sets the cookies needed to complete that sign-in and to keep you signed in afterwards. They are required for the application to work and are not used for advertising.

Retention and deletion

Runs and their artifacts are kept for as long as your account exists, so that earlier results remain available to you. There is no automatic deletion and no self-serve delete yet.

Email support@docsupdater.com to have a project’s history deleted, or your account and all data belonging to it. We will confirm once it is done. You can also revoke the DocsUpdater GitHub App’s access at any time from your GitHub settings, which stops any further reads immediately.

Questions

Write to support@docsupdater.com. If we change this policy in a way that affects what we collect or how long we keep it, we will update the date above and note the change on this page.

See also: Security · Terms