Privacy Policy


We value your privacy and question everything that stores or processes your personal information. With that in mind, we still need a few external services to publish Tiptap.

We don’t provide email support for Tiptap, but if you have some legal issues, privacy or security concerns, send us an email to For everything else, please use GitHub issues.

Necessary cookies

Missing the cookie banner? Sorry, we use technically necessary cookies only. 🍪

  1. The XCSRF-TOKEN cookie is a security measure to prevent attackers from sending data to our servers in your behalf.
  2. The laravel_session cookie stores who you are, after you logged in.

Delete your account

If you signed up and want to delete your account, you can do that on your profile page. Just scroll down to the bottom, click “delete account” and follow the instructions.

For security reasons we can’t delete your account manually. You wouldn’t want us to delete your account when someone asks to do so, right? Unfortunately it’s not easy to make 100 % sure who sent an email, so we can’t trust email inquiries to delete accounts.

Your data will be completely deleted from our database. If you created a subscription with our payment provider Paddle, they’ll need to keep your information for legal reasons though.

List of external services

Community (GitHub)

We use GitHub to store our code, collaborate, give support, and offer sponsorships. Check their privacy statement to learn more about what data they process.

Hosting (DigitalOcean)

We use DigitalOcean to host the documentation. We’re using a virtual server (“Droplet”) in their Frankfurt (Germany, EU) data center to run the Laravel application that renders the documentation. If you want to know more, read DigitalOcean’s privacy policy.

Deployment (GitHub Actions)

We use GitHub Actions to deploy the documentation to our server. It checks the code for issues, runs automated tests and releases new versions automatically. If you want to know more, read GitHub’s privacy policy

Tracking (Plausible)

We use Plausible to gain insight about our visitors in general. It doesn’t track individual users per se and does not store any personal identifiable information. Go to their documentation to find out what Simple Analytics collects (and more importantly what they don’t).

Or have a look at the public analytics dashboard they provide. It’s not a stripped down version, it’s the exact same dashboard we use to check the traffic.

Search (Algolia)

We use Algolia DocSearch to offer search functionality for the documentation. They crawl the same pages as you see once every day. If you click on the search field on top of this page, their search interface pops up.

If you want to know more about what data they collect and process, read Algolia’s privacy policy.

Subscriptions (Paddle)

We use Paddle to sell subscriptions. They are the merchant of record, so it’s them who you officially buy from. They provide us with an API to handle your subscription. Also, they store your personal and payment data to process the subscription payment. If you want to know more, read Paddle’s privacy policy.

Suggesting alternatives

If you know a good self-hosted version of any of the mentioned services, create an issue on GitHub or send us an email to