Data Ownership
If you stop using PlainHub — or if PlainHub itself goes away — your notes stay in your GitHub, exactly as they are. They're plain text files, so any editor can open them.
Why your notes stay
- Saved only in your GitHub repository — PlainHub has no server or database that holds your files. They're saved to a repository in your own GitHub account from the start
- Contents never pass through PlainHub's servers — Files are read and saved directly between your browser and GitHub
- Plain text files with Git history — Nothing is converted to a special format, so there's nothing to export. Open them in any editor or Git tool and keep writing
Data flow
graph LR
A["Browser / CLI"] -- GitHub API --> B["GitHub"] -- read/write --> C["Your Repo"]
File contents are read and saved directly between your browser and GitHub. No PlainHub server sits in between. (If you use AI, the content you send goes from your browser straight to the AI provider with your own key.)
How it compares
| Service | Where your data lives | If the service shuts down |
|---|---|---|
| Typical cloud note apps | The provider's servers | You need to export before it's gone |
| PlainHub | Your GitHub | Nothing to do — it all stays |
What this means for you
- Leave anytime — You're not locked in to PlainHub, and there's nothing to migrate when you go
- Open them anywhere — Plain text files work with any local editor or Git tool
- A record of every change — Git history shows who changed what, and when. Useful for audits and reviews
What PlainHub records
PlainHub never records your file contents. To run sign-in and understand usage, it handles only a minimum of information, such as your GitHub username and when you used the app (deleted automatically after 90 days). See the Privacy Policy for details.