Data handling
What dlogs reads from your code host, what leaves it, and how to get it deleted.
What dlogs connects to
- GitHub, through a GitHub App you install on the repositories you choose, or Bitbucket Cloud, through OAuth.
- dlogs looks for decisions only in the repositories you select, in up to 200 merged pull requests per repository from the last 6 months. This reads. It never writes to your code host.
- Connecting Bitbucket creates one workspace-level webhook, so dlogs receives pull-request events for every repository in that workspace. Event bodies are stripped of secrets and discarded once processed.
- dlogs does not comment on pull requests or post build statuses unless a workspace admin turns that on. It never blocks a merge.
What is sent to OpenAI
When dlogs looks for decisions in pull request history: the title, the description, the file paths, the kind of change, and short snippets of changed lines. No whole files.
To decide whether a pull request contains a decision, and to write the proposal.
Only when a person clicks Extract from PR, or proposes a replacement for a decision whose code has changed: a redacted, shortened diff of that one pull request.
To fill in a proposal for a person to review.
What a coding agent proposes while it works: a title, the reasoning, the file paths and the repository name.
To queue a proposal for review and fill in missing fields.
The text of decisions your team has approved, and the text an agent or a person searches for.
To make search find decisions by meaning, not only by keyword.
In everything sent to OpenAI, secrets are redacted first: keys, tokens, passwords and credentials inside connection strings. The contents of .env, key, certificate, tfvars and credential files are never sent; only their paths are. OpenAI's API data-use policy applies to the text it receives.
What dlogs stores
- Approved decisions and proposals waiting for review.
- The email addresses of the people in your workspace.
- Usage records, including the repository name and pull request number an event referred to, for up to 90 days.
- A failed delivery from your code host, for up to 7 days, so it can be retried.
Each workspace is isolated from every other at the database level. Bitbucket tokens are encrypted at rest.
Ownership and deletion
- You own the decisions created from your repositories and people.
- A decision is never edited or deleted in place. A new decision replaces it, and the old one stays readable.
- Disconnecting Bitbucket removes the webhook. You can stop at any time.
- On request, we delete your whole workspace and send a receipt with the number of rows removed from each table. Database backups age out after that. Email hello@dlogs.app.