Correcting a Wrong SCHUFA Entry in Berlin: Your Article 16 GDPR Right, and Why Berlin's Own Regulator Can't Help

A SCHUFA entry being wrong in fact, an already-repaid debt that was never removed, a claim listed at the wrong amount, a previous tenant or a name mix-up attached to your file, is a genuinely different problem from a debt collection letter that skipped the legal steps required to become a SCHUFA entry in the first place. For this kind of factual error, Article 16 GDPR gives you a direct right to demand correction, not just deletion. Start by requesting your data: Berlin's own data protection authority (the Berliner Beauftragte für Datenschutz und Informationsfreiheit, BlnBDI) confirms you're entitled to a free disclosure from SCHUFA once a year by post, while the fuller Article 15 GDPR Datenkopie through meineschufa.de is a separate, repeatable channel worth using proactively rather than only after you suspect a problem. Once you've identified the specific error, SCHUFA is legally required to respond within one month under Article 12(3) GDPR, extendable by up to two further months for genuinely complex cases if they tell you why. If SCHUFA doesn't correct it, you can escalate to their own Ombudsfrau free of charge, or file a complaint with the Hessischer Beauftragter für Datenschutz und Informationsfreiheit (HBDI). One thing worth being direct about if you live in Berlin specifically: the BlnBDI's own SCHUFA page states plainly that it is not the responsible authority here and points you to Hesse instead, since that's where SCHUFA is headquartered.

The Official Rule

Not every wrong-feeling SCHUFA entry is a procedural problem, and it’s worth being precise about which kind of error you’re actually dealing with. A collection letter that skipped the legal reminder steps before being reported is a procedural issue, covered elsewhere. This page is about a different, genuinely common problem: the data itself being factually wrong, a debt that was already repaid but was never removed from your file, a claim listed at an inflated amount, or, in a genuinely disruptive scenario for newcomers, a previous tenant’s or a similarly named person’s information attached to your record by mistake.

The starting point is seeing exactly what SCHUFA has on file, and Berlin’s own authority actually spells out two different ways to do that. The Berliner Beauftragte für Datenschutz und Informationsfreiheit (BlnBDI) confirms on its own SCHUFA page that you can request a free disclosure once a year by post, an older, simpler mechanism worth knowing about on its own. Separately, and more useful if you’re actively checking for an error, Article 15 GDPR entitles you to a Datenkopie, a full self-disclosure, through SCHUFA’s own meineschufa.de portal, and consumer finance guides like finanztip.de describe this route as usable more than once a year, since GDPR itself doesn’t cap it the way the postal option effectively is. Once you’ve identified a specific, factual error, Article 16 GDPR gives you a direct right to demand correction, not merely deletion, since a correction (fixing the actual figure or removing data that belongs to someone else) is often the more accurate remedy than a blanket deletion request.

SCHUFA doesn’t get an indefinite amount of time to respond. Article 12(3) GDPR requires a response within one month of your request, extendable by up to two further months for genuinely complex cases, as long as you’re told the reason for the delay within that first month. If they simply don’t act, or refuse without a real explanation, you have two free paths forward: SCHUFA’s own Ombudsfrau, an internal review process that can order verification or a correction, and a formal complaint to the Hessischer Beauftragter für Datenschutz und Informationsfreiheit (HBDI), the actual supervisory authority for SCHUFA specifically, since the company is headquartered in Wiesbaden, Hesse.

This is where living in Berlin specifically matters, and it’s worth being direct about it rather than assuming your own city’s regulator handles everything. The BlnBDI’s own SCHUFA page doesn’t just stay silent on this, it states plainly that the Hessischer Beauftragter für Datenschutz und Informationsfreiheit is responsible for SCHUFA, not the Berlin office itself. That’s a genuinely useful thing to know upfront, since it saves a round trip: if you file a SCHUFA complaint with Berlin’s own authority expecting it to act, the realistic outcome is a redirect to Hesse rather than a resolution, and going straight to the HBDI from the start is the faster path.

How long different SCHUFA entries are supposed to stay on file
Entry typeRetention period
Repaid credit contract data3 years after full repayment
Account or contract closure noticeImmediate deletion once reported
Credit inquiries (Anfragen)12 months
Concluded insolvency proceedings6 months after completion
Factually incorrect dataImmediate deletion once confirmed wrong
Two people at a desk reviewing a printed credit offer document together, one holding the page and pointing at a line item

Photo by RDNE Stock project on Pexels

What Real People Say

Consumer finance guides that walk through this process consistently point to the same recurring error types: a loan that was fully repaid but the closure notice never reached SCHUFA, an old address or account still attached to your file after a move, and, less often but more disruptively, data that genuinely belongs to a different person entirely, a mix-up that newcomers with common transliterated names sometimes report more frequently than the general population. Berlin’s own housing-search guides on this site describe a related, practical wrinkle: many landlords here don’t actually want the free Datenkopie at all, they want the paid SCHUFA-BonitätsCheck instead, which is a genuinely different document built for that specific purpose, so don’t assume the free disclosure you’re requesting to check for errors is the same thing a landlord is asking for.

On the escalation path, guides note that the HBDI has faced a genuinely high volume of SCHUFA-related complaints in recent years, and some consumer advocates have publicly criticized how quickly those complaints get resolved. That’s not a reason to skip the complaint, since it remains a real, free, and legally grounded escalation path, but it’s worth setting realistic expectations about the timeline rather than assuming an immediate resolution, and it’s worth going directly to the HBDI from the start rather than routing through Berlin’s own authority first.

Step by Step

  1. Request your free annual postal disclosure from SCHUFA, per Berlin’s own BlnBDI guidance, or go straight to the fuller Article 15 GDPR Datenkopie through meineschufa.de if you want a more current, repeatable check.
  2. Read through it carefully for factual errors: repaid debts still listed, amounts that don’t match your own records, or entries connected to an address, account, or name that isn’t actually yours.
  3. Submit a written correction request under Article 16 GDPR, citing the specific entry and the specific error, by post, phone, or through SCHUFA’s own service portal.
  4. Track the one-month response deadline under Article 12(3) GDPR, and note that a genuine extension of up to two further months requires SCHUFA to tell you why within that first month.
  5. If SCHUFA doesn’t act, contact their Ombudsfrau first, a free internal review step that can order verification or a correction.
  6. If that doesn’t resolve it, file a formal complaint directly with the HBDI in Hesse, not Berlin’s own BlnBDI, since Berlin’s authority itself points complainants to Hesse for anything involving SCHUFA’s own conduct.

Compliance Note

This page explains the general legal framework under EU and German data protection law for correcting a factually wrong credit bureau entry, current as of mid-2026. It is not legal advice, and the specific facts of your case, including whether an entry is genuinely incorrect or simply unwelcome, determine what remedy actually applies. For a disputed case that doesn’t resolve through these channels, consult a Verbraucherzentrale or a lawyer specializing in Datenschutzrecht.

FAQ & Common Pitfalls

How is this different from the rules about a collection letter turning into a SCHUFA entry?

They're two genuinely different mechanisms. The collection letter threshold is about procedure: whether a creditor followed the required steps (two written reminders, a four-week gap, an advance warning) before reporting a genuine, undisputed debt. This page is about content: whether the data itself is factually correct at all, regardless of procedure, for example a debt that's already been repaid but never removed, an amount that's simply wrong, or a previous tenant's or a similarly named person's information attached to your file by mistake. A procedural violation and a factual error can both exist, but they're challenged on different grounds.

I keep seeing 'once a year' and 'several times a year' for the free SCHUFA disclosure. Which is it?

Both exist, and they're genuinely different channels, which is worth being precise about. Berlin's own data protection authority (BlnBDI) states on its own SCHUFA page that you're entitled to one free disclosure a year by post, an older, simpler mechanism. Separately, the Article 15 GDPR Datenkopie through SCHUFA's own meineschufa.de portal is a broader, more current export of your file, and consumer finance outlets like finanztip.de describe requesting it more than once a year as reasonable, since GDPR itself doesn't impose a strict one-request-per-year cap the way the older postal option effectively does. Using both, the routine annual postal check and the online portal when you actually suspect something, is a reasonable way to stay on top of your file.

What happens if SCHUFA just ignores my correction request?

You have two free escalation paths. First, SCHUFA has its own Ombudsfrau, a free, internal review process that can order verification of a disputed entry or mandate a correction. Second, and separately, you can file a formal complaint with the Hessischer Beauftragter für Datenschutz und Informationsfreiheit (HBDI), the state data protection authority with jurisdiction over SCHUFA specifically, since the company is headquartered in Wiesbaden. Be aware that HBDI complaint volumes about SCHUFA have genuinely been high, so processing times can run longer than you'd expect from a straightforward request.

I live in Berlin. Can't I just complain to Berlin's own data protection authority instead of dealing with Hesse?

No, and Berlin's own regulator is explicit about this rather than leaving it ambiguous. The BlnBDI's SCHUFA page states directly that it is not the responsible authority for SCHUFA itself, and names the HBDI in Hesse as the correct one, since SCHUFA Holding AG is headquartered in Wiesbaden and German data protection complaints go to the authority with jurisdiction over the company you're complaining about, not the state where you personally live. The BlnBDI remains the right place for complaints about Berlin-based companies or landlords mishandling your data; it just isn't the right place for SCHUFA's own conduct.