Legal information
Privacy policy
autofetch
Last updated: 20 July 2026
This English translation is provided for accessibility and information. In case of differences, the German privacy policy is the authoritative version.
Protecting personal data is important to us. This policy explains which data autofetch processes, why it is needed and which rights you have.
1. Controller
Han Esser
Schloßgasse 6a
65239 Hochheim am Main
Germany
Email: support@autofetch.de
2. Data and purposes
2.1 Account
For registration and account operation, autofetch processes your email address, username, a securely hashed password, registration and verification times and, where required for security and proof of registration, the associated IP address.
Legal basis: Article 6(1)(b) and (f) GDPR.
2.2 Technical access data and server logs
Operational server logs may contain the network address, time, requested path, response status and user agent where needed to secure and operate the service. They are retained for no longer than 30 days.
2.2.1 Privacy-friendly traffic statistics for public pages
A separate, deliberately reduced traffic log records only the public path, day and time, response status, whether the request appears to come from a person or an automated client, and a coarse source category such as direct, internal, search engine or external.
This reduced log contains no IP address, user or session ID, tracking cookie, raw referrer, referrer host, search term, user agent or URL query parameter. It is not used to create individual browsing profiles and is deleted after no more than 30 days.
2.3 Watches, jobs and clients
The server stores the configuration, metadata, job and status information needed to provide the service. Downloads themselves are performed by a client on your device and are not relayed through or stored as media files on the autofetch server.
2.4 Email and support
Your email address is used for account verification, requested password resets, important service notices, optional notifications and support. Support submissions may contain your description, client version, system information and redacted log excerpts.
2.5 No tracking or profiling
autofetch uses no advertising trackers, marketing analytics or cross-site profiles. User data is not sold to advertisers.
3. Recipients
Data is not shared for advertising. The service is hosted by IONOS SE in Germany as a processor under Article 28 GDPR. Data may also be disclosed where required by law or a binding authority or court order.
4. Hosting and location
The service is hosted in Germany. Personal data is processed within the European Union unless this policy explicitly states otherwise.
5. Retention
- Account data: until account deletion, then normally deleted within 30 days unless a legal obligation applies.
- Server and reduced public traffic logs: no longer than 30 days.
- Configuration, activity and status data: while needed for the account and according to configured retention.
- Support communication: while needed to resolve the request and reasonable follow-up questions.
6. Cookies and device storage
Only technically necessary cookies are used:
autofetch.sid: a random session identifier required for sign-in, session security and CSRF protection; removed on sign-out or after no more than seven days.autofetch_locale: contains onlydeorenand remembers an explicitly selected language for no more than one year. For signed-in users the language is also stored in the account so the interface and emails can use it.
The browser language may be read on a first visit but is not thereby saved permanently and never overrides an explicit selection.
autofetch does not currently use localStorage or sessionStorage to retain search terms, sorting preferences or tracking identifiers.
7. Your rights
Subject to the legal requirements, you have rights of access, rectification, erasure, restriction, data portability and objection under Articles 15–21 GDPR, and may withdraw consent where processing relies on consent. Contact support@autofetch.de. You may also complain to a competent data-protection authority.
8. Security
Measures include HTTPS/TLS, secure password hashing, protected session cookies, access restrictions and regular security updates.
9. Changes
This policy may be updated when the service or legal requirements change. Material changes will be communicated where required.