Your website account
When you sign in with GitHub, I store your GitHub user id, login, public email if available, contact email, creation time and last sign-in time. Cloudflare stores the account, and a signed, secure cookie keeps you signed in for up to seven days. GitHub handles authentication. I do not request repository access. Use Support for account data questions or deletion requests.
The site uses Cloudflare Web Analytics, which sets no cookies and does not identify you.
If you opt in, I use your contact email or public GitHub email to send Drover updates a few times a year, and you can unsubscribe any time.
What stays on your machine
Drover stores repository configuration, workspace settings and the driver’s per-ticket working records locally. These records can contain requests, plans, session output and results. Tracker secrets are stored in the system keyring.
The desktop also keeps preferences and feedback history in per-user webview storage. Sent history retains up to 50 reports and omits optional plan and last-session text. Reports waiting offline keep the exact report bytes until a receipt is stored.
What leaves your machine
Drover has no telemetry. No feedback report is sent until you press Send. If that send cannot reach the intake and the report is saved offline, the app tries it again on a later launch. Sent report references are used to check their state when Your reports is open.
Your configured coding tools and trackers communicate with their providers to do the work you request. Their services have their own data policies. Local working records do not mean model use is offline.
What a feedback report contains
Feedback is sent from the app while signed in. I store your account id privately with the report reference, along with the email you enter only if you turn on Contact me. A report carries type, description, send time and optional contact email. Ticket reports include ticket context and available version, operating system, attempt outcome and timing diagnostics. Plan and latest session message are included only if you choose them.
Ticket descriptions, code changes and session transcripts are not automatically sent. Recognizable credentials are redacted before the preview, but review the description and optional text yourself before sending.
Questions about a report
Keep its receipt reference and contact me through support. Do not post the report’s private contents in a public issue.