Privacy
Privacy Policy
Last updated: May 4, 2026. This policy explains how Deep Dev handles data for repository intelligence, code scans, Build Lab previews, runtime logs, AI verdicts, reports, billing, and workspace administration.
Data Deep Dev Processes
Deep Dev may process account details, workspace membership, GitHub profile metadata, repository metadata, selected source files, dependency manifests, scan events, findings, build output, preview artifacts, runtime logs, usage records, billing records, support requests, and generated reports.
How Data Is Used
Data is used to provide repository intelligence, security and quality scans, Build Lab execution, preview delivery, runtime log analysis, AI synthesis, scheduled scans, report generation, usage limits, billing operations, support, abuse prevention, service reliability, and product improvement.
Workspace Boundaries
Repositories, scans, logs, reports, subscriptions, billing records, and integration credentials are scoped to the active organization. Deep Dev is designed around tenant boundaries so one customer's workspace data is not intentionally exposed to another customer.
Repository, Build, and Preview Evidence
When you run scans or builds, Deep Dev may temporarily clone selected repositories, install dependencies, inspect files, execute supported commands, store build and scan events, and serve preview artifacts or preview sessions. Build and preview data is used only for the requested workspace workflow and operational diagnostics.
Runtime Logs and Log Sources
Runtime logs may contain stack traces, service names, request metadata, deployment output, and application messages. Customers should avoid sending secrets, payment data, regulated records, or unnecessary personal data through logs unless they have appropriate authorization and controls.
AI Processing
When AI verdicts or code improvement analysis are enabled, relevant repository, scan, build, log, and finding evidence may be sent to the configured AI provider to generate summaries, priorities, and recommendations. AI output is stored with the related scan or report for workspace review.
Sharing and Subprocessors
Deep Dev may share data with infrastructure, database, hosting, authentication, billing, analytics, support, and AI service providers that help operate the platform. These providers are used to deliver the service, not to sell customer repository data.
Security Controls
Deep Dev applies access controls, tenant scoping, encrypted integration secrets where configured, operational monitoring, and least-privilege handling of connected systems. No internet service can be guaranteed fully secure, so suspected security issues should be reported promptly.
Retention and Deletion
Deep Dev keeps workspace records for as long as needed to provide the service, maintain auditability, enforce limits, comply with legal or billing obligations, and support customers. Workspace owners may request deletion or disconnection of repositories, logs, reports, and integrations through product controls or support.
Customer Controls and Rights
Workspace owners can disconnect integrations, select which repositories are imported, refresh repository data from GitHub, manage users, review plan limits, and request support with access, correction, export, or deletion where applicable.
International Processing
Deep Dev and its providers may process data in countries where the platform, infrastructure, support, and AI services operate. Where required, Deep Dev relies on appropriate contractual, technical, and organizational safeguards for cross-border processing.
Security or privacy questions can be sent through the contact page.