# Hosted security and data handling A security reviewer's guide to Hosted at repowise.dev, covering what happens to your source code, what is kept, when a model sees it, and how data is deleted. This page covers the hosted platform at [repowise.dev](https://repowise.dev): how it handles your code and account data. For self-hosted Repowise, where code never leaves your machines, see [Security and data handling (self-hosted)](https://docs.repowise.dev/security). The scanning product that runs on Hosted is the [Security suite](https://docs.repowise.dev/hosted/security), and the free scan in the open-source engine is [Security signals](https://docs.repowise.dev/intelligence/security-signals). ## Where Hosted runs Hosted is a managed service that Repowise operates on third-party cloud providers. The [privacy policy](https://repowise.dev/legal/privacy) lists each category of sub-processor and what it is used for. The named list is available on request at [hello@repowise.dev](mailto:hello@repowise.dev). If your code cannot leave your own network, Hosted is the wrong fit. Run [self-hosted Repowise](https://docs.repowise.dev/security) on your machines, or talk to us about a [customer-managed deployment](https://docs.repowise.dev/enterprise). ## What happens to your source code 1. Indexing runs in an isolated, short-lived container. Your repository is cloned into a temporary directory inside it. 2. The pipeline parses the code and reads git history to build the index. 3. The clone is deleted at the end of every run, including runs that fail. Git credentials are passed to the clone in a way that keeps them out of logs. Private repositories are read through a read-only GitHub App install, or through the GitLab.com account you connect. Repowise reads GitLab code and never changes it; with the `api` scope it adds one push hook to each project you turn auto-sync on for. ## What is stored after indexing Raw source is not kept. Only data derived from it persists: - Documentation pages - The dependency graph - Git metadata such as hotspots and ownership - Architectural decisions - Code-health findings - Embeddings for semantic search Private repository data is isolated per account with row-level access controls tied to the signed-in user. Large artifacts for public repositories go to a separate public artifact store, and private repository data is never written there. For secret detection, only a fingerprint and a redacted preview of each finding are stored, never the secret value. ## When a model sees your code The dependency graph, git analysis, code health, dead code and security scanning do not call a model. Model features, such as AI-written documentation, chat and answers, call Anthropic, OpenAI or Google Gemini models through Repowise's business API accounts. Claude Haiku is the default, and you can pick another supported model. AI pull request review runs on Anthropic or OpenAI models, Claude Haiku by default. Embeddings for semantic search come from an OpenAI or Gemini embedding model. When you use these features, code excerpts and context derived from your repository are sent to that provider to produce the result. Two other outbound paths carry no code: - Dependency vulnerability matching sends package URLs (purls) to [OSV.dev](https://osv.dev), never source code. - Security alert webhooks and emails carry metadata only: rule ids, file paths and counts. Never code snippets or secret values. ## Access control - Sign-in is with GitHub, Google, or email and password. - Indexes of public repositories are public. Access to a private repository's index is gated on the signed-in user's ownership of it. Workspaces and [Teams](https://docs.repowise.dev/hosted/teams) add explicit membership, and a team has owner, admin and member roles. - API keys for the [hosted MCP endpoint](https://docs.repowise.dev/hosted/connecting-ide) are shown to you once at creation. Only a one-way hash is stored. - On the Teams plan, security actions such as viewing findings, exports and status changes are recorded in an [insert-only audit trail](https://docs.repowise.dev/hosted/security#audit-trail-teams). It covers the security surface only and is not a full account audit log. ## Retention and deletion Indexed data is kept while your account is active. You can delete a repository, a workspace or the whole account from **Settings**. Removing a repository unlinks it from your account. Once no account links it, its index, stored artifacts, embeddings and chats are deleted right away. Account deletion locks the account and starts a 7-day grace period, during which you can cancel. A daily job then hard-deletes the account, and the records tied to it are deleted with it. A few records are kept with the link to you removed instead: billing ledger entries, public documentation pages, feedback you sent and product analytics events. The [privacy policy](https://repowise.dev/legal/privacy) states that deleted data is purged from backups within 90 days. Usage telemetry events are kept for about 90 days and product analytics events for about 180 days, then removed by a scheduled job. ## Sub-processors The [privacy policy](https://repowise.dev/legal/privacy) lists each category of sub-processor and what it is used for. For the named list, email [hello@repowise.dev](mailto:hello@repowise.dev). ## Certifications and single sign-on - **Security reviews.** Hosted is reviewed directly against your questionnaire rather than a SOC 2 or ISO 27001 report: send it to [security@repowise.dev](mailto:security@repowise.dev). Teams whose policy requires their own audited boundary run [Enterprise](https://docs.repowise.dev/enterprise#why-your-security-team-can-say-yes), which sits entirely inside their perimeter, so Repowise never handles their code or data and their own certifications cover it. The compliance reports in the Security suite are control-coverage signals for your code, not a certification of Repowise. - **Single sign-on.** SAML / OIDC single sign-on and SCIM provisioning are set up with your identity provider as part of an [Enterprise deployment](https://docs.repowise.dev/enterprise#what-the-commercial-licence-adds), scoped during the pilot. ## Reporting a vulnerability Email [security@repowise.dev](mailto:security@repowise.dev) with reproduction steps. ## Security review Bring your questionnaire and a representative repository to a call. [Book a security review](https://cal.com/repowise-demo/30min?overlayCalendar=true)