privacy policy

who is responsible

hop is made by anton shakirov. questions about this policy and any request about your data go to info@hop.tools, and the person who writes the code answers them.

the app

hop has no account, no telemetry, no analytics and no crash reports. timers, tasks, clipboard history, converted files and everything else stay on your mac, in your own user folder. nothing about how you use the app is sent anywhere, and the whole source code is open, so this can be checked rather than trusted.

the app goes to the network in four cases, and in each of them it sends only what the task needs:

• once an hour it asks hop.tools whether a newer version exists, passing the version currently running. the answer is a small manifest. our server writes the usual web-server line about that request: address, time, and the app's user agent.
• when you turn on torrents, file archives or video conversion for the first time, the matching helper is downloaded. the files are served through a content delivery network (bunny.net), which sees the same kind of request data its servers always see.
• the internet speed test measures against apple's own servers, and only while you keep it running.
• torrent traffic goes directly between you and other participants of a download, and only for downloads you start yourself.

the app never opens any of these connections on its own initiative beyond the update check, and the update check can be turned off in settings.

this site

the site is a set of static pages. there are no forms, no registration and no comments, so there is nothing here that could ask you for personal data.

the web server writes an ordinary log line for every request: the address the request came from, the time, the page, the response code, the browser's user agent and the referring page. these lines exist to keep the server working and to notice attacks, they are kept for fourteen days and then deleted by rotation. the legal basis is legitimate interest in a working and secure service.

the download button goes through our own address before it sends you to the file, so that a click can be counted. that produces the same log line and nothing else. the number of downloads shown in the readme is built from those lines.

if you agree to it, the site loads google analytics (property G-ZRRWFEJSM1) and it collects the usual visit statistics: pages viewed, approximate location by network address, device and browser, and how you arrived. google llc acts as our processor and may process this data outside your country, including in the united states. the legal basis is your consent, the data is kept for fourteen months, and until you agree nothing is loaded and no request goes to google at all.

what is stored in your browser

• your answer to the consent banner, so it is not asked again.
• the language you picked in the switcher, so the site does not send you elsewhere next time.
• after you agree to analytics: google's own cookies (_ga and similar), which live up to two years and hold a random identifier of the browser, not of you.

the first two are kept by the browser itself and never leave your device.

changing your mind

consent can be withdrawn at any moment, and the site has to accept that as easily as it accepted the consent. clearing site data for hop.tools in your browser settings removes both our stored answer and google's cookies, and the banner will ask again on your next visit.

if you are in the european union or the united kingdom

the general data protection regulation gives you the rights below, and they apply to the log lines and analytics described above, since those are the only data we have:

• to know what is stored about you and to get a copy of it.
• to have it corrected if it is wrong.
• to have it deleted.
• to restrict or object to its processing.
• to receive it in a machine-readable form.
• to withdraw consent to analytics without giving a reason.
• to complain to the data protection authority of your country.

a request sent to info@hop.tools is answered within thirty days. be aware that server log lines are identified only by network address and time, so a request about them has to say which address and roughly when, otherwise there is nothing to look up.

children

the app and the site are not aimed at children and do not knowingly collect anything about them.

changes to this text

the date at the top says when this page last changed. if something changes that affects what is collected, the change is written here before it starts working, not after.