Privacy Policy

Your letters contain personal information, so it matters what happens to them. This page explains, in plain English, what data Klartext processes and why. Where this translation and the legal requirements differ, the principles of the EU General Data Protection Regulation (GDPR / DSGVO) apply.

1. Who is responsible (Verantwortlicher)

Husameldin Osman Awadelkarim
Isländische Str. 12, 10439 Berlin, Germany
E-mail: hossamossman92@gmail.com

See also the Impressum.

2. What we process, and why

a) The letter you submit

When you paste text or upload a photo or PDF of a letter, that content — including any personal data inside it (names, addresses, reference numbers, financial or health details, etc.) — is processed solely to generate the plain-English explanation you receive. You submit this voluntarily.

• Purpose: to read your letter and return an explanation.
• Legal basis: your consent (Art. 6(1)(a), and Art. 9(2)(a) GDPR for any special-category data such as health information), given by submitting the letter, and the performance of the service you requested (Art. 6(1)(b) GDPR).
• Storage by Klartext: we do not save your letter or the explanation on our server. They are held in memory only for the moment it takes to generate your answer, then discarded. There is no account and no history.

b) Technical data

To keep the service available and prevent abuse, our hosting provider and the application process your IP address and basic request information transiently.

• Purpose: security and rate-limiting (capping how many requests one visitor can make).
• Legal basis: our legitimate interest in a secure, functioning service (Art. 6(1)(f) GDPR).

3. AI processing (Anthropic)

To produce the explanation, the content you submit is sent to Anthropic PBC (the provider of the Claude AI model) via its API. Anthropic acts as a processor on our behalf under a data processing agreement.

• Anthropic may process the data on servers outside the European Union (e.g. in the United States). This international transfer is safeguarded by the EU Standard Contractual Clauses incorporated into Anthropic's terms.
• Through the commercial API, your inputs and outputs are not used to train Anthropic's models. Anthropic may retain API data for a limited period for trust-and-safety / abuse-monitoring purposes before deletion, as described in its policies.
• Anthropic's privacy terms: anthropic.com/legal/privacy.

4. Hosting

This website is hosted by Render Services, Inc., which processes server log data (including IP addresses) to deliver the site. The provider may be located outside the EU; such transfers are covered by Standard Contractual Clauses. Legal basis: Art. 6(1)(f) GDPR.

5. Cookies & analytics

Klartext uses no cookies and no third-party trackers. To understand how the tool is used, we record anonymous, aggregate events on our own server — when a page is opened or a letter is explained, together with a coarse device type (mobile/desktop) and, where available, the country. These records contain no cookies, no stored IP address, and nothing that identifies you, and are kept in a private spreadsheet we control. Fonts are served from our own server, so no data is sent to third-party font providers.

6. How long we keep data

Klartext does not store your letters or explanations. Transient technical/security data is kept only as long as needed for that purpose. Any retention by Anthropic or the hosting provider is governed by their respective terms.

7. Your rights

Under the GDPR you have the right to access, rectification, erasure, restriction, data portability, and to object to processing. Because we do not store your letters or hold an account for you, there is normally no personal data on our side to retrieve or delete after a request completes. For any request, contact us at hossamossman92@gmail.com.

You also have the right to lodge a complaint with a supervisory authority. The competent authority here is the Berliner Beauftragte für Datenschutz und Informationsfreiheit (BlnBDI).

8. Changes

We may update this policy as the service evolves. The current version always applies.