This policy covers the website at enidor.com, including the receive page at enidor.com/d/, run by hermesnetdev. It explains what happens to information about you when you visit.
The short version
- We don't run analytics, and we don't ask you for any personal information on this site.
- The site is hosted on GitHub Pages. GitHub logs visitors' IP addresses for security.
- Pages on this site, including the receive page, show ads from Google, which may use cookies. The Enidor app has no ads.
- Files you receive come straight from the sender's computer, encrypted end to end. We can't read them, and they're never stored on our servers.
Hosting
enidor.com is served by GitHub Pages. When you visit any page, GitHub logs and stores your IP address for security purposes, whether or not you have a GitHub account. GitHub's handling of that data is described in the GitHub General Privacy Statement. We don't receive those logs.
Advertising
Pages on enidor.com, including the receive page (/d/), may show ads served by Google AdSense.
- Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this website or other websites.
- Google's use of advertising cookies enables it and its partners to serve ads to you based on your visits to this site and/or other sites on the Internet.
- You may opt out of personalized advertising by visiting Google Ads Settings.
- You can also opt out of other third-party vendors' use of cookies for personalized advertising at aboutads.info.
Visitors in the European Economic Area, the United Kingdom and Switzerland are asked for consent before Google uses cookies or similar technologies for personalized ads, and can change that choice later. How Google uses information from sites that use its services explains what Google collects and how.
The release list
The home page and the receive page link to the latest Enidor release. To find it, your browser asks GitHub's API directly, so GitHub sees your IP address. Your browser keeps a copy in local storage for 10 minutes so repeat visits don't ask again. The copy contains only public release information and stays in your browser.
The receive page
The receive page lets you download files someone shared with you, straight from their computer. It has no analytics.
- Ads. The page shows ads from Google, as described above. Google's ad code runs inside the page, so, like any code on a page, it can technically see what the page shows, such as the link and the names of the files. If you'd rather avoid that, open the link in the Enidor app, which has no ads.
- The link. The share's ID sits after the
#in the link. Browsers don't send that part to the web server, so GitHub never sees it. The page sends it to Enidor's room directory to find out which computer is hosting the share. - Enidor's servers. The room directory and the relay that sets up the connection see your IP address and the share you're opening, as any server you connect to does. The relay may also carry the transfer when a direct connection isn't possible. Transfers are encrypted end to end, so it can't read them.
- The sender. Your browser connects to the sender's computer. The sender's app records the visit in their Activity Monitor and audit log, labelled with your browser and operating system (for example, “Web guest · Chrome on macOS”), along with which files you opened. A PIN you enter is sent to the sender's computer to unlock the share.
- Your browser. Downloads are written into your browser's private storage while they arrive, and stay there until you save or discard them. Anything left over is deleted automatically on a later visit once it's more than an hour old.
Cookies and browser storage
| What | Where | Why |
|---|---|---|
| Google advertising cookies | Every page | Serving and measuring ads, subject to your consent where required |
enidor:releases:v1 (local storage) | Home page and receive page | Caches the public release list for 10 minutes |
enidor-downloads (private file storage) | Receive page | Holds a download in progress until you save or discard it |
Clearing this site's data in your browser removes all of it.
Children
This site isn't directed at children under 13, and we don't knowingly collect information from them.
Changes to this policy
If this policy changes, the new version will be posted on this page with a new date at the top.
Contact
Questions about this policy can be raised on GitHub.