Skip to content
Dori Help Center
Esc
navigateopen⌘Jpreview
On this page

GitHub Vault Sync & Privacy Controls

How Dori uses private GitHub repositories for cloud backup, time-travel version control, and zero vendor lock-in.

Dori uses GitHub as its primary remote vault backup and synchronization provider. Your personal notes, project histories, and decisions stay synchronized to a repository you own on GitHub.

Local Markdown VaultPlain Files on DiskOffline PrimaryEngine Sync DriverAutomated Git CommitsConflict DetectionPrivate GitHub RepoStrictly Private OnlyFull Commit History

1. Strict Privacy Rule: Private Repositories Only

Dori enforces a strict security policy: Vault repositories must be 100% Private.

  • No Public Repo Risk: Dori will reject connecting to or bootstrapping a public GitHub repository. This prevents accidental exposure of client notes, meeting transcripts, or personal thoughts.
  • You Own the Remote: The repository is created under your personal GitHub account (github.com/your-username/dori-vault). Dori never stores your vault content in a central Dori server database.

2. Automatic Private Repo Bootstrapping

Setting up GitHub sync requires zero Git commands:

  1. Go to Settings → Connections → GitHub and click Connect.
  2. Authenticate with your GitHub account.
  3. Dori automatically creates or connects a private repository (dori-vault) and bootstraps initial vault commit history.

3. Git-Backed Time-Travel History

Because your remote vault is a standard Git repository:

  • Complete Commit History: Every note edit, meeting debrief, or project update creates clean Git commits. You can view past versions of any note at any point in time.
  • Multi-Device Synchronization: Connect Dori Desktop on your laptop and desktop Mac to keep your memory in sync across machines.
  • Zero Lock-In: If you ever stop using Dori, your full Markdown repository remains accessible on GitHub and locally on your hard drive forever.

Was this page helpful?