Rabbit Hole › Privacy
Privacy
Rabbit Hole has no server, no accounts and no database. A rabbit hole lives in your browser while you build it, and in the link when you share it.
What stays where
- Your draft is saved in your browser's local storage so it survives a reload. It never leaves your device. Press “New” in the builder or clear this site's data to remove it.
- A shared rabbit hole is encoded in the part of the link after the # sign. Browsers don't send that part to web servers, so even this site's host never sees it. Anyone you give the link to can read it.
- Video titles are looked up when you add a link, through YouTube's public oEmbed address (youtube.com/oembed). That request tells YouTube which video you added; nothing else is sent.
YouTube
Videos play in YouTube's embedded player in privacy-enhanced mode (youtube-nocookie.com), and thumbnails load from YouTube's image servers. YouTube describes privacy-enhanced mode as not using what you watch in an embedded player to personalise your YouTube experience. Once a video plays, YouTube's privacy policy and terms apply to it. Rabbit Hole can't see what YouTube collects and doesn't receive anything from it.
Counting visits
This site doesn't count visits at the moment. If counting is switched on later, it will be cookieless, it will never receive the contents of a rabbit hole or anything you type, and it will be skipped when your browser sends Do Not Track or Global Privacy Control.
Hosting
The site is static files on GitHub Pages. Like any web host, GitHub receives the usual request information (your IP address and browser) when you load the pages; see GitHub's privacy statement.
Content
Rabbit Hole doesn't host videos. Every video belongs to its creator and plays from YouTube under YouTube's terms. The demo paths use public videos whose owners allow embedding, and link to them on YouTube. To report a problem, open an issue at the project's GitHub page.