Privacy Policy

The short version

Dillinger is a browser-based markdown editor. You can use it without an account. Your documents are saved in your own browser's local storage — not on our servers. We do not sell your data.

What we store

In your browser: your documents, editor settings (theme, keybindings, preview mode), and recent files. This data lives in localStorage on the device you are using. Clear your browser storage and it is gone.

On our servers: nothing tied to your identity. We do not maintain user accounts and we do not persist your document contents.

Cloud integrations

If you connect Dillinger to GitHub, Dropbox, Google Drive, OneDrive, Bitbucket, or Medium, OAuth tokens are issued by those providers and held only for the duration of your session so we can read and write the specific files you ask us to. We do not browse your accounts in the background.

Disconnecting is as simple as revoking access in that provider's settings. You can also clear your local browser storage to remove any session state on your end.

Analytics and ads

We use privacy-respecting analytics to understand aggregate usage of the site (page views, traffic sources). Dillinger may also display a single Carbon ad on the landing page; Carbon serves a contextual ad based on the page itself, not on your personal profile.

Exports and uploads

HTML and PDF exports are generated on demand by our server. The markdown you submit for export is processed transiently and is not retained after the response is returned.

Children

Dillinger is a general-audience tool and is not directed at children under 13.

Changes

If this policy changes in a way that affects how we handle your data, we will update the "Last updated" date above and, where appropriate, surface a notice in the editor.

Contact

Questions? Open an issue at github.com/joemccann/dillinger.