Privacy policy
Last updated: 16 November 2026
This is a convenience translation. Only the German version, the Datenschutzerklärung, is legally binding. To read it, switch to “DE” at the top.
This privacy policy applies to argupedia.com and to the former address argupedia.eu, which now only redirects to argupedia.com.
1) Controller
Controller within the meaning of the GDPR (DSGVO):
Julian Ohm
Holzgasse 8
50676 Köln
Germany
Email: info@argupedia.com
2) Delivery, security & performance (Cloudflare)
This website uses Cloudflare (Cloudflare, Inc., 101 Townsend St, San Francisco, CA 94107, USA) as a content delivery network (CDN), hosting and security service (e.g. protection against DDoS and other attacks, stability and performance).
When you access the website, Cloudflare processes technical connection data, in particular:
- IP address
- date and time of access
- requested URL or file
- referrer URL
- browser and device information (user agent)
- where applicable, security-related signals used to detect and fend off attacks
Purpose: secure, stable and efficient provision of the website.
Legal basis: Art. 6(1)(f) GDPR (legitimate interest in security and
reliable operation).
Data processing: a data processing agreement (Art. 28 GDPR) is in place
with Cloudflare.
The databases of this website (content and community data) are run at Cloudflare with the location setting Western Europe.
3) Cloudflare Web Analytics
I use Cloudflare Web Analytics to measure reach and improve the website. Cloudflare describes Web Analytics as "privacy-first" and states that no client-side state such as cookies or localStorage is used to collect the usage metrics, and that users are not tracked over time by fingerprinting (e.g. via IP address or user agent). This statement refers solely to reach measurement; for strictly necessary cookies and local storage used by the website itself, see section 4.
In the process, usage data (typically aggregated) may be processed, for example:
- pages or URLs visited and the time of the visit
- referrer (the page you came from)
- technical information (e.g. browser type)
Purpose: statistics and optimisation of the website.
Legal basis: Art. 6(1)(f) GDPR (legitimate interest in analysing and
improving the service).
4) Cookies & local storage
This website uses only strictly necessary cookies and local storage. No marketing, tracking or profiling cookies are used; a consent banner is therefore not required.
a) Cloudflare security cookie
Depending on the bot and security features enabled, Cloudflare may set
strictly necessary cookies (e.g. __cf_bm for Bot
Management/Bot Fight Mode).
Legal basis: Art. 6(1)(f) GDPR (security and abuse prevention).
b) Sign-in and session cookies
When you sign in, the website sets strictly necessary session cookies
(better-auth.session_token and a short-lived cache cookie
better-auth.session_data) so that you stay signed in. They
contain a signed session identifier or signed session data (no password
in plain text), are set as httpOnly and Secure,
and expire after at most 7 days or are deleted when you sign out. These
cookies are not set if you do not sign in.
Legal basis: Art. 6(1)(b) GDPR and § 25(2) TDDDG (strictly necessary for
the service requested).
c) Local storage (localStorage)
Below the circle of arguments on the debate pages, “Edit the circle”
lets you build your own version of a debate: changed scores (value,
impact, plausibility), removed arguments and arguments you add yourself.
The calculation runs entirely in your browser. This version is stored
only if you explicitly click “Save in this browser”, and then solely
locally on your device (localStorage, key
argumenta:kreis-bearbeiten:<debate>), so that it is
still there next time. Without that click nothing is stored. The data is
not transmitted to the server, not analysed and not linked to any
account. “Delete saved version” or your browser settings remove it at
any time.
Legal basis: Art. 6(1)(f) GDPR and § 25(2) TDDDG (strictly necessary
function).
On the debate pages, the community tendency lets you indicate whether an
argument is stronger or weaker than scored. The vote is stored on the
server (level and chosen reasons per argument) so that it counts towards
the shared tendency and you can change it later. If you are signed in,
it is linked to your account and no additional cookie is set. If you
vote without an account, the website sets the cookie
av_voter when you first submit a vote. It contains a
randomly generated device identifier (av_ plus 24
characters) and a server signature that makes a forged cookie
detectable; it contains no name, no email address and no IP address.
Purpose: to link your vote to this browser, so that only one vote per
device and argument counts, you can change it, and repeated write
attempts are limited (the counter for this is deleted after 24 hours).
The cookie is set as httpOnly, SameSite=Lax
and, over HTTPS, Secure, and expires after 365 days; you can
delete it at any time in your browser settings. Merely viewing the
tendency sets no cookie. For anonymous votes, Cloudflare Turnstile also
checks the request (see section 9).
Legal basis: § 25(2) no. 2 TDDDG (strictly necessary for the vote you
explicitly requested) and Art. 6(1)(f) GDPR (legitimate interest in one
vote per device and in preventing abuse).
5) User account & sign-in
You can create an account to use the community features (discussing, suggesting, agreeing). In doing so, we process:
- your display name (freely chosen, may be a pseudonym; the only thing shown publicly),
- your email address (for verification, sign-in, password reset and important account notices; never public),
- when registering by email: your password, solely as a cryptographic hash (no plain text),
- when signing in via GitHub: the user identifier transmitted by the provider, your GitHub username (which we adopt as your public display name, not your real name) and your email address. In this case no password is stored with us. Signing in with GitHub is subject to the provider's privacy terms; we receive only the basic data listed (no access to other account content),
- session data (IP address and user agent of active sessions) to secure the account and manage active sign-ins,
- role and status data (e.g. team role, suspension status) to administer the community.
Purpose: provision of the account and the community features, abuse
prevention.
Legal basis: Art. 6(1)(b) GDPR (contract of use); for security measures
additionally Art. 6(1)(f) GDPR.
Data minimisation applies: only what operation strictly requires is
stored; no real-name, address or payment data. You can change your
display name yourself at any time under "Account".
6) Public posts & community data
- Posts are public: comments, value suggestions and submissions appear with your display name and a timestamp. Earlier versions of edited posts remain publicly viewable (transparency principle).
- Agreements (likes): the count is public; the link to your account is stored internally (one vote per account).
- Follows & notifications: if you follow threads or write posts, we store this in order to show you notifications on the website. No emails are sent for this.
- Reports: if you report a post, we store the reason and, if you are signed in, your account. Reports are also possible without an account. Moderation decisions are logged internally (documentation obligation).
- Account deletion = anonymisation: if you delete your account, your email address, password hash, login links and sessions are physically deleted. Your published posts remain as part of the documented debate and are shown as "Deleted account", with no link to you as a person. You can delete individual posts yourself beforehand.
Legal basis: Art. 6(1)(b) GDPR; for moderation and abuse prevention Art. 6(1)(f) GDPR (legitimate interest in a secure platform that complies with the law).
7) Topic suggestions (form)
The "Suggest a topic" form lets you suggest which policy debate we
should cover next. Only the topic is required; reasoning, policy area,
links and your email address are optional. We store your details in our
database (Cloudflare D1, EU) and also send them by email to our
editorial inbox (info@argupedia.com). If you give an email address, we use
it solely to follow up on your suggestion.
To prevent abuse, we also store a hash of your IP
address (SHA-256 with a secret salt) in order to limit the
number of submissions per hour. The IP address itself is not stored;
the hash cannot be reversed. The bot protection described in section 9
also applies.
Legal basis: Art. 6(1)(f) GDPR (legitimate interest in developing the
content and in preventing abuse); where you voluntarily give your email
address, additionally Art. 6(1)(a) GDPR (consent), which you can
withdraw at any time.
7a) Chat "Ask the bot"
The chat answers questions about the method and the debate on the current
page using the AI model Claude Haiku by Anthropic PBC (USA). What you type
into the chat is sent to Anthropic together with the earlier messages of
this chat and the path of the current page, so that the answer can be
produced. Please do not enter personal data in the chat.
For each chat we store one row without content (time,
language, page, number of questions, tokens used and cost) in order to
cap costs; it is deleted after 400 days. For the question limit we count
questions per hash of your IP address as in section 7; the counter is
deleted after 24 hours.
We store your questions only if you agree in the chat
window: then the question text, page, time and any signpost card
shown, without IP address and without account, for 90 days, to see what
is still unclear on the website. The bot's answers are never stored. Your
choice is remembered by the browser for the session of the tab
(sessionStorage) and can be changed in the chat window at any time. It
also remembers that you confirmed the notes on use
(terms of use, clause 9a); no chat starts
without this confirmation. The bot protection in section 9 applies
before the first question.
Legal basis: Art. 6(1)(f) GDPR (legitimate interest in answering
questions about the website and preventing abuse); for storing questions
Art. 6(1)(a) GDPR (consent), which you can withdraw at any time.
Data processing: Anthropic processes the chat content on our behalf;
transfers to the USA are covered by standard contractual clauses.
8) Sending emails (Resend)
For account emails (email confirmation, password reset, confirmation of
account deletion) we use the email service Resend (Resend, Inc., USA).
This involves processing your email address and the content of the
account email concerned. The notification about a topic suggestion
(section 7) to our editorial inbox is also sent via the same service.
No newsletters or advertising emails are sent.
Legal basis: Art. 6(1)(b) GDPR.
Data processing: a data processing agreement is in place with Resend;
for transfers to the USA, Resend relies on the EU–U.S. Data Privacy
Framework and/or standard contractual clauses.
9) Bot protection (Cloudflare Turnstile)
To protect against automated abuse, we use Cloudflare Turnstile for
certain actions (e.g. registration, password reset, anonymous reports,
community tendency votes without an account, the first question in the
chat).
Turnstile uses technical signals (e.g. browser characteristics,
interaction signals, IP address) to check whether a request comes from
a human, without picture puzzles and without cross-user tracking.
Legal basis: Art. 6(1)(f) GDPR (legitimate interest in preventing
abuse); processing on our behalf by Cloudflare (see section 2).
10) Data transfers to third countries (in particular the USA)
Cloudflare and Resend may also process data in the USA. Both providers base transfers on the EU–U.S. Data Privacy Framework and/or standard contractual clauses (SCCs). Anthropic processes the content of the chat (section 7a) in the USA on the basis of standard contractual clauses. If you sign in via GitHub, GitHub processes your data under its own responsibility; its privacy notices apply.
11) Retention period
I process personal data only for as long as is necessary for the purposes stated. Server and security data (e.g. log data) are usually stored for 7–30 days. Account data is stored until the account is deleted; expired sessions are removed regularly. Public posts remain, anonymised after account deletion (see section 6). Topic suggestions (section 7) are deleted once the suggestion has been dealt with, at the latest after 24 months; the IP hash is removed after 30 days. For the chat (section 7a): 400 days for the cost row without content, 90 days for stored questions, 24 hours for the question counter. Backup copies of the databases are made and overwritten on a regular cycle.
12) Your rights
You have the right of access, rectification, erasure, restriction of processing and data portability, and the right to object to processing based on Art. 6(1)(f) GDPR. You also have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR). You can delete your account yourself at any time under "Account"; an informal email is sufficient for a request for information about your data.
13) Contact
Please send data protection requests to: info@argupedia.com