Privacy
Prose never enters our servers
GitPress.net is a cloud tool, not a content host. When you open the admin, the platform uses the GitHub App you authorized to read your repo; save writes back to the same repo. The only source of prose is your GitHub, not our Postgres.
Control plane
Enough to sign in and find your sites. Not a draft library.
Sign-in account
Email, display name, avatar. Auth needs them.
GitHub App install mapping
So the admin can read and write repos on your behalf. Uninstall the App and this link breaks.
Site pointers
Site name, theme name, the two repo URLs, public URL, and similar metadata.
Optional: your own AI key
Stored only if you fill it in. Encrypted; the database never has plaintext.
Visits to gitpress.net itself
When this app is deployed on Vercel, Web Analytics counts opens of the marketing site and admin. There is no analytics key in the repo. Readers of your blog do not go through gitpress.net, and those views are not counted here.
Content
These live only on your GitHub. We have no second copy.
Posts and pages
Markdown prose and drafts. Save writes them into the private data repo.
Media files
Images, video, and the like. Same data repo only.
Public-site HTML
On your site repo / Pages. Reader requests do not go through gitpress.net.
After you revoke access
Uninstall the GitHub App or delete the repo, and we can no longer read content.
Where data goes
Four steps. There is no “upload to GitPress, then we distribute it” hop.
1 / 4
You write in the admin
The editor is on gitpress.net. The draft has not become “our data” yet.
2 / 4
The platform calls the GitHub API
Opening the admin reads your repo; save writes back to the same repo.
3 / 4
Private data repo
Prose, media, and drafts live only here. This is the only source.
4 / 4
Public site repo / Pages
Actions compiles HTML. Readers do not go through gitpress.net.
What the three pieces do, and what happens if we shut down: What is GitPress?.