Privacy & security

Your source code is yours. peek is private by default, single-tenant, and never trains a model on your code — or on the understanding it builds from it.

Scoped access

Private repos connect through the GitHub App, and you grant access only to the specific repositories you choose — nothing more. peek reads just the repos you've explicitly added. Public repos are added without the App, so they involve no special access to your account.

What peek stores

Indexing produces a hierarchical understanding of your codebase — file, folder, and repository-level summaries. That understanding is what lets peek answer questions without re-reading everything each time, and it is stored against your account in our database. A working copy of your repo is kept on disk only so peek can refresh that understanding when you push; it is never pooled or shared across accounts.

How your code is processed

To build that understanding and answer your questions, peek sends the relevant code to the large-language-model providers it runs on. peek does not train any model on your code or summaries, and only the code a given task needs is sent. We're glad to share the current list of model and infrastructure providers on request.

Single-tenant by design

Your code is cloned into an isolated working copy and used for one thing: building your understanding of the repo and answering your questions. It isn't mixed with other accounts, and it never becomes training data.

Encryption & infrastructure

Traffic to peek is served over TLS. Your summaries live in a managed Postgres database and the service runs on managed cloud infrastructure; access to production data is limited to what's needed to operate the service.

You stay in control

• Remove a repository at any time to stop indexing it.
• Revoke the GitHub App from your GitHub settings to cut off access entirely.
• Want your data gone? Email hello@codepeekr.dev and we'll delete your summaries and working copies.

Reporting a security issue

Found a vulnerability? Email hello@codepeekr.dev with the details and we'll respond quickly. Please give us a chance to fix it before disclosing publicly.

Have a security or compliance question that isn't covered here? Reply to any of our emails — humans answer.