Your machine · Skene OSS

Chosen inputs and local output

Repository and optional schema inputs are read for analysis. The journey artifact is written locally.

Provider credentials may be saved in local configuration.

Chosen model provider

Analysis context

A remote model receives analysis context when you select one. A supported local provider keeps model processing local.

Local execution alone does not mean local model processing.

Skene Cloud · Separate workspace

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.

Approve all repositories or a selected set during installation. A workspace owner links the repository. This app connection does not require a personal access token.

Permissions requested by the Skene GitHub App
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 contract

Schema 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. Compile/deploy cycles also reconcile triggers automatically.
Analytics destination	Receive the product events you send.	Separate server-side credentials and Supabase storage configuration.

Read-write upgrade uses re-authorization. Returning to read-only requires disconnecting and reconnecting. 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 details

Permission 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	Authorized write access saves the definition directly.
Trigger deployment	The deploy wizard has a review step. Trigger reconciliation also runs automatically during compile/deploy cycles.

MCP tool visibility follows credential scopes. Read-only mode omits write tools. Workspace API keys receive full workspace access; OAuth tokens support narrower scopes. Revoke workspace credentials when access is no longer needed.

Review workspace access

Review retained data separately.

Cloud retains artifacts and review context between runs. Source permissions do not, by themselves, describe every stored artifact or processor involved.

Confirm current retention periods, deletion handling, processors and certification requirements with the team. Removing a connection does not establish deletion of every stored record.

Read the privacy policy Inspect the OSS boundary

Bring the requirements for your security review.

Tell us which data, access restrictions, retention periods and certifications your team needs to assess.

Know what each connection can reach.