Security & Data
Security & Data
You own your content and repository. Understand workspace isolation, scoped GitHub access, server-side secrets, and Client Reviewer isolation.
Articles
You own your content and repositoryOverview
Acrosite is Git-backed: it commits your content as Markdown to your own GitHub repository, so your content and its history live with you, not locked inside Acrosite.
acrosite.com/docs/security/data-ownership
How Acrosite uses GitHub accessOverview
Acrosite connects through a scoped GitHub App, commits only to the repositories and paths you choose, and keeps installation tokens server-side — never in your browser.
acrosite.com/docs/security/how-acrosite-uses-github
Workspace and tenant isolationOverview
Your workspace is the tenant boundary in Acrosite. One workspace cannot reach another workspace's clients, projects, content, media, reviews, logs, or billing state.
acrosite.com/docs/security/workspace-isolation
How Client Reviewers stay isolatedOverview
Client Reviewers work from a separate portal and only see the projects and content you assign — never your repository, deployment, billing, team, or other projects.
acrosite.com/docs/security/client-reviewer-isolation
How Acrosite handles secretsOverview
GitHub tokens, deployment hook URLs, webhook secrets, and provider credentials stay server-side. You see safe status and masked metadata — never raw secrets, in the UI or in logs.
acrosite.com/docs/security/secrets-and-secure-storage
What Acrosite stores about your contentReference
An overview of the workspace-scoped records Acrosite keeps — drafts, structure, media references, review and publishing history, and logs — and what stays in your repository.
acrosite.com/docs/security/what-acrosite-stores