markbaseCurrent access model
Security and data use
Markbase is being migrated toward selected-repository, least-privilege access. This page describes the current production behavior so you can make an informed choice today.
GitHub permissions
GitHub's current OAuth repo scope grants broad read and write access to repositories. Markbase uses that token only to read repository metadata and markdown content; it does not commit, push, or modify repository contents. A GitHub App migration is planned so users can select repositories and grant narrower, short-lived access.
Sessions and shares
Web sessions keep the GitHub token in an encrypted Auth.js session. New file shares store an encrypted immutable copy of that file and do not retain a reusable GitHub token. Repository and folder shares, plus older file shares, still use an encrypted token on the server so documents can be fetched later. The token is never sent to the recipient, but its GitHub permission scope is broader than the shared scope. Delete shares you no longer need and revoke the OAuth app in GitHub to invalidate legacy live-share access.
AI summaries
When AI summaries are enabled by the operator, Markbase may send up to 30,000 characters of public document content to the configured OpenAI, Anthropic, or Google model. Private or unknown repository visibility fails closed unless the operator separately opts in. Generated summaries and provider/model metadata are cached in Postgres. Per-repository consent and deletion controls are still planned; keep private summaries disabled until that policy matches your requirements.
MCP access
MCP access and refresh tokens contain a revocable server-side grant identifier, not a GitHub credential. The encrypted GitHub token remains on the server. Refresh rotation invalidates the previous grant version, authorization codes are single-use, and an authenticated MCP DELETE request revokes the grant.
Stored product data
Markbase stores user profile metadata, repository names, share scope and recipient metadata, comments, review baselines, content hashes, and cached AI outputs. It does not store a second editable copy of your repository documents.
Revoking access and reporting issues
You can revoke Markbase from GitHub's application settings and delete active shares from Markbase. Security issues should be reported privately using the repository's security policy.