Effective: March 11, 2026 · md-edit on GitHub
Your data situation depends entirely on whether you create an account.
| Data | No account | MD-Edit Cloud | Google Drive |
|---|---|---|---|
| Your documents | Browser only | Browser + our servers | Browser + your Drive |
| Email address | Not collected | Stored in Supabase | Not collected by us |
| Terms consent timestamp | Not collected | Stored in Supabase | Stored in Supabase |
| MCP connection metadata | Not collected | Stored in Supabase | Stored in Supabase |
| Cookies | None | None | None |
| Analytics / tracking | None | None | None |
| Server access logs | IP, browser, page, timestamp | Same | Same |
md-edit works entirely offline in your browser. Your documents are stored in your browser's IndexedDB — a local storage mechanism similar to cookies but larger and server-inaccessible. We have no technical ability to read them.
We set no cookies. We load no third-party scripts (analytics, ads, social widgets). The only network requests your browser makes are to fetch the app itself from our CDN (Netlify).
Like any web server, Netlify records standard HTTP access logs containing your IP address, browser user-agent, the URL you requested, and a timestamp. This is infrastructure-level logging, not personal profiling. These logs are retained for approximately 30 days.
Signing in is optional. It exists solely to enable sync across devices and optional future features. When you sign in and choose MD-Edit Cloud, we store the following in our database (Supabase, hosted on AWS):
| What | Why |
|---|---|
| Email address | Your account identifier. Used to send magic-link emails if you request them. |
| Document titles and content | To sync your documents across devices and keep a backup. |
| Plan tier | To know which features you have access to (free, pro, etc.). |
| Terms of Service consent | Timestamp and version of the ToS you agreed to. Required for GDPR compliance to prove consent. |
| MCP connection data | If you connect Claude.ai or other AI assistants via MCP (Model Context Protocol), we store: platform name (e.g., "claude.ai"), client ID (anonymous identifier), connection timestamp, and usage count. This enables the MCP integration feature. |
| Auth session token |
Stored in your browser's localStorage — not a cookie.
Used to authenticate API requests. You can clear it by signing out.
|
We do not store your password (we don't offer password sign-in). If you use GitHub or Google sign-in, we receive only your email address from them — we do not request access to your repositories, contacts, or any other data.
As an alternative to MD-Edit Cloud, you can connect your own Google Drive account.
When you do, your documents are stored as .md files in a dedicated
"md-edit" folder in your Google Drive.
We never see your documents. Files go directly from your browser to Google's servers via the Google Drive API. We do not proxy, cache, or store your document content on our servers at any point.
Minimal permissions. We request the drive.file scope,
which is the least-privilege option Google offers. This means the app can only
access files it created — it cannot read, modify, or list any other files in your Drive.
Short-lived tokens. Google issues an access token that expires after approximately one hour. We do not store this token persistently — it lives only in browser memory for the duration of your session. When it expires, Google seamlessly re-authenticates you. We never receive or store a refresh token.
Revoke anytime. You can disconnect Google Drive from within md-edit's settings. You can also revoke access at any time from your Google Account Permissions page. Revoking access does not delete the files already in your Drive — they remain yours.
We use a minimal set of services. None of them are advertising or analytics platforms.
drive.file scope — app can only access files it created). Documents go directly from your browser to Google; we never proxy or store them.
Privacy policy ↗
There are no other third-party services. No Google Analytics, Mixpanel, Segment, Hotjar, Facebook Pixel, or similar. The full list is above.
Export anytime. Use the "Download all as ZIP" button in the sidebar to export every document as plain Markdown files. No account needed.
Delete your account. Email us at the address below. We will delete your profile, documents, and auth record from Supabase within 30 days. Your local browser data is under your own control — clear it via your browser's developer tools (Application → IndexedDB → documents).
Access your data. Email us and we'll provide a full export of everything we hold about you.
Opt out of sync entirely. Simply don't create an account. The editor works identically without one.
No account: We hold no personal data on our servers. Your documents persist in your browser until you clear them.
MD-Edit Cloud account: Your data is retained until you request deletion. Netlify server logs expire after approximately 30 days.
Google Drive: Documents remain in your Google Drive even after you disconnect from md-edit. We do not retain any copies on our servers.
md-edit is provided "as is" and "as available" without warranty of any kind, express or implied, including but not limited to warranties of merchantability, fitness for a particular purpose, or non-infringement.
We do not guarantee that the service will be uninterrupted, error-free, or that data will not be lost. Browser-based storage (IndexedDB) can be cleared by your browser, operating system, or privacy settings at any time. Cloud sync depends on third-party services (Supabase, Google) that may experience outages or data loss outside our control.
You are responsible for maintaining your own backups. We strongly recommend using the "Download all as ZIP" feature regularly to keep copies of your work outside the app.
To the maximum extent permitted by applicable law, md-edit, its operators, and contributors shall not be liable for any indirect, incidental, special, consequential, or punitive damages, or any loss of data, profits, or revenue, arising out of or in connection with your use of the service — even if we have been advised of the possibility of such damages.
For complete terms governing your use of the service, please see our Terms of Use.
If we make material changes — for example, adding a new data type we collect or a new third-party service — we will update the effective date at the top of this page and, if you have an account, notify you by email.
Questions, data requests, or account deletion: