Privacy

Privacy Policy

This policy explains how FUD Archive processes personal data when you use the website, submit screenshots, or allow optional analytics. Last updated: July 27, 2026.

1. Controller

Martin Geltl
ProxyHub
PX-10026
Höhenstraße 10
70736 Fellbach
Germany
Email: kontakt@fud-archive.com

2. Hosting, submissions, and public archive

FUD Archive is hosted on Vercel and stores submitted screenshots and metadata in Cloudflare R2. Technical request data such as IP address, timestamp, requested URL, referrer, user agent, status code, and transferred volume may be processed to deliver, secure, and troubleshoot the website.

When you submit content, we process the uploaded image, platform, date, topic, language, and optional source metadata. When you report or suggest a correction for a public entry, we process the entry id, selected reason, optional message, optional contact email, page locale, and a hashed IP-based rate-limit key. When you send site feedback, feature requests, bug reports, or change ideas, we process the selected category, message, optional contact email, page locale, and a hashed IP-based rate-limit key. IP addresses are not stored in plain text for submissions, reports, or feedback. Approved submissions become publicly visible; reports and feedback stay private for admin review.

3. Embedded X posts

The archive listing displays X posts in a custom view. Our server retrieves the post data from X and caches it temporarily. Your browser loads profile images and, where displayed, post media directly from X's media servers, which may receive the IP address, user agent, referrer, and other technically necessary connection data. Further processing by X is described in the X Privacy Policy. The separately available archive screenshot continues to be delivered through Cloudflare R2.

4. X bot tags and hunter credits

When you tag @FUDArchiveBot on X, we process the tagging post (ID and text), your X user ID and, where X provides it, your handle. We use them to match the tag to the intended post, reply to you on X and credit the find. The user ID is stored internally only; it appears neither in the public archive nor in the data export.

If the post is published as an entry and you were the first to tag it, the entry may show "Archived by @handle", and the hunter leaderboard lists your handle with the number of your public entries and the date of your last find. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is crediting contributors and operating the archive.

You can object at any time: write "anon" or "anonym" in a tag, use the feedback form or email the address in the imprint. The objection applies retroactively to all entries and the leaderboard. On request we delete the stored handle. The link to your user ID stays internal so the objection also covers future tags.

5. Cookies, local storage, and analytics

The admin area uses the technically necessary HTTP-only cookie fud_admin_session. Public preferences such as privacy choices and currency selection are stored locally in your browser. Optional Vercel Web Analytics is loaded only after consent and can be changed through the cookie settings link in the footer.

6. Legal bases and rights

Processing is based on contract-related steps for submissions, legitimate interests in operating and securing the archive, and consent for optional analytics. You may request access, rectification, deletion, restriction, data portability, object to legitimate-interest processing, withdraw consent, and lodge a complaint with a competent supervisory authority.