Security and data handling
This page gives a concise view of how Skene connects to your repositories and how it uses that data while you evaluate the product.
Repository access and data handling
Skene connects to your code via your Git provider. You stay in control of which repositories are visible.
Read-only access
Repository content is accessed using credentials scoped to repository contents and metadata, and Skene only performs read operations on your code.
You control access
You choose which repositories Skene can see when you connect it, and you can remove that access at any time from your Git provider.
Purpose-limited use
Skene uses repository data to understand your product and help you design growth loops; it is not intended for unrelated use cases.
No tracking scripts required
Skene is designed to work from your code, APIs, configurations, and docs, rather than requiring additional tracking scripts to start an evaluation.
Security at a glance
Need a deeper security review?
If your security, legal, or procurement teams need more detail than this page provides, get in touch and we can walk through the current controls and answer specific questions based on your evaluation setup.
Ready to try Skene?
Start with a free trial and connect your first repository.