On this page
Security & Data

What Acrosite stores about your content

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.

ReferenceFor OwnersUpdated November 12, 2026

Acrosite keeps a workspace-scoped record of your content work so your team can write, review, schedule, and publish. Your published content also lives in your own repository. This reference summarises what Acrosite stores and where.

Who this is for

Workspace Owners who want a clear picture of what data Acrosite holds.

What Acrosite stores in the workspace

Inside your workspace, Acrosite keeps the records that make authoring work:

  • Drafts and content items — your work in progress and its current status.
  • Content structure — your Custom Content Types and Custom Fields.
  • Media references — the staged and published media for your projects.
  • Review history — submissions, approvals, requested changes, and comments.
  • Publishing and deployment records — Publish Logs and Deployment Logs (sanitized), and the build status reported to GitHub for commits Acrosite published.
  • Workspace and billing state — your team, plan, usage, and access state.

All of this is scoped to your workspace. See Workspace and tenant isolation.

What lives in your repository

When you publish, your content is committed to your own GitHub repository as Markdown with frontmatter, along with the media it uses. That repository is the source of truth for your published site. See You own your content and repository.

What Acrosite does not store in the open

Note
Acrosite is designed to keep secrets out of the records you can see. Logs and notifications avoid tokens, full deployment hook URLs, raw provider payloads, and other sensitive values. See How Acrosite handles secrets.

How long Acrosite keeps it

While a workspace has an active plan, a running trial or complimentary access, Acrosite does not close it or remove its content because nobody signs in. Publish Logs, Deployment Logs and items in Trash follow their own retention periods. When that access ends and nothing replaces it, the workspace becomes read-only:

  • Acrosite keeps a read-only workspace for at least 12 months, and emails the Owner and Admins at least 30 days and at least 7 days before it closes the workspace.
  • On or after the closing date, the workspace closes for everyone. For 30 days after that, Acrosite Support can restore it at the Owner's request.
  • After that, its projects, content, media, Team Members, invitations and connections are permanently removed. Billing records are kept, without names, email addresses, websites or content.
  • A workspace you delete yourself follows its own 30-day recovery period.

None of this changes your GitHub repositories or published websites. See When a workspace has no active plan.

Acrosite's database is backed up daily, and recent backups are kept for a limited time; uploaded files are stored separately and are not in those backups. The Privacy Policy explains the records kept after a deletion, how backups and restores are handled, and what service providers keep.

Next steps