Security
Know what each connection can reach.
Skene security covers what Skene can reach in engineering’s code and the sources growth reports from. Skene OSS runs on your engineers’ machines and reads the inputs they choose. Skene Cloud uses your connected sources and keeps review context for both teams.
Chosen inputs and local output
The code and optional schema engineers choose are read for analysis. The customer journey file is written locally.
Provider credentials may be saved in local configuration.Analysis context
A remote model receives analysis context when engineers select one. A supported local provider keeps model processing local.
Local execution alone does not mean local model processing.Shared context and review history
Cloud uses connected sources and retains artifacts and review context for the team.
Source grants, model processing and event storage are separate boundaries.GitHub permissions.
Engineering approves all or selected repositories during installation. A workspace owner links the repository. It needs no personal access token.
| Permission | Access | Purpose |
|---|---|---|
| Contents | Read & write | Read source and context files; propose updates through pull requests. |
| Pull requests | Read & write | Read changes, post reviews and open fix pull requests. |
| Issues | Read & write | Respond to /skene fix comments. |
| Metadata | Read | List repositories accessible to the installation. |
Skene never pushes directly to your default branch. Your team reviews proposed changes. Uninstall the GitHub App in GitHub to revoke repository permissions.
Read the GitHub contractSchema access and optional writes.
| Connection | Purpose | Boundary |
|---|---|---|
| Read-only OAuth | Schema and authorized table queries. | Read-only queries; no database writes. Available rows and counts depend on the connected role. |
| Optional read-write | Supported trigger deployment and other authorized queries. | The deploy wizard includes review. Later deploy runs also update triggers automatically. |
| Analytics destination | Receive the product events you send. | Separate server-side credentials and Supabase storage configuration. |
Moving to read-write asks you to authorize again. To return to read-only, disconnect and reconnect. Disconnecting OAuth removes its stored tokens; deployed triggers remain in your database. Disconnecting the event destination removes its stored credentials; existing events stay in your bucket.
Read connection detailsPermission and review are distinct.
| Action | Review or permission |
|---|---|
| Application code change | Engineer reviews before merge. |
| Canvas proposal | Your team accepts or dismisses it in the workspace. |
| MCP journey build | No review step. Authorized write access saves the definition directly. |
| Trigger deployment | The deploy wizard has a review step. Later deploy runs also update triggers automatically. |
The MCP tools an agent sees follow its credential’s scopes. Read-only mode omits write tools. Workspace API keys receive full workspace access; OAuth tokens support narrower scopes.
Review workspace accessReview retained data separately.
Cloud retains artifacts and review context between runs. The permissions above do not list everything stored or every processor involved.
Confirm current retention periods, deletion handling, processors and certification requirements with us. Do not assume that removing a connection deletes every stored record.
Bring the requirements for your security review.
Tell us which data, access restrictions, retention periods and certifications your team needs to assess.
Contact us about security