Terms of use
Updated Oct. 22, 2026
This English version is provided for convenience. If the versions differ, the German version prevails.
1. Scope and provider
These terms apply to the use of Anbloq and to all paid subscriptions. The provider is the operator named in
the imprint. How we process personal data is described in the
privacy policy.
2. Services
Reading, posting, commenting, and the archive are free. There are also paid monthly subscriptions, described
on the Premium page:
- Anbloq Badge: €4 per month including VAT.
- Anbloq Premium: €12 per month including VAT.
A subscription gives no advantage in ranking, visibility, or moderation. There is no right to uninterrupted
availability; we aim for stable operation.
3. Account
- You must be at least 16 years old. The +18 forum and blogs marked NSFW are for adults only.
- Provide an email address where you can be reached and keep your login details secret.
- A real name is not required. You must not impersonate another person.
- You can delete your account at any time in your settings.
4. Your content
You keep the rights to your content. You grant the provider a non-exclusive, worldwide, free right to store,
display, search, and permanently keep your public content in the Anbloq archive. This right continues in
anonymised form after you delete your account, unless you delete the content as well.
You are responsible for your content and make sure you hold the necessary rights to it.
5. What is not allowed
Anbloq does not moderate opinions. Not allowed is content that is illegal under the law of your country or
under the law that applies to Anbloq (Germany and the EU), as well as:
- doxxing, meaning publishing other people's private data,
- spam and automated bot abuse,
- malware and links to malicious software,
- direct threats and calls for real-world violence,
- actions that endanger the operation or security of the platform.
Adult content is only allowed in the +18 forum or when marked NSFW.
6. Reports and moderation
- Anyone can report blogs and comments, even without an account. We confirm receipt by email and tell you the decision.
- People review reports. New content is also checked automatically for typical spam patterns.
- Possible measures are removing content (a placeholder with the reason stays visible), marking it NSFW, and suspending an account temporarily or permanently.
- If we take a measure, you receive a statement of reasons by email. You can contest it by replying or writing to the address in the imprint; we will then review the decision again.
- You can also turn to a certified out-of-court dispute settlement body (Art. 21 DSA) or a court.
7. Subscriptions, payment, and cancellation
- Subscriptions are billed monthly in advance through Stripe and renew automatically for another month.
- The contract is concluded when you complete payment with Stripe.
- You can cancel at any time with effect from the end of the paid month, using the “Cancel subscription” button in your settings or in the billing portal. Features stay active until then.
- We announce price changes at least six weeks in advance. You can cancel until they take effect.
8. Right of withdrawal
Consumers have a right of withdrawal as follows:
Right of withdrawal
You have the right to withdraw from this contract within fourteen days without giving any reason.
The withdrawal period is fourteen days from the day the contract is concluded.
To exercise your right of withdrawal, you must inform us
(Tarik Marton, c/o Impressumservice Dein-Impressum, Stettiner Str. 41, 35410 Hungen, Germany; E-Mail: tamaritter.38@gmail.com)
of your decision to withdraw from this contract by an unequivocal statement (e.g. a letter sent by post or an
email). You may use the model withdrawal form below, but it is not obligatory.
To meet the withdrawal deadline, it is sufficient for you to send your communication concerning your exercise
of the right of withdrawal before the withdrawal period has expired.
Effects of withdrawal
If you withdraw from this contract, we shall reimburse all payments received from you without undue delay and
in any event not later than fourteen days from the day on which we are informed about your decision to
withdraw from this contract. We will carry out such reimbursement using the same means of payment as you used
for the initial transaction, unless you have expressly agreed otherwise; in any event, you will not incur any
fees as a result of such reimbursement.
If you requested to begin the performance of services during the withdrawal period, you shall pay us an amount
which is in proportion to what has been provided until you have communicated to us your withdrawal from this
contract, in comparison with the full coverage of the contract.
Model withdrawal form
(Complete and return this form only if you wish to withdraw from the contract.)
(*) Delete as appropriate.
9. Liability
We are liable without limitation for intent and gross negligence, for injury to life, body, or health, and
under the Product Liability Act. For slight negligence we are only liable for breaches of essential
contractual obligations, limited to the foreseeable, typical damage. For other people's content we are liable
under the statutory rules for hosting services.
10. Changes and final provisions
- We inform signed-in members of changes to these terms in good time beforehand.
- German law applies, excluding the UN Convention on Contracts for the International Sale of Goods. Mandatory consumer protection rules of the country where you have your habitual residence remain unaffected.
- We are neither willing nor obliged to take part in dispute resolution proceedings before a consumer arbitration board.
Privacy policy
Updated Oct. 23, 2026
This English version is provided for convenience. If the versions differ, the German version prevails.
1. Controller
The controller for data processing on Anbloq is the provider named in the imprint,
which lists name, postal address, and email address. Send privacy questions and requests about your rights
to that email address.
2. Summary
- Anbloq uses no tracking, analytics, or advertising cookies and no ad networks.
- We only use cookies and local storage that are technically necessary to run the service.
- Blogs, comments, traces, reviews, and your public profile are visible to everyone and are kept permanently as part of the archive.
- Payments are handled by Stripe. We never receive your card details.
3. Hosting and server logs
Anbloq is hosted by Railway Corporation, 548 Market St PMB 68956, San Francisco, California 94104, USA.
Anbloq uses servers in the European Union. Railway provides a
Data Processing Addendum.
Further information is available in
Railway's privacy policy.
For processing outside the EU, see section 13.
Every page request processes technically necessary data: IP address, date and time, requested address,
status code, amount of data transferred, referrer, and browser and operating system (user agent). This
data is used to deliver the page, analyse errors, and defend against attacks.
Application and deployment log availability at Railway depends on the selected plan:
Free: 3 days; Trial and Hobby: 7 days; Pro: 30 days; Enterprise: up to 90 days.
These periods describe dashboard availability rather than guaranteed final deletion;
Railway states that upgrading plans can restore older logs.
See Railway's log documentation.
To prevent abuse (for example on login, registration, password reset, and reports) we count requests per IP
address and account. Counters are shared across servers in the database, using
keyed hashes instead of readable IP addresses, emails or usernames. Request
windows last up to one hour; daily upload-byte budgets reset after 24 hours.
Expired counters are removed as new counters are created.
The legal basis is our legitimate interest in a secure and stable service (Art. 6(1)(f) GDPR).
4. Account and profile
For an account we process your username, email address, and password, which we only store as a secure
hash. You may optionally add a display name, bio, location, website, profile picture, banner, accent colour,
theme, and further profile settings. Profile details, account age, and your activity (for example the
number of blogs) are public. A real name is not required.
Your account also includes your settings (such as whether NSFW content is shown), follows, saved blogs,
votes, the seen state of traces, and notifications.
If email confirmation is enabled, we send you a confirmation link. We also send password reset emails (see
section 8).
The legal basis is the performance of the terms of use (Art. 6(1)(b) GDPR).
5. Public content and archive
Blogs, comments, traces, sources in public libraries, reviews, and reactions are public and are shown with
your username, date, and edit status. Anbloq is meant to be a lasting archive: content stays findable,
including through search engines. Exceptions are blogs marked NSFW and the +18 forum, which are only shown to
signed-in people who enabled NSFW content and are excluded from indexing.
Removed or deleted content may remain visible as a placeholder (for example "[removed: spam]") so that
discussions stay traceable. The content itself is no longer shown.
The legal basis is the performance of the terms of use (Art. 6(1)(b) GDPR) and our legitimate interest in a
lasting, traceable discussion archive (Art. 6(1)(f) GDPR).
6. Private areas
Files and folders in the Anbloq Library, premium uploads, private notes, and private sources are stored for
you only. They are not public unless you explicitly share them through a share link. We only access them
when this is necessary for technical operation, to handle a report, or because of a legal obligation.
The legal basis is the performance of the terms of use (Art. 6(1)(b) GDPR).
7. Signing in with Google or GitHub
You may optionally sign in with Google or GitHub. We then receive a unique account ID and your email address
from that provider, plus your GitHub username for GitHub, and link them to your Anbloq account.
- Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland (privacy policy)
- GitHub, Inc., 88 Colin P. Kelly Jr. Street, San Francisco, CA 94107, USA (privacy policy)
Google's sign-in script only loads after you click "Continue with Google". Only then are your IP address and
technical browser data transmitted to Google.
The legal basis is the performance of the terms of use at your request (Art. 6(1)(b) GDPR). For transfers to
the USA, see section 13.
8. Sending emails
System emails (email confirmation, password reset) are sent through Resend, Inc., USA
(privacy policy). Your email
address and the content of the message are transmitted to Resend. We do not send newsletters or marketing
emails.
The legal basis is the performance of the terms of use (Art. 6(1)(b) GDPR).
9. Subscriptions and payments
Badge and Premium subscriptions are processed by Stripe Payments Europe, Limited, 1 Grand Canal
Street Lower, Grand Canal Dock, Dublin, D02 H210, Ireland
(privacy policy). You enter payment details
directly with Stripe; we do not receive them. We store the Stripe customer ID, the plan, status, billing
period, cancellations, and refunds. Cancellations through the cancellation form in your settings are stored with name, email address, contract, type,
and time, and you receive a confirmation by email. Stripe is partly a controller in its own right for payment processing
and also processes data to prevent fraud.
The legal basis is the performance of the contract (Art. 6(1)(b) GDPR) and statutory retention duties
(Art. 6(1)(c) GDPR in conjunction with section 147 of the German Fiscal Code and section 257 of the German
Commercial Code).
10. Reports, moderation, and security
When you report content, we store the report, the reason, your explanation, the reported content, and your
account or, without an account, your name and email address. We confirm receipt and tell you the decision by
email. If your own content is removed, you receive a statement of reasons by email. For decisions about
content or accounts we store the reason, time, and the person who acted. Spam filters automatically check new
content for typical spam patterns.
The legal basis is our legitimate interest in protecting the platform (Art. 6(1)(f) GDPR) and the duties
under the Digital Services Act (Art. 6(1)(c) GDPR).
11. Cookies and local storage
We only use technically necessary storage:
sessionid: keeps you signed in (cookie, until you sign out, at most two weeks).
csrftoken: protects forms against forgery (cookie, one year).
django_language: stores your language if you switch it manually (cookie, until you close the browser).
anbloq-theme: stores your colour scheme (browser local storage).
anbloq-seen-traces: remembers which traces you have already seen (local storage).
anbloq-post-scroll: restores your scroll position in the feed (session storage).
anbloq-offline-…: the service worker's offline cache with a notice page, the stylesheet, and the logo, so Anbloq shows an offline page without a connection and can be installed as an app. No personal content is stored there.
This storage is strictly necessary for the functions you request (section 25(2) no. 2 of the German TDDDG),
so no consent is required. You can delete it in your browser at any time.
12. External content
-
GIFs and emotes:
Opening the GIF or emote picker connects your browser to GIPHY or 7TV. GIPHY receives GIF search terms; emote names are searched locally after loading the 7TV set. Embedded media load directly from these providers, which receive your IP address and technical request data. We do not send them your post text or Anbloq account details.
GIPHY
· 7TV
-
Knowledge pages: our server downloads Wikipedia articles without transmitting any of your
data. Images on these pages, however, load directly from servers of the Wikimedia Foundation, Inc. (USA).
The Wikimedia Foundation receives your IP address. We serve the formula rendering (KaTeX) ourselves.
-
Linked profile pictures: if someone sets a profile or banner image as an external address,
your browser loads that image directly from the external server.
-
Links: you open external links in blogs and sources yourself; the privacy policy of that
website then applies.
The legal basis is our legitimate interest in displaying this content (Art. 6(1)(f) GDPR).
13. Transfers to third countries
Some of the providers above (in particular Railway, Resend, GitHub, Google, Stripe, and the Wikimedia Foundation) also
process data in the USA. Transfers rely on the adequacy decision for the EU-US Data Privacy Framework
(Art. 45 GDPR) where the provider is certified, and otherwise on the EU standard contractual clauses
(Art. 46(2)(c) GDPR).
14. Retention
- We keep account data until you have your account deleted.
-
You can delete your account at any time in your settings or request deletion by email. We then delete your
login details, profile data, connections, and private content.
Public blogs and comments are deleted or anonymised so that they can no longer be linked to you.
- We keep billing records for up to ten years because of statutory obligations.
- We keep reports and moderation decisions as long as they are needed for handling and evidence.
- Request counters expire after at most one hour, upload-byte counters after 24 hours. Expired entries are periodically removed.
15. Your rights
Under the GDPR you have the right to
- access the data stored about you (Art. 15),
- rectification of inaccurate data (Art. 16),
- erasure (Art. 17) and restriction of processing (Art. 18),
- data portability (Art. 20),
- object to processing based on our legitimate interest (Art. 21),
- lodge a complaint with a data protection supervisory authority (Art. 77), in particular in the member state where you live.
You can change many details directly in your settings, where you can also delete your account. For everything
else, an email to the address in the
imprint is enough.
16. Minors and the +18 forum
Anbloq is intended for people aged 16 and over. The +18 forum and
blogs marked NSFW are for adults only; enabling NSFW content confirms that you are at least 18 years old.
17. Security and changes
Connections are encrypted with TLS, passwords are only stored as hashes, and access to administrative
functions is restricted. We update this privacy policy when features or the law change. The version
published here applies.