AccountRights.
Check my options My space
GDPR Data Rights Article 17

GDPR and Platform Bans: What Articles 12, 17 and 22 Can (and Cannot) Do

GDPR Articles 12, 17 and 22 can support a challenge to an automated ban, in particular the right not to be subject to a solely automated decision. How to file a complaint with your national data protection authority.

AC
AccountRights Legal Research
Updated 11 min

A widespread idea holds that Article 17 of the GDPR, the "right to erasure", can get a ban overturned. It cannot: that article is used to have data erased, not to reopen an account. But the GDPR is not useless against a platform for all that. Its Articles 12, 15 and 22, together with Article 17 and a few others, give concrete rights: to know what the platform has recorded about you, to obtain an explanation of an automated decision, to require human intervention in certain cases, to prevent your data from being erased during a dispute, and to claim compensation for damage. These rights can support a challenge; on their own, they do not force an account to be restored. This article explains what each provision really allows, how to invoke it, and where its limits lie.

Key points

  • Article 17 of the GDPR lets you obtain the erasure of data, in particular data processed unlawfully; it does not provide for an account to be reopened.
  • Article 22 in principle prohibits decisions based solely on automated processing that significantly affect you, but it provides for exceptions, including the contract exception.
  • Article 15 gives you access to your data and, in the case of an automated decision, to meaningful information about its logic; the platform answers within one month, which can be extended by two months.
  • A complaint to the data protection authority is free of charge; Article 82 gives a right to compensation if an infringement has caused you damage.
  • The obligation to give reasons for an account suspension comes from the DSA (Article 17), not from the GDPR: the two texts complement each other.

What Article 17 of the GDPR really says (and does not say)

Article 17(1) gives the data subject the right to obtain "the erasure of personal data concerning him or her without undue delay" where one of six grounds applies. The most useful here:

  • (a) the data "are no longer necessary in relation to the purposes for which they were collected";
  • (b) you withdraw the consent on which the processing is based, and there is no other legal ground;
  • (c) you object to the processing under Article 21 and there are no overriding legitimate grounds;
  • (d) the data "have been unlawfully processed".

The key words are therefore "unlawfully processed", in point (d), and not in point (f) as is sometimes claimed: point (f) concerns data collected from children in connection with online services.

Many users invoke Article 17 to demand: "erase my data and give me my account back". That is a contradiction. Erasure makes data disappear; it does not put an account back into service. And Article 17(3) provides that the right to erasure does not apply to the extent that processing is necessary "for the establishment, exercise or defence of legal claims". A platform that expects a dispute can rely on this to keep certain data.

The value of the GDPR in a ban lies elsewhere: it concerns the way the platform processed your data to reach its decision, your right to know about it, and the preservation of what belongs to you.

The Article 22 angle: automated decisions without human intervention

Article 22(1) provides: "The data subject shall have the right not to be subject to a decision based solely on automated processing, including profiling, which produces legal effects concerning him or her or similarly significantly affects him or her." The deletion of an account that carries your business, your contacts or your income can, depending on the case, be a decision that significantly affects you.

But paragraph 2 provides for three exceptions. The prohibition does not apply where the decision:

  • (a) "is necessary for entering into, or performance of, a contract" between you and the controller;
  • (b) is authorised by Union or Member State law, with suitable safeguards;
  • (c) is based on your explicit consent.

Platforms often invoke the first: in their view, enforcing their terms of use falls under the performance of the contract. This is debatable case by case, but it shows that Article 22 is not an absolute prohibition. On the other hand, in cases (a) and (c), paragraph 3 imposes minimum safeguards: "at least the right to obtain human intervention on the part of the controller, to express his or her point of view and to contest the decision".

What does valid human intervention look like? The Article 29 Working Party guidelines on automated decision-making (WP251rev.01), endorsed by the European Data Protection Board, are specific: the controller cannot avoid Article 22 by "fabricating human involvement"; oversight must be "meaningful, rather than just a token gesture", carried out by someone who has the authority and competence to change the decision, and who takes into account all the relevant data, including information provided by the data subject.

The Court of Justice of the European Union has also given a broad reading of the notion of an automated decision. In the SCHUFA judgment (C-634/21, 7 December 2023), it held that an automatically calculated score constitutes "automated individual decision-making" where a third party draws strongly on that score to establish, implement or terminate a contractual relationship. A result produced by a machine and applied as is can therefore fall under Article 22, even if a person formally signs the decision.

In practice, Article 22 allows you to ask: was the decision taken solely by automated means? Which exception does the platform rely on? What safeguards has it put in place, and did a person with the power to change the decision actually go back over your case? The answers, or their absence, feed into what comes next.

The Article 12 angle: the right to exercise your rights

Article 12 does not, on its own, give a right to the reasons for a ban. It organises the way the platform must respond when you exercise your rights under Articles 15 to 22:

  • The time limit (Article 12(3)): the platform informs you of the action taken "without undue delay and in any event within one month of receipt of the request". This period can be extended by two months, taking into account the complexity and number of requests, provided it informs you, with the reasons, within the first month.
  • The reasoned refusal (paragraph 4): if the platform does not act on your request, it must tell you why, at the latest within the month, and inform you of the possibility of lodging a complaint with a supervisory authority and going to court.
  • Free of charge (paragraph 5): no payment can be required, unless a request is "manifestly unfounded or excessive", which the platform must then demonstrate.

The detailed reasons for a suspension fall under another text: Article 17 of the DSA requires the platform to give a "clear and specific" statement of reasons for any suspension or termination of an account, with the facts and circumstances, any use of automated means, the rule relied on and the available means of redress. A vague answer such as "your account has violated our Community Standards" is therefore a problem under the DSA; under the GDPR, the question is whether the platform answered your access request completely and on time.

Article 15: knowing what the platform has recorded, and how it decided

The right of access is the most concrete lever. Article 15 lets you obtain confirmation that your data are being processed, a copy of those data (paragraph 3), and a series of information items, including, in point (h), "the existence of automated decision-making, including profiling", and "meaningful information about the logic involved, as well as the significance and the envisaged consequences of such processing".

The Court of Justice clarified the scope of point (h) in the Dun & Bradstreet Austria judgment (C-203/22, 27 February 2025): the data subject may require the controller to explain, in a concise, transparent and intelligible way, "the procedure and principles actually applied" in order to use their data by automated means. According to the Court's press release, the mere communication of an algorithm does not constitute a sufficient explanation; it may be appropriate to indicate the extent to which a variation in the data taken into account would have led to a different result.

Applied to a ban, this means you can request the data linked to the decision (reports, alerts, the activity history relied on) and, if the decision was automated, an intelligible explanation of how it was produced.

Combining Articles 12, 15, 17 and 22: the GDPR argument, and what it can achieve

Here is how a GDPR line of reasoning can be built, while staying true to what the texts say:

  1. The ban rests on processing of your data. The platform used information about you (activity, content, reports, technical signals) to reach its decision.
  2. You ask to know how (Article 15). A copy of the data, the existence of an automated decision, an explanation of its logic. The answer is due within one month, which can be extended by two months (Article 12).
  3. If the decision was solely automated (Article 22), you ask which exception is relied on and what safeguards are in place, and you exercise your right to obtain human intervention, to express your point of view and to contest the decision.
  4. If data are inaccurate, for example an error about your age or activity that is not yours, you request their rectification (Article 16).
  5. To prevent your data from disappearing during the dispute, you can request restriction of processing where you need the data to assert your rights in court (Article 18(1)(c)), and retrieve the data you provided in a machine-readable format (Article 20).
  6. If the processing turns out to be unlawful, the consequences provided for by the GDPR are erasure (Article 17), a complaint to the authority (Article 77) and compensation for the damage (Article 82).

This reasoning changes the ground of the discussion: the question is no longer only "were you right to ban me?", but "did you process my data in accordance with the GDPR, and can you demonstrate it?". The reopening of the account, however, is argued on the ground of the contract and the DSA, which the material obtained through the GDPR strengthens.

The contract cannot set the GDPR aside

The GDPR is a European regulation: it applies directly. A platform's terms of use are a contract, and the contract is not among the exceptions to the right of access, the right to lodge a complaint or the right to compensation. Where the GDPR takes the contract into account, in Article 22, it is as an exception framed by minimum safeguards: human intervention, the opportunity to express yourself and to contest.

How to invoke GDPR rights against a platform ban

Step 1: the written request to the data protection officer

Send a written request to the platform's data protection officer (their address or form is given in the privacy policy). Example content:

"I am exercising my rights under Articles 15, 16, 18, 20 and 22 of the GDPR. My account [identifier] was suspended on [date], with the following reason: [stated reason].
I request:
1. a copy of all personal data concerning me, including data linked to this decision (Article 15);
2. that you tell me whether this decision was taken solely by automated means and, if so, meaningful information about the logic involved, the significance and the consequences of this processing (Article 15(1)(h)), as well as the exception under Article 22(2) that you rely on and the safeguards in place;
3. human intervention on your part, and the opportunity to express my point of view and to contest the decision (Article 22(3));
4. restriction of the processing of the data linked to my account, which are necessary for the defence of my rights (Article 18);
5. the data I provided, in a structured and machine-readable format (Article 20).
Please reply within the one-month period provided for in Article 12(3)."

Keep proof of sending and of the date: this is what starts the one-month period.

Step 2: the complaint to the data protection authority

If the platform does not reply, replies incompletely or refuses without a valid reason, Article 77 allows you to lodge a complaint with a supervisory authority, "in particular in the Member State of his or her habitual residence, place of work or place of the alleged infringement". For example:

  • France: Commission nationale de l'informatique et des libertés (CNIL);
  • Italy: Garante per la protezione dei dati personali;
  • Belgium: Autorité de protection des données (APD);
  • Luxembourg: Commission nationale pour la protection des données (CNPD);
  • Germany: in particular the Federal Commissioner for Data Protection (BfDI);
  • other countries: the list of authorities is available on the website of the European Data Protection Board (edpb.europa.eu).

For cross-border processing, the "lead" authority is the one of the platform's main establishment in the Union (Article 56). For several large platforms established in Dublin, such as Meta Platforms Ireland, this is the Irish Data Protection Commission; you can nevertheless lodge your complaint in your own country, which passes it on.

Your complaint sets out the facts, attaches the request and the answer (or the lack of an answer), and states what you are asking for: that the platform answer the access request completely, explain the automated decision and put in place the safeguards of Article 22. The GDPR does not set a time limit for handling the complaint; but if the authority does not handle the complaint or does not inform you, within three months, of its progress or outcome, Article 78(2) gives you a remedy before the courts.

Step 3: the formal letter and, if necessary, the court

The material obtained (or refused) under the GDPR strengthens a formal letter addressed to the platform's legal department, which combines the GDPR, the DSA and the contract. It can be sent by AccountRights, or drawn up, signed and sent by an independent partner lawyer, on their firm's letterhead. When platforms respond, they generally do so within a few days to several weeks; no time frame is guaranteed. If this fails, a lawyer can take the matter to court: Article 79(2) allows proceedings against the controller before the courts of the Member State of your habitual residence.

What court decisions say

Published decisions on bans ruled on under the GDPR remain rare. Those that exist show what these rights can produce, and under what conditions.

Access to data refused: a penalty of 4,000 euros per day. On 4 July 2024, the Amsterdam District Court (Mekić v. Twitter, ECLI:NL:RBAMS:2024:4019) found that Twitter had not complied with the access request under Article 15 made by a user. It ordered Twitter to answer it within the month, subject to a penalty of 4,000 euros for each day of delay. A penalty payment is a sum due for each day of delay, set by the court to secure compliance.

Automated decision: a broad notion. In the SCHUFA judgment (C-634/21), the Court of Justice held that an automatically calculated result constitutes an automated individual decision where the party using it depends on it decisively to establish, implement or terminate a contract.

Explanation of the logic: more than an algorithm. In the Dun & Bradstreet Austria judgment (C-203/22), the Court held that the data subject may require a concrete and understandable explanation of the procedure and principles applied to their data.

Compensation: there must be damage. In the Österreichische Post judgment (C-300/21, 4 May 2023), the Court held that the mere infringement of the GDPR is not sufficient to obtain compensation, but that no threshold of seriousness is required for non-material damage.

Limits: when GDPR arguments are not enough

GDPR arguments are stronger when:

  • the decision appears to have been taken solely by an automated system, with no demonstrated human intervention;
  • the platform does not answer the access request, or answers it incompletely or late;
  • it refuses to explain the logic of an automated decision;
  • inaccurate data (age, identity, activity wrongly attributed) are at the origin of the decision.

They are weaker when:

  • the platform demonstrates real human intervention, exercised by a person who could change the decision;
  • it invokes an exception under Article 22(2) and shows the safeguards in place;
  • it answered the access request completely and on time;
  • the breach of the platform's rules is real and documented: the GDPR governs the way your data are processed, it does not settle the question of whether you broke the rules.

Finally, since 17 February 2024, the DSA has already required that internal complaints against an account suspension are not handled solely by automated means (Article 20(6)). The two texts overlap: that is a reason to invoke them together.

GDPR + DSA Article 21: a dual approach

You can pursue both routes in parallel:

  • the GDPR route, with the platform and then the data protection authority: access to data, explanation of the automated decision, Article 22 safeguards;
  • the DSA route, with a certified out-of-court dispute settlement body (Article 21), which rules on the suspension decision itself. The Appeals Centre Europe, for example, is free for the user and issued its decisions in 65 days on average according to its May 2026 report; but its decisions are not binding on the platform, and it excludes certain grounds (account behaviour, identity verification, impersonation, copyright).

The two routes complement each other: a poorly explained automated decision (GDPR) often goes hand in hand with an insufficient statement of reasons (DSA), and what one brings to light serves the other.

Article 82 of the GDPR: compensation for damage

Article 82(1) provides: "Any person who has suffered material or non-material damage as a result of an infringement of this Regulation shall have the right to receive compensation from the controller or processor for the damage suffered."

According to the Court of Justice (Österreichische Post, C-300/21), this right requires three cumulative conditions: an infringement of the GDPR, material or non-material damage, and a causal link between the two. The damage may in particular be:

  • material: income lost during the period when the account was inaccessible, costs incurred;
  • non-material: for example the harm suffered as a result of a decision taken on inaccurate data or without explanation.

This right is exercised before the courts, independently of the internal appeal and of the complaint to the authority. Article 54 of the DSA, for its part, provides for a right to compensation for damage caused by an infringement of that regulation, "in accordance with Union and national law".

Take stock of your situation

If your account has been blocked and you want to know whether the GDPR, the DSA or the contract offers the best hold, the AccountRights free diagnostic takes about five minutes and points you to the solution best suited to your case: a formal letter sent by AccountRights, a letter drawn up, signed and sent by an independent partner lawyer, or full handling by an AccountRights partner lawyer, who can take the matter to court, through urgent proceedings to quickly obtain a provisional decision, or through a standard lawsuit, which takes several months.

Start the free diagnostic

Related articles

DSA Article 21 Explained: Out-of-Court Dispute Resolution

Why Meta's Internal Appeal Often Falls Short (And What Can Take Over)

The Legal Demand Letter That Gets Meta's Attention

Recovering a Banned Social Media Account: The Complete Legal Guide

Monetised Account Banned: Calculating Damages and Recovering Lost Revenue

Think your case has merit?

Our free diagnostic checks whether your file contains what is needed for an appeal. Legal analysis is carried out by the partner lawyer.

Check my options
Legal information notice: This article provides general legal information and does not constitute personalised legal advice. Only a lawyer qualified and licensed to practise can evaluate your specific situation. To check whether your file contains what is needed, use our diagnostic tool: if needed, it directs you to an independent partner lawyer. AccountRights is not a law firm.

Don't wait for the platform to act.

Every day your account stays down, evidence becomes harder to gather and deadlines move closer. Start your free diagnostic now.

Check my options